latest DHCP changes broke

[frater]

My Copperjet modem can give its PPPoA-obtained WAN-IP to a DHCP-client on its ethernet. It needs a hostname for this. Somehow it is not seeing this hostname anymore. As it seems the DHCP-client is not giving its hostname anymore.

My copperjet now refuses to give its WAN-IP anymore.

This has been broken before and fixed a few years back.

[frater]

I found the previous ticket which was made in Mantis: http://www.dd-wrt.com/dd-wrtv2/bugtracker/view.php?id=2168

[frater]

​http://svn.dd-wrt.com:8000/dd-wrt/changeset/5853

[BrainSlayer]

fixed in r14568

[frater]

The behaviour is different. It now sees the hostname which is WAN in my case, but zipB still doesn't give me its WAN IP unless I tell it to give to '172.19.3.2' instead of 'WAN'. I'm sorry I can't give you a proper bug report. It's really the strange implementation of "ZipB" on my Copperjet which is the cause, but this workaround I wrote has been working for years.

I would appreciate it if you could take a second look and check if the DHCP-client is really behaving as it should.

[BrainSlayer]

its working as it should. the bug was caused by a small change in the dhcp client parameters which introduced a typo. its now working like before

[frater]

My copperjet router still doesn't recognizes the hostname of my router and keeps refusing it the Internet IP-address. DD-WRT gets stuck with 172.19.3.2

I'm now running SVN 14818, and I know what change broke it. The fix didn't fix it.

Before I go on holidays I will downgrade the firmware as I need to keep it going to access my services.....

[frater]

​http://svn.dd-wrt.com:8000/dd-wrt/changeset/14848

hoping Brainslayer reads this.....