SEO

I have a computer with two interfaces, a wired and a wireless interface.
Both appear to function correctly, BUT:

After about half an hour, the dhcpcd for the wireless interface will start
querying the DHCP servers over and over again, twice every 3 seconds, and
will continue to do so until dhcpcd is killed or restarted, after which it
works correctly for half an hour again. A short log excerpt:

May 7 00:16:41 tree dhcpd: DHCPREQUEST for 172.16.24.9 from
00:0b:cd:74:1a:bf via eth1
May 7 00:16:41 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via
eth1
May 7 00:16:41 tree dhcpd: DHCPREQUEST for 172.16.24.9 from
00:0b:cd:74:1a:bf via eth1
May 7 00:16:41 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via
eth1
May 7 00:16:44 tree dhcpd: DHCPREQUEST for 172.16.24.9 from
00:0b:cd:74:1a:bf via eth1
May 7 00:16:44 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via
eth1
May 7 00:16:44 tree dhcpd: DHCPREQUEST for 172.16.24.9 from
00:0b:cd:74:1a:bf via eth1
May 7 00:16:44 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via
eth1
May 7 00:16:47 tree dhcpd: DHCPREQUEST for 172.16.24.9 from
00:0b:cd:74:1a:bf via eth1
May 7 00:16:47 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via
eth1
May 7 00:16:47 tree dhcpd: DHCPREQUEST for 172.16.24.9 from
00:0b:cd:74:1a:bf via eth1
May 7 00:16:47 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via
eth1

# ps -fC dhcpcd | cat
UID PID PPID C STIME TTY TIME CMD
root 8206 1 0 May05 ? 00:00:00 /sbin/dhcpcd -h fairy -t 5
eth0
root 20189 1 0 00:22 ? 00:00:00 /sbin/dhcpcd -h fairy -t
15 -m 2000 wlan0

The only thing I can see is that dhcpcd sets the hostname where it shouldn't
(gentoo doesn't allow for specifying a hostname per interface, or rather, it
will tack on -h `hostname` regardless), but that shouldn't affect the
renewal. The DHCP servers are set to ignore the hostname for gentoo hosts,
due to this design flaw.

This problem only occurs for the wlan0 interface, and not for eth0.

Anyone seen this, and know what could cause this misbehaviour?

Regards,
--
*Art

Arthur Hagen wrote:

> I have a computer with two interfaces, a wired and a wireless interface.
> Both appear to function correctly, BUT:
>
> After about half an hour, the dhcpcd for the wireless interface will start
> querying the DHCP servers over and over again, twice every 3 seconds, and
> will continue to do so until dhcpcd is killed or restarted, after which it
> works correctly for half an hour again. A short log excerpt:
>
> [...]
> # ps -fC dhcpcd | cat
> UID PID PPID C STIME TTY TIME CMD
> root 8206 1 0 May05 ? 00:00:00 /sbin/dhcpcd -h fairy -t 5
> eth0
> root 20189 1 0 00:22 ? 00:00:00 /sbin/dhcpcd -h fairy -t
> 15 -m 2000 wlan0
>
> The only thing I can see is that dhcpcd sets the hostname where it
> shouldn't (gentoo doesn't allow for specifying a hostname per interface,
> or rather, it will tack on -h `hostname` regardless), but that shouldn't
> affect the renewal. The DHCP servers are set to ignore the hostname for
> gentoo hosts, due to this design flaw.
>
> This problem only occurs for the wlan0 interface, and not for eth0.
>
> Anyone seen this, and know what could cause this misbehaviour?

Just a wild guess, but couldn't it be so that the wireless connections time
out after a given period?

I'm running an IRC network with a couple of friends, and many - I would even
say "most" - of those who have a wireless LAN set-up at home ping out from
IRC multiple times per day, while those with a cabled LAN or a direct
connection to the internet have a more stable connection with the IRC
server.

Maybe it's something typical of WiFi... Don't know, really... :-/

--
*Aragorn*
(registered GNU/Linux user #223157)

Aragorn wrote:
> Arthur Hagen wrote:

>> This problem only occurs for the wlan0 interface, and not for eth0.
>>
>> Anyone seen this, and know what could cause this misbehaviour?
>
> Just a wild guess, but couldn't it be so that the wireless connections time
> out after a given period?
>
> I'm running an IRC network with a couple of friends, and many - I would even
> say "most" - of those who have a wireless LAN set-up at home ping out from
> IRC multiple times per day, while those with a cabled LAN or a direct
> connection to the internet have a more stable connection with the IRC
> server.
>
> Maybe it's something typical of WiFi... Don't know, really... :-/

We did had trouble with wifi-scanners, that they lost connection quite
many times and at the worst time, but after a whiles experimentation it
seemed that the trouble was the default power save mode that caused all
the dropped connections.

I never had this kind of trouble with my laptop, which I never used with
wired network, so I more believe it has to do with settings than wifi.


--

//Aho

Aragorn <aragorn@chatfactory.invalid> wrote:
> Arthur Hagen wrote:
>
>> I have a computer with two interfaces, a wired and a wireless
>> interface. Both appear to function correctly, BUT:
>>
>> After about half an hour, the dhcpcd for the wireless interface will
>> start querying the DHCP servers over and over again, twice every 3
>> seconds, and will continue to do so until dhcpcd is killed or
>> restarted, after which it works correctly for half an hour again.
>> [...]
>> This problem only occurs for the wlan0 interface, and not for eth0.
>>
>> Anyone seen this, and know what could cause this misbehaviour?
>
> Just a wild guess, but couldn't it be so that the wireless
> connections time out after a given period?
>
> I'm running an IRC network with a couple of friends, and many - I
> would even say "most" - of those who have a wireless LAN set-up at
> home ping out from IRC multiple times per day, while those with a
> cabled LAN or a direct connection to the internet have a more stable
> connection with the IRC server.
>
> Maybe it's something typical of WiFi... Don't know, really... :-/

Nah, the wireless connection stays up. It's just the DHCP renewal requests
that suddenly happen again and again.

Perhaps it has something to do with the DHCP request being broadcast, and
thus received on BOTH interfaces, and dhcpcd not liking that the first reply
is on eth0 (simply because wired ethernet is faster than wifi)? But if so,
then why does the original request work, and only the renews fail?

For now, my workaround is to set the lease period for this address to a
ridiculously high amount. Unfortunately, that's not a good workaround, if I
ever take the laptop roaming into somewhere which uses the same private IP
range.

Regards,
--
*Art

Arthur Hagen wrote:

> Aragorn <aragorn@chatfactory.invalid> wrote:
>> Arthur Hagen wrote:
>>
>>> I have a computer with two interfaces, a wired and a wireless
>>> interface. Both appear to function correctly, BUT:
>>>
>>> After about half an hour, the dhcpcd for the wireless interface will
>>> start querying the DHCP servers over and over again, twice every 3
>>> seconds, and will continue to do so until dhcpcd is killed or
>>> restarted, after which it works correctly for half an hour again.
>>> [...] This problem only occurs for the wlan0 interface, and not for
>>> eth0.
>>>
>>> Anyone seen this, and know what could cause this misbehaviour?
>>
>> Just a wild guess, but couldn't it be so that the wireless
>> connections time out after a given period?
>>
>> I'm running an IRC network with a couple of friends, and many - I
>> would even say "most" - of those who have a wireless LAN set-up at
>> home ping out from IRC multiple times per day, while those with a
>> cabled LAN or a direct connection to the internet have a more stable
>> connection with the IRC server.
>>
>> Maybe it's something typical of WiFi... Don't know, really... :-/
>
> Nah, the wireless connection stays up. It's just the DHCP renewal
> requests that suddenly happen again and again.
>
> Perhaps it has something to do with the DHCP request being broadcast, and
> thus received on BOTH interfaces, and dhcpcd not liking that the first
> reply is on eth0 (simply because wired ethernet is faster than wifi)? But
> if so, then why does the original request work, and only the renews fail?
>
> [...]

Perhaps you should file a bug report then. Might be nice if they get it
fixed before 2008.0 becomes official. ;-)

--
*Aragorn*
(registered GNU/Linux user #223157)