Posted: Sun Sep 19, 2021 8:21 Post subject: HTTP HTTPS management question
I would like to know if anyone knows how to modify
settings in the file structure for management settings?
More specifically how to make dd-wrt open the mangement
pages with ipv6. I know it does already, but is there
a way to enable and disable it?
A little hard to understand what you are asking...
For ipv6 version, you probably need a global ipv6 address to make things easier... using the link local addresses fe80::/10 may not be bound to from the http server (ie it may not be told to respond to it)... just looking on an x86 version I have it does listen on all addresses...
The suggested way, the more permenant is to use:
nvram set http_enable=1
or similarly for https:
nvram set https_enable=1
1 means true and 0 means false (disable) then reboot the router....
If you want to do via command line to start:
httpd -n -p 80
or
httpd -S -m 443
or both
httpd -n -S -p 80 -m 443
to enable ipv6 from command line
nvram set ipv6_enable=1
(but do not forget to do things like radvd, dhcp6s, ...)
if you want pure linux ... call the daemons themselves ... dd-wrt is a customized linux distro..
pure linux for disabling ipv6 -- look up sysctl
sysctl -w net.ipv6.conf.all.disable_ipv6=1
sysctl -w net.ipv6.conf.default.disable_ipv6=1
I am not sure that dd-wrt saves the sysctl.conf file across boots (or if it regenerates it)
I have an asus rt-ac68u with stock firmware in media bridge mode. I can't
open the iov6 management page. Usually
with brackets. i.e.
http:[fe80::xxxx:xxxx:xxxx:xxxx]
It does, and yes I'm worried that it isn't
listening to ipv6 on the management page.
I guess to confirm that all asus oem and dd-wrt can be opened easily with its ipv6 address?
I noticed that ping skips the first query in windows command line. Packet loss. That's my issue. But no worries.
I'm trying to force it to use the whole of modules so ping and others to work.
Someone please confirm they can login web management page with ipv6 address in the form http://[fe80::xxxx:xxxx:xxxx:xxxx] on an asus wifi router with stock firmware.
Link local address are not forwarded by spec, but that does not mean that everyone honors the spec, so as long as they do not cross a router link-local should work
I just spun up an instance of the virtual network lab that I have access to and I was not able to connect to http using an ipv6 link local address (ie fe80::/10), it might be due to the virtual network, but pings work fine... looking at netstat on the router it says:
tcp 0 0 :::http :::* LISTEN
so it looks as though the daemon is listening, but it does respond to its global ipv6 address... based on a simple search:
I thought it was obvious to. dd-wrt and stock asus do not have the same behavior. Thanks for confirming. I'm worried because I want to force various levels of dd-wrt and asus oem because the first query of ping inherently fails. Thx 4 the code block.