Hello all

Ok this is strange, really!

Installed FC5, wireless ipw2200-firmware-3.0-2.noarch.rpm on a Toshiba Portege m200 - great!

However when running wireless:
1) '$> iwconfig eth1 essid etc' brings up the interface and then '$> dhclient' configures the network.
2) browse to router 192.168.1.1 using firefox & konqueror
3) browse the web for a few seconds / minutes and then it goes down
4) note: router is still reachable through browers and pingable

Last night I went on, connected to skype and when the
web went down skype stayed up for another hr or so!?! :-o

Below is the /var/log/message.
Question: Why is dhclient-script updating /etc/resolv.conf for eth0?

Any ideas are much appreciated
Thanks in advance
Graeme


uname -a:
Linux phi.devel.co.uk 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55 EDT 2006 i686 i686
i386 GNU/Linux

Here is the relevant /var/log/message extract, eth0 is wired n.work and eth1 wireless:

Sep 14 23:44:16 phi dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
Sep 14 23:44:16 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 6
Sep 14 23:44:16 phi dhclient: DHCPACK from 192.168.1.1
Sep 14 23:44:16 phi avahi-daemon[1929]: New relevant interface eth1.IPv4 for mDN
S.
Sep 14 23:44:16 phi avahi-daemon[1929]: Joining mDNS multicast group on interfac
e eth1.IPv4 with address 192.168.1.4.
Sep 14 23:44:16 phi avahi-daemon[1929]: Registering new address record for 192.1
68.1.4 on eth1.
Sep 14 23:44:17 phi NET[6871]: /sbin/dhclient-script : updated /etc/resolv.conf
Sep 14 23:44:17 phi dhclient: bound to 192.168.1.4 -- renewal in 35430 seconds.
Sep 14 23:44:22 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 14
Sep 14 23:44:36 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 20
Sep 14 23:44:56 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 10
Sep 14 23:45:06 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 11
Sep 14 23:45:17 phi dhclient: No DHCPOFFERS received.
Sep 14 23:45:17 phi dhclient: No working leases in persistent database - sleepin
g.
Sep 14 23:45:17 phi NET[6941]: /sbin/dhclient-script : updated /etc/resolv.conf
Sep 14 23:47:55 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 6
Sep 14 23:48:01 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 13
Sep 14 23:48:14 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 13
Sep 14 23:48:27 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 14
Sep 14 23:48:41 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 14
Sep 14 23:48:55 phi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 in
terval 1
Sep 14 23:48:56 phi dhclient: No DHCPOFFERS received.
Sep 14 23:48:56 phi dhclient: No working leases in persistent database - sleepin
g.

Why is dhclient-script updating /etc/resolv.conf for eth0?

Ok the question was my clue and managed to help solve this. The problem is that the command (dhclient) was used incorrectly. This happens...
The one that I should have used is '$> dhclient -1' which configures the network and exits. I.e. no daemon is run.

Hope this helps
Graeme