Not sure if this is a known issue or whatever;
- unable to access router admin via it's own local lan ipv6 address
ipv6 tunnel has been up and stable since I resolved my initial dsl modem issues (required full bridge mode and pptp on router).
on a whim I tried to access the router web admin via ipv6, using the "LAN IPv6 Address" as specified on the ipv6 tunnel config page. (this internal ipv6 ip to internal ipv6, not trying to access via wan)
I can ping the address fine.
In chrome you must create the url putting brackets around the ipv6 address;
http://[2001:12:34:56::1]
this results in error connection refused.
I assume that is probably because the web admin service is not bound to the ipv6 lan ip of the router.
I did not try disabling the ipv6 firewall (due to too much active using going on to disrupt connections), but I would hope the firewall would not block lan internal network ips from connecting to the router admin.
merlin 380.57 on rt-ac66u
- unable to access router admin via it's own local lan ipv6 address
ipv6 tunnel has been up and stable since I resolved my initial dsl modem issues (required full bridge mode and pptp on router).
on a whim I tried to access the router web admin via ipv6, using the "LAN IPv6 Address" as specified on the ipv6 tunnel config page. (this internal ipv6 ip to internal ipv6, not trying to access via wan)
I can ping the address fine.
In chrome you must create the url putting brackets around the ipv6 address;
http://[2001:12:34:56::1]
this results in error connection refused.
I assume that is probably because the web admin service is not bound to the ipv6 lan ip of the router.
I did not try disabling the ipv6 firewall (due to too much active using going on to disrupt connections), but I would hope the firewall would not block lan internal network ips from connecting to the router admin.
merlin 380.57 on rt-ac66u