News: This forum is now permanently frozen.
Pages: [1]
Topic: dhclient on WAN supporting DHCPFORCERENEW (RFC3203)?  (Read 1891 times)
« on: August 24, 2013, 16:02:32 »
mikeboss *
Posts: 11

swisscom are deploying a new product called "Business Connect" and during a conversation with a swisscom engineer, he mentioned to me that it is mandatory for this new service (DSL&VoIP) to work reliable that the gateway on the customer's site needs to be able to understand the DHCPFORCERENEW message (RFC3203). does anybody know if m0n0wall can handle this DHCP command?

thanks!


regards,
michael

http://bosshard.be
« Last Edit: August 26, 2013, 10:26:05 by mikeboss »
« Reply #1 on: August 26, 2013, 06:29:51 »
Lee Sharp *****
Posts: 517

This is a 12 year old standard, so I see no reason that it would NOT be supported, but I also see no proof that is is supported.
« Reply #2 on: August 26, 2013, 09:06:00 »
mikeboss *
Posts: 11

see? this my problem. there's no hard evidence to be found anywhere... I didn't even find out how to set up a DHCP server which is capable of sending a DHCPFORCERENEW message. otherwise I would have tested it and see if m0n0wall will accept it...
« Last Edit: August 26, 2013, 11:12:17 by mikeboss »
« Reply #3 on: August 26, 2013, 17:10:10 »
Lee Sharp *****
Posts: 517

Actually, I believe that m0n0wall does send a forcerenew packet.  This is because if you go to DHCP leases, pick an IP, and assign it a static, the device often immediately picks up the new IP address, even if the lease is not close to expiring.

So, I strongly suspect you are fin, but the only way to know is to test.
« Reply #4 on: August 26, 2013, 22:55:00 »
mikeboss *
Posts: 11

I just tested this (m0n0wall acting as DHCP server and another m0n0wall as client). unfortunately, I can't confirm your findings. the client m0n0 didn't get a new IP address until I initiated a release/renew manually. both m0n0walls were running on version 1.34.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines