prb ip fixe

gizmo15 · Le 18/08/2006, à 15:56

bonjour a tous

jai installer un serveur teamspeak chez moie t pour avoir tout le temps la meme ip je me suis inscrit sur dyndns.org, installer ddclient et je lai configurer.

seulement quand je fais sudo ddclient pour mettre a our mon ip il em met warning: unable to determine ip adresse, sa vient dou car la je sais pas du tout??!!

et une autre question, quand on configure ddclient dans interface faut mettre quoi?

merci

ps: jai suivis ce tuto http://doc.ubuntu-fr.org/serveur/dns_dynamique

Dernière modification par gizmo15 (Le 18/08/2006, à 15:56)

dexinou · Le 18/08/2006, à 17:00

et une autre question, quand on configure ddclient dans interface faut mettre quoi?

Tu peut mettre 'web'
Voici ma config si ça peut t'aider:

# Configuration file for ddclient generated by debconf
# Conifiguration pour IP Dynamique
# /etc/ddclient.conf

daemon=300					# check every 300 seconds
syslog=yes					# log update msgs to syslog
mail=root					# mail update msgs to root
pid=/var/run/ddclient.pid			# record PID in file.
protocol=dyndns2
use=web						
server=members.dyndns.org
login=tata
password=titi
linux.homelinux.com,debian.homelinux.net

Dernière modification par dexinou (Le 18/08/2006, à 17:02)

gizmo15 · Le 18/08/2006, à 17:08

tu fais comment pour ouvrir le fichier ddclient.conf?

car je lai pas dans le dossier etc

Dernière modification par gizmo15 (Le 18/08/2006, à 17:09)

dexinou · Le 18/08/2006, à 17:10

fait une recherche:

# sudo find / -name ddclient.conf -print

Dernière modification par dexinou (Le 18/08/2006, à 17:11)

gizmo15 · Le 18/08/2006, à 17:16

merci je lai trouver mais quand je louvre avec sudo nano /etc/ddclient.conf le fichier est vide??:/ et quand je vais le chercher dans le dossier etc et bas je peux pas louvrir

dexinou · Le 18/08/2006, à 17:29

ouvre le avec nano et copie mes données dessus
indique ton login, ton passe et tes domaines.
sauvegarde avec ctrl-X et restart ddclient.

sinon fait un :
# sudo chmod 777 /etc/ddlient.conf

et ouvre le avec un éditeur comme gedit
copie les données, sauvegarde et remet le chmod 600

Dernière modification par dexinou (Le 18/08/2006, à 17:32)

gizmo15 · Le 18/08/2006, à 17:59

ok merci je teste ca et je te tiens au courant

edit: alors dans mon fichier ddclient.conf jai

pid=/var/run/ddclient.pid
protocol=dyndns2
use=if, if=web
server=members.dyndns.org
login= mon login a moi
password= mon mot de passe
et ladresse du serveur ts

y manque des trucs?

Dernière modification par gizmo15 (Le 18/08/2006, à 18:05)

dexinou · Le 18/08/2006, à 18:24

test comme ça !
n'oublie pas de recharger le client

gizmo15 · Le 18/08/2006, à 18:33

tu fais comment pour recharger le client?

dexinou · Le 18/08/2006, à 19:04

sudo /etc/init.d/ddclient restart

Dernière modification par dexinou (Le 18/08/2006, à 19:04)

gizmo15 · Le 18/08/2006, à 19:10

ok merci beaucoup de ton aide

une tite derniere avant de partir (lol): comment savoir si il envoit bien la nouvelle ip a dyndns?

dexinou · Le 18/08/2006, à 19:23

tu ouvre 2 consoles en root ou sudo.
dans la première tu fais :

# sudo tail -f /var/log/syslog

dans la deuxième tu fais :

# sudo /usr/sbin/ddclient -daemon=0 -syslog -quiet -force

et tu regarde ce qu'il t'affiche dans la première.
c'est des logs en temps réel.

Si il te dit SUCCESS, tu peux faire un cron pour mettre à jour ton IP automatiquement 2 fois par mois comme ceci :

# crontab -e

et tu ajoutes ceci sur nano :

# 30 23 1,15 * *	sudo    /usr/sbin/ddclient -daemon=0 -syslog -quiet -force

S'il te dit fail ou warning tu remplaces la ligne if=..etc... par :

use=web

Dernière modification par dexinou (Le 18/08/2006, à 19:33)

gizmo15 · Le 18/08/2006, à 19:31

ok merci mais ca ma mit plein de warning dans la premiere console quand jai fais enter!!

y a pas moyen davoir un ti icone pour voir si sa le fait bien?

Dernière modification par gizmo15 (Le 18/08/2006, à 19:32)

dexinou · Le 18/08/2006, à 19:34

tu veux pas qu'il t'apporte une tasse de thé aussi ? ^^
refait ta config il y a surement un truc qui cloche et poste tes warning pour voir.

Dernière modification par dexinou (Le 18/08/2006, à 19:35)

gizmo15 · Le 18/08/2006, à 19:40

Aug 18 20:03:59 localhost ddclient[9044]: WARNING: file /etc/ddclient.conf, lin e 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:04:59 localhost ddclient[9044]: WARNING: file /etc/ddclient.conf, lin e 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:05:59 localhost ddclient[9044]: WARNING: file /etc/ddclient.conf, lin e 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:07:00 localhost ddclient[9044]: WARNING: file /etc/ddclient.conf, lin e 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:08:01 localhost ddclient[12725]: WARNING: file /etc/ddclient.conf, li ne 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:08:01 localhost ddclient[12732]: WARNING: file /etc/ddclient.conf, li ne 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:08:07 localhost ddclient[12737]: WARNING: file /etc/ddclient.conf, li ne 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:09:01 localhost ddclient[12732]: WARNING: file /etc/ddclient.conf: fi le /etc/ddclient.conf must be accessible only by its owner (fixed).
Aug 18 20:09:01 localhost ddclient[12732]: WARNING: file /etc/ddclient.conf, li ne 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:17:01 localhost /USR/SBIN/CRON[12995]: (root) CMD ( run-parts --repo rt /etc/cron.hourly)
Aug 18 20:36:03 localhost -- MARK --

sa me fait ca

et pour la deuxieme commande sa me fait ca:
Unknown option: deamon
usage: ddclient [options]
options are:
-daemon delay : run as a daemon (default: 0).
-proxy host : use 'host' as the HTTP proxy.
-server host : update DNS information on 'host' (default: members.dyndn s.org).
-protocol type : update protocol used (default: dyndns2).
-file path : load configuration information from 'path' (default: /et c/ddclient.conf).
-cache path : record address used in 'path' (default: /var/cache/ddcli ent/ddclient.cache).
-pid path : record process id in 'path'.

-use which : how the should IP address be obtained. (default: ip).
-use=3com-3c886a : obtain IP from 3com 3c886a 56k Lan Modem at th e -fw {address}.
-use=alcatel-stp : obtain IP from Alcatel Speed Touch Pro at the -fw {address}.
-use=cisco : obtain IP from Cisco FW at the -fw {address}.
-use=cmd : obtain IP from the -cmd {external-command}.
-use=elsa-lancom-dsl10 : obtain IP from ELSA LanCom DSL/10 DSL FW at th e -fw {address}.
-use=elsa-lancom-dsl10-ch01 : obtain IP from ELSA LanCom DSL/10 DSL FW (isdn ch01) at the -fw {address}.
-use=elsa-lancom-dsl10-ch02 : obtain IP from ELSA LanCom DSL/10 DSL FW (isdn ch01) at the -fw {address}.
-use=fw : obtain IP from the firewall specified by -fw { type|address}.
-use=if : obtain IP from the -if {interface}.
-use=ip : obtain IP from -ip {address}.
-use=linksys : obtain IP from Linksys FW at the -fw {address} .
-use=maxgate-ugate3x00 : obtain IP from MaxGate UGATE-3x00 FW at the -f w {address}.
-use=netgear-rt3xx : obtain IP from Netgear FW at the -fw {address} .
-use=netopia-r910 : obtain IP from Netopia R910 FW at the -fw {add ress}.
-use=smc-barricade : obtain IP from SMC Barricade FW at the -fw {ad dress}.
-use=smc-barricade-alt : obtain IP from SMC Barricade FW (alternate con fig) at the -fw {address}.
-use=sohoware-nbg800 : obtain IP from SOHOWare BroadGuard NBG800 at t he -fw {address}.
-use=watchguard-soho : obtain IP from Watchguard SOHO FW at the -fw { address}.
-use=web : obtain IP from an IP discovery page on the web .
-use=xsense-aero : obtain IP from Xsense Aero at the -fw {address }.

-ip address : set the IP address to 'address'.

-if interface : obtain IP address from 'interface' (default: ppp0).
-if-skip pattern : skip any IP addresses before 'pattern' in the output of ifconfig {if}.

-web provider|url : obtain IP address from provider's IP checking page (defa ult: dyndns).
-web-skip pattern : skip any IP addresses before 'pattern' on the web provid er|url.

-fw address|url : obtain IP address from firewall at 'address'.
-fw-skip pattern : skip any IP addresses before 'pattern' on the firewall a ddress|url.
-fw-login login : use 'login' when getting IP from fw.
-fw-password secret : use password 'secret' when getting IP from fw.

-cmd program : obtain IP address from by calling {program}.
-cmd-skip pattern : skip any IP addresses before 'pattern' in the output of {cmd}.

-login user : login as 'user'.
-password secret : use password 'secret'.
-host host : update DNS information for 'host'.

-options opt,opt : optional per-service arguments (see below).

-{no}retry : retry failed updates. (default: noretry).
-{no}force : force an update even if the update may be unnecessary (d efault: noforce).
-timeout max : wait at most 'max' seconds for the host to respond (defa ult: 0).
-{no}syslog : log messages to syslog (default: nosyslog).
-facility {type} : log messages to syslog to facility {type} (default: daem on).
-priority {pri} : log messages to syslog with priority {pri} (default: not ice).
-mail address : e-mail messages to {address}.
-{no}exec : do {not} execute; just show what would be done (default: exec).
-{no}debug : print {no} debugging information (default: nodebug).
-{no}verbose : print {no} verbose information (default: noverbose).
-{no}quiet : print {no} messages for unnecessary updates (default: no quiet).
-help : this message (default: 0).
-{no}query : print {no} ip addresses and exit.

== CONFIGURING ddclient

The configuration file, ddclient.conf, can be used to define the
default behaviour and operation of ddclient. The file consists of
sequences of global variable definitions and host definitions.

Global definitions look like:
name=value [,name=value]*

For example:
daemon=5m
use=if, if=eth0
proxy=proxy.myisp.com
protocol=dyndns2

specifies that ddclient should operate as a daemon, checking the
eth0 interface for an IP address change every 5 minutes and use the
'dyndns2' protocol by default.

Host definitions look like:
[name=value [,name=value]*]* a.host.domain [,b.host.domain] [login] [password]

For example:
protocol=hammernode1, \
login=my-hn-login, password=my-hn-password myhost.hn.org
login=my-login, password=my-password myhost.dyndns.org,my2nd.dyndns.org

specifies two host definitions.

The first definition will use the hammernode1 protocol,
my-hn-login and my-hn-password to update the ip-address of
myhost.hn.org and my2ndhost.hn.org.

The second host definition will use the current default protocol
('dyndns2'), my-login and my-password to update the ip-address of
myhost.dyndns.org and my2ndhost.dyndns.org.

The order of this sequence is significant because the values of any
global variable definitions are bound to a host definition when the
host definition is encountered.

See the sample-ddclient.conf file for further examples.

== NIC specific variables and examples:
o 'dslreports1'

The 'dslreports1' protocol is used by a free DSL monitoring service
offered by www.dslreports.com.

Configuration variables applicable to the 'dslreports1' protocol are:
protocol=dslreports1 ##
server=fqdn.of.service ## defaults to www.dslreports.com
login=service-login ## login name and password registered with the s ervice
password=service-password ##
unique-number ## the host registered with the service.

Example ddclient.conf file entries:
## single host update
protocol=dslreports1, \
server=www.dslreports.com, \
login=my-dslreports-login, \
password=my-dslreports-password \
123456

Note: DSL Reports uses a unique number as the host name. This number
can be found on the Monitor Control web page.

o 'dyndns1'

The 'dyndns1' protocol is a deprecated protocol used by the free dynamic
DNS service offered by www.dyndns.org. The 'dyndns2' should be used to
update the www.dyndns.org service. However, other services are also
using this protocol so support is still provided by ddclient.

Configuration variables applicable to the 'dyndns1' protocol are:
protocol=dyndns1 ##
server=fqdn.of.service ## defaults to members.dyndns.org
backupmx=no|yes ## indicates that this host is the primary MX for the domain.
mx=any.host.domain ## a host MX'ing for this host definition.
wildcard=no|yes ## add a DNS wildcard CNAME record that points to {host}
login=service-login ## login name and password registered with the s ervice
password=service-password ##
fully.qualified.host ## the host registered with the service.

Example ddclient.conf file entries:
## single host update
protocol=dyndns1, \
login=my-dyndns.org-login, \
password=my-dyndns.org-password \
myhost.dyndns.org

## multiple host update with wildcard'ing mx, and backupmx
protocol=dyndns1, \
login=my-dyndns.org-login, \
password=my-dyndns.org-password, \
mx=a.host.willing.to.mx.for.me,backupmx=yes,wildcard=yes \
myhost.dyndns.org,my2ndhost.dyndns.org

o 'dyndns2'

The 'dyndns2' protocol is a newer low-bandwidth protocol used by a
free dynamic DNS service offered by www.dyndns.org. It supports
features of the older 'dyndns1' in addition to others. [These will be
supported in a future version of ddclient.]

Configuration variables applicable to the 'dyndns2' protocol are:
protocol=dyndns2 ##
server=fqdn.of.service ## defaults to members.dyndns.org
backupmx=no|yes ## indicates that this host is the primary MX for the domain.
static=no|yes ## indicates that this host has a static IP addre ss.
custom=no|yes ## indicates that this host is a 'custom' top-lev el domain name.
mx=any.host.domain ## a host MX'ing for this host definition.
wildcard=no|yes ## add a DNS wildcard CNAME record that points to {host}
login=service-login ## login name and password registered with the s ervice
password=service-password ##
fully.qualified.host ## the host registered with the service.

Example ddclient.conf file entries:
## single host update
protocol=dyndns2, \
login=my-dyndns.org-login, \
password=my-dyndns.org-password \
myhost.dyndns.org

## multiple host update with wildcard'ing mx, and backupmx
protocol=dyndns2, \
login=my-dyndns.org-login, \
password=my-dyndns.org-password, \
mx=a.host.willing.to.mx.for.me,backupmx=yes,wildcard=yes \
myhost.dyndns.org,my2ndhost.dyndns.org

## multiple host update to the custom DNS service
protocol=dyndns2, \
login=my-dyndns.org-login, \
password=my-dyndns.org-password \
my-toplevel-domain.com,my-other-domain.com

o 'easydns'

The 'easydns' protocol is used by the for fee DNS service offered
by www.easydns.com.

Configuration variables applicable to the 'easydns' protocol are:
protocol=easydns ##
server=fqdn.of.service ## defaults to members.easydns.com
backupmx=no|yes ## indicates that EasyDNS should be the secondary MX
## for this domain or host.
mx=any.host.domain ## a host MX'ing for this host or domain.
wildcard=no|yes ## add a DNS wildcard CNAME record that points to {host}
login=service-login ## login name and password registered with the s ervice
password=service-password ##
fully.qualified.host ## the host registered with the service.

Example ddclient.conf file entries:
## single host update
protocol=easydns, \
login=my-easydns.com-login, \
password=my-easydns.com-password \
myhost.easydns.com

## multiple host update with wildcard'ing mx, and backupmx
protocol=easydns, \
login=my-easydns.com-login, \
password=my-easydns.com-password, \
mx=a.host.willing.to.mx.for.me, \
backupmx=yes, \
wildcard=yes \
my-toplevel-domain.com,my-other-domain.com

## multiple host update to the custom DNS service
protocol=easydns, \
login=my-easydns.com-login, \
password=my-easydns.com-password \
my-toplevel-domain.com,my-other-domain.com

o 'hammernode1'

The 'hammernode1' protocol is the protocol used by the free dynamic
DNS service offered by Hammernode at www.hn.org

Configuration variables applicable to the 'hammernode1' protocol are:
protocol=hammernode1 ##
server=fqdn.of.service ## defaults to members.dyndns.org
login=service-login ## login name and password registered with the s ervice
password=service-password ##
fully.qualified.host ## the host registered with the service.

Example ddclient.conf file entries:
## single host update
protocol=hammernode1, \
login=my-hn.org-login, \
password=my-hn.org-password \
myhost.hn.org

## multiple host update
protocol=hammernode1, \
login=my-hn.org-login, \
password=my-hn.org-password, \
myhost.hn.org,my2ndhost.hn.org

o 'zoneedit1'

The 'zoneedit1' protocol is used by a DNS service offered by
www.zoneedit.com.

Configuration variables applicable to the 'zoneedit1' protocol are:
protocol=zoneedit1 ##
server=fqdn.of.service ## defaults to www.zoneedit.com
login=service-login ## login name and password registered with the s ervice
password=service-password ##
your.domain.name ## the host registered with the service.

Example ddclient.conf file entries:
## single host update
protocol=zoneedit1, \
server=www.zoneedit.com, \
login=my-zoneedit-login, \
password=my-zoneedit-password \
my.domain.name

ddclient version 3.6.2, written by Paul Burry, paul+ddclient@burry.ca

dexinou · Le 18/08/2006, à 19:41

tu tes trompé !
c pas deamon mais daemon

gizmo15 · Le 18/08/2006, à 19:47

ok autant pour moi!!

jai refait la premiere commande et sa me met:
Aug 18 20:04:59 localhost ddclient[9044]: WARNING: file /etc/ddclient.conf, line 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:05:59 localhost ddclient[9044]: WARNING: file /etc/ddclient.conf, line 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:07:00 localhost ddclient[9044]: WARNING: file /etc/ddclient.conf, line 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:08:01 localhost ddclient[12725]: WARNING: file /etc/ddclient.conf, line 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:08:01 localhost ddclient[12732]: WARNING: file /etc/ddclient.conf, line 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:08:07 localhost ddclient[12737]: WARNING: file /etc/ddclient.conf, line 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:09:01 localhost ddclient[12732]: WARNING: file /etc/ddclient.conf: file /etc/ddclient.conf must be accessible only by its owner (fixed).
Aug 18 20:09:01 localhost ddclient[12732]: WARNING: file /etc/ddclient.conf, line 4: unrecognized keyword 'deamon' (ignored)
Aug 18 20:17:01 localhost /USR/SBIN/CRON[12995]: (root) CMD ( run-parts --report /etc/cron.hourly)
Aug 18 20:36:03 localhost -- MARK --
Aug 18 20:45:55 localhost ddclient[13931]: WARNING: unable to determine IP address

et la deuxieme:
WARNING: unable to determine IP address

dexinou · Le 18/08/2006, à 19:50

poste un peu ton fichier de ddclient.conf !

gizmo15 · Le 18/08/2006, à 19:52

pid=/var/run/ddclient.pid
protocol=dyndns2
use=if, if=web
server=members.dyndns.org
login=gizmo15
password='mon mot de passe'
commando.homelinux.com

dexinou · Le 18/08/2006, à 19:53

ok fait un :

# chown ddclient:ddclient /etc/ddclient.conf

Dernière modification par dexinou (Le 18/08/2006, à 19:53)

gizmo15 · Le 18/08/2006, à 19:55

chown: `ddclient:ddclient': usager invalide

cest ce que jai apres cette commande

dexinou · Le 18/08/2006, à 19:57

dans ton crontab tu remplace sudo par root
puis un :
chown root:root /etc/ddclient.conf

Dernière modification par dexinou (Le 18/08/2006, à 19:59)

gizmo15 · Le 18/08/2006, à 19:59

dans le quoi? desoler mais je debute

je te remercie vraiment de ton aide

dexinou · Le 18/08/2006, à 20:00

C pas grave on va y arriver
sinon tu as essayer un :

# sudo dpkg-reconfigure ddclient

Dernière modification par dexinou (Le 18/08/2006, à 20:01)

dexinou · Le 18/08/2006, à 20:03

mais moi aussi j'ai l'impression de débuté quand je vois les messages d'erreurs.
Sur ma debian c facile !! sur ubuntu c autre chose mais c une très bonne distrib ^^

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 18/08/2006, à 15:56

prb ip fixe

#2 Le 18/08/2006, à 17:00

Re : prb ip fixe

#3 Le 18/08/2006, à 17:08

Re : prb ip fixe

#4 Le 18/08/2006, à 17:10

Re : prb ip fixe

#5 Le 18/08/2006, à 17:16

Re : prb ip fixe

#6 Le 18/08/2006, à 17:29

Re : prb ip fixe

#7 Le 18/08/2006, à 17:59

Re : prb ip fixe

#8 Le 18/08/2006, à 18:24

Re : prb ip fixe

#9 Le 18/08/2006, à 18:33

Re : prb ip fixe

#10 Le 18/08/2006, à 19:04

Re : prb ip fixe

#11 Le 18/08/2006, à 19:10

Re : prb ip fixe

#12 Le 18/08/2006, à 19:23

Re : prb ip fixe

#13 Le 18/08/2006, à 19:31

Re : prb ip fixe

#14 Le 18/08/2006, à 19:34

Re : prb ip fixe

#15 Le 18/08/2006, à 19:40

Re : prb ip fixe

#16 Le 18/08/2006, à 19:41

Re : prb ip fixe

#17 Le 18/08/2006, à 19:47

Re : prb ip fixe

#18 Le 18/08/2006, à 19:50

Re : prb ip fixe

#19 Le 18/08/2006, à 19:52

Re : prb ip fixe

#20 Le 18/08/2006, à 19:53

Re : prb ip fixe

#21 Le 18/08/2006, à 19:55

Re : prb ip fixe

#22 Le 18/08/2006, à 19:57

Re : prb ip fixe

#23 Le 18/08/2006, à 19:59

Re : prb ip fixe

#24 Le 18/08/2006, à 20:00

Re : prb ip fixe

#25 Le 18/08/2006, à 20:03

Re : prb ip fixe

Pied de page des forums