Hi Daniel,
NM needs a lot of fixes and improvements, but I think that in this
case, it is completely innocent.
Your dhcp server is too lazy, as you can see: it only answered for the
initial DHCPDISCOVER on the third attempt, the same for the other
messages of the DHCP sequence.
Maybe you should
2010/1/11 José Queiroz zekk...@gmail.com:
Hi Daniel,
NM needs a lot of fixes and improvements, but I think that in this
case, it is completely innocent.
Your dhcp server is too lazy, as you can see: it only answered for the
initial DHCPDISCOVER on the third attempt, the same for the other
Hi,
On Mon, 11 Jan 2010, Benoit Boissinot wrote:
I've seen cases (wired network) where the communication actually work
only about 60 seconds after the the interface it brought up (I think
it has to do with some interaction with the switches). Maybe that's
the case here?
This is often caused
2010/1/11 Sven Nielsen p...@svennielsen.de:
Ask the dhcp team on your campus why they are giving away DHCP leases
for 3! days (286274 seconds):
Jan 10 21:40:12 DHCPACK of 149.106.215.247 from 149.106.192.253
Jan 10 21:40:13 bound to 149.106.215.247 -- renewal in 286274
seconds.
Maybe the
On Ubuntu 9.10 it appears you can edit the file /etc/dhcp3/dhclient.conf and
uncomment the line timeout in the file and increase it to say 180 seconds.
These values then get copied into /var/run/nm-dhclient-{interface-name}.conf
and that is the config file used by nm. This would be a hack and
Am Montag, den 11.01.2010, 17:02 -0200 schrieb José Queiroz:
I understand that, if the address pool is exausted, the DHCP server
should respond immediatelly with a DHCPNACK, and not start a ping
sweep to find free addresses.
from dhcpd.conf
José Queiroz wrote:
NM needs a lot of fixes and improvements, but I think that in this
case, it is completely innocent.
Your dhcp server is too lazy, as you can see: it only answered for the
initial DHCPDISCOVER on the third attempt, the same for the other
messages of the DHCP sequence.
I
Sven Nielsen wrote:
Ask the dhcp team on your campus why they are giving away DHCP leases
for 3! days (286274 seconds):
I've heard that 3 days is the Microsoft default. The IT department is a
Microsoft shop, so that probably explains it. ;)
___
John Mahoney wrote:
On Ubuntu 9.10 it appears you can edit the file /etc/dhcp3/dhclient.conf
and uncomment the line timeout in the file and increase it to say 180
seconds.
Thanks for the suggestion! Sadly, it didn't work.
I'm running Ubuntu 9.10 too, and I do indeed see that the config file
Yeah too good to be true. I see two ways to change the timeout.
1.Change this - /NetworkManager/src/dhcp-manager/nm-dhcp-manager.c:#define
NM_DHCP_TIMEOUT 45 /* DHCP timeout, in seconds */
OR
2. call this function somehere?
/NetworkManager/src/nm-device-olpc-mesh.c:
On Tue, Jan 12, 2010 at 1:02 AM, John Mahoney jmaho...@waav.com wrote:
Yeah too good to be true. I see two ways to change the timeout.
1.Change this - /NetworkManager/src/dhcp-manager/nm-dhcp-manager.c:#define
NM_DHCP_TIMEOUT 45 /* DHCP timeout, in seconds */
OR
2. call this function
On Tue, Jan 12, 2010 at 1:22 AM, John Mahoney jmaho...@waav.com wrote:
On Tue, Jan 12, 2010 at 1:02 AM, John Mahoney jmaho...@waav.com wrote:
Yeah too good to be true. I see two ways to change the timeout.
1.Change this - /NetworkManager/src/dhcp-manager/nm-dhcp-manager.c:#define
12 matches
Mail list logo
