What's new

Setting illegal WAN hostnames... how?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Raulete

New Around Here
Hello everybody and apologies if the question has already been asked.

My ISP requires the use of illegal hostnames (with a /) on the otherwise normal DHCP WAN interface to prevent customers from using routers different than the supplied ones. I had hoped the Merlin firmware would allow me to bypass this limitation from the original ASUS firmware. I have tried nvram set wan_hostname=VFHXXX/YYY and it seems to set the right value in NVRAM, but as soon as I touch the WEB GUI the value reverts to the one stored through the WEB GUI. Also, the router doesn't get an IP from the DHCP server, while my old wrt54gs works perfectly with dd-wrt.

I imagine the data from the WEB GUI are stored somewhere but couldn't find out where. Can anybody help me bypass the web gui data validation so as to be able of using the web gui and avoiding the nvram value from reverting back? Some script would be ideal, but I'm unsure where to set it.

Many thanks in advance!
 
es, I tried. The router won't get a valid wan IP as if though the Hostname was wrong (or the nvram parameter ignored) and then the wan_hostname in nvram will be overwritten as soon as I get near the wan configuration page on the Web gui or the wan section of the network map.
Many thanks for your help and reply!

Enviado desde mi D6603 mediante Tapatalk
 
Any help is appreciated, I'm really stuck and I like Merlin so much better than dd-wrt...

Enviado desde mi D6603 mediante Tapatalk
 
Try setting the value into wan0_hostname instead of wan_hostname followed by an nvram commit and reboot.
 
Hi! Thanks for the hint! With this, the wan Hostname is accepted, doesn't change, and even appears in the Web GUI but the router still doesn't get a valid IP, as if the setting was wrong. I also tried wan_wan_interface. Once the router has completely booted, I need to login and run udhcpc -h VFHXXX/YYY manually. I can't completely understand why, but this always works so I'm thinking of setting some script to run this every time the wan interface goes up...

Enviado desde mi D6603 mediante Tapatalk
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top