reseau en panne?

c.kumsta c.kumsta at free.fr
Lun 18 Fév 15:30:40 GMT 2008


Houlà .. j'ai un horrible doute ! :)
Tu ne tentes pas de lancer le serveur dhcp sur la machine qui est en IP dynamique sur le réseau ??
Car DHCP serveur a besoin de se binder sur un réseau déjà configuré (et oui, tu ne peux pas lancer un serveur
réseau sans que ta couche réseau soit configuré !! ;) ).

Ton serveur dhcp3 ne peut donc pas être la même machine qui va récupérer son IP sur le serveur DHCP ... c'est l'histoire
du serpent qui se mord la queue là ;)

++dune2

J Bond 0.07 a écrit :
> c.kumsta wrote:
>> Mais je ne vois pas l'interêt de la ligne :
>> "nameserver 194.206.126.253;nameserver 194.206.126.54;" ??
>> (je ne sais même pas si c'est "nameserver" est quelque chose de valide
>> dans un dhcpd.conf !)
>> étant donné que tu précises :
>> "option domain-name-servers 127.0.0.1;" dans le bloc.
>>
>> Si tu veux mettre les dns de ton FAI, il faut que tu le fasses dans
>> l'option "domain-name-servers" :
>> "option domain-name-servers 194.206.126.253, 194.206.126.54;"
>> (qui remplace bien entendu le "option domain-name-servers 127.0.0.1;")
>>
>> ++dune2
>>
>> J Bond 0.07 a écrit :
>>> Suite à la mise au point pécèdente de dhcpd.conf,
>>> et d'après /var/log/daemon.log, j'ai du rajouter les dns de mon fai:
>>>
>>> nameserver 194.206.126.253;nameserver 194.206.126.54;
>>> subnet 192.168.88.0 netmask 255.255.255.0 {
>>>     option routers 192.168.88.1;
>>>     range 192.168.88.1 192.168.88.254;
>>>     option domain-name-servers 127.0.0.1;
>>>     option domain-name "chikungugna.org";
>>>     option subnet-mask 255.255.255.0;
>>>     option ip-forwarding on;
>>>     default-lease-time 21600;
>>>     max-lease-time 43200;
>>> or j'ai les fautes suivantes que je ne sais pas interprèter:
>>> /etc/dhcp3/dhcpd.conf line 1: semicolon expected.
>>> name-server 194.
>>>             ^
>>> /etc/dhcp3/dhcpd.conf line 1: semicolon expected.
>>> name-server 194.206.126.253;name-server 194.
>>>                                         ^
>>> Configuration file errors encountered -- exiting
>>> mb at moustique:~$
>>>
>>> S'il te plait , patience j'apprends petit à petit à interpèter
>>> les fautes?
>>>
>>>
>>
>>
>> oui! c'est bien plus simple comme tu dis : 
> 
> subnet 192.168.88.0 netmask 255.255.255.0 {
>     option routers 192.168.88.1;
>     range 192.168.88.1 192.168.88.254;
>     option domain-name-servers 127.0.0.1, 194.206.126.253 ,194.206.126.54;
>     option domain-name "chikungugna.org";
>     option subnet-mask 255.255.255.0;
>     option ip-forwarding on;
>     default-lease-time 21600;
>     max-lease-time 43200;
> }
> 
> Mais : /var/log/daemon.log gueule :
> Feb 18 15:56:15 localhost dhcpd:
> Feb 18 15:56:15 localhost dhcpd:
> Feb 18 15:56:15 localhost dhcpd: Not configured to listen on any
> interfaces!
> Feb 18 16:01:28 localhost dhclient: DHCPDISCOVER on eth2 to
> 255.255.255.255 port 67 interval 5
> Feb 18 16:01:33 localhost dhclient: DHCPDISCOVER on eth2 to
> 255.255.255.255 port 67 interval 12
> Feb 18 16:01:45 localhost dhclient: DHCPDISCOVER on eth2 to
> 255.255.255.255 port 67 interval 13
> Feb 18 16:01:58 localhost dhclient: DHCPDISCOVER on eth2 to
> 255.255.255.255 port 67 interval 1
> Feb 18 16:01:59 localhost dhclient: No DHCPOFFERS received.
> Feb 18 16:01:59 localhost dhclient: Trying recorded lease 192.168.0.133
> Feb 18 16:01:59 localhost avahi-autoipd(eth2)[12542]: A routable address
> has been configured.
> Feb 18 16:01:59 localhost avahi-autoipd(eth2)[12542]: Callout UNBIND,
> address 169.254.5.88 on interface eth2
> Feb 18 16:01:59 localhost avahi-daemon[7323]: Leaving mDNS multicast
> group on interface eth2.IPv4 with address 169.254.5.88.
> Feb 18 16:01:59 localhost avahi-daemon[7323]: Joining mDNS multicast
> group on interface eth2.IPv4 with address 192.168.0.133.
> Feb 18 16:01:59 localhost avahi-daemon[7323]: Registering new address
> record for 192.168.0.133 on eth2.IPv4.
> Feb 18 16:01:59 localhost avahi-daemon[7323]: Withdrawing address record
> for 169.254.5.88 on eth2.
> Feb 18 16:02:02 localhost avahi-autoipd(eth2)[12542]: No longer a
> routable address configured, restarting probe process.
> Feb 18 16:02:02 localhost avahi-daemon[7323]: Withdrawing address record
> for 192.168.0.133 on eth2.
> Feb 18 16:02:02 localhost avahi-daemon[7323]: Leaving mDNS multicast
> group on interface eth2.IPv4 with address 192.168.0.133.
> Feb 18 16:02:02 localhost avahi-daemon[7323]: Interface eth2.IPv4 no
> longer relevant for mDNS.
> Feb 18 16:02:02 localhost dhclient: No working leases in persistent
> database - sleeping.
> Feb 18 16:02:03 localhost ntpd[7298]: Deleting interface #13 eth2:avahi,
> 169.254.5.88#123, interface stats: received=0, sent=0, dropped=0,
> active_time=2100 secs
> Feb 18 16:02:07 localhost avahi-autoipd(eth2)[12542]: Callout BIND,
> address 169.254.5.88 on interface eth2
> Feb 18 16:02:07 localhost avahi-daemon[7323]: Joining mDNS multicast
> group on interface eth2.IPv4 with address 169.254.5.88.
> Feb 18 16:02:07 localhost avahi-daemon[7323]: New relevant interface
> eth2.IPv4 for mDNS.
> Feb 18 16:02:07 localhost avahi-daemon[7323]: Registering new address
> record for 169.254.5.88 on eth2.IPv4.
> Feb 18 16:02:11 localhost avahi-autoipd(eth2)[12542]: Successfully
> claimed IP address 169.254.5.88
> Feb 18 16:02:19 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 3
> Feb 18 16:02:22 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 8
> Feb 18 16:02:30 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 18
> Feb 18 16:02:48 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 2
> Feb 18 16:02:50 localhost dhclient: No DHCPOFFERS received.
> Feb 18 16:02:50 localhost dhclient: No working leases in persistent
> database - sleeping.
> 
> mb at moustique:~$ sudo /etc/init.d/dhcp3-server start
>  * Starting DHCP server dhcpd3            [fail]
> mb at moustique:~$ sudo /etc/init.d/networking start
>  * Configuring network interfaces...            [ OK ]
> mb at moustique:~$
> 
> Si le reseau est pret?
> Il est possible que j(interdise l'attribution d'adresses dhcp par
> firestarter en les bloquant pour le moment en adresses fixes?
> 
> C'est plus facile pour le moment!
> 
> Je ne me suis pas encore penché sur firestarter en lignes de commande :
> sudo firestarter
> 
> 






Plus d'informations sur la liste de diffusion ubuntu-fr