What's new

separate default gateways for ip4 vs ip6

  • 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!

teknojnky

Senior Member
I have 2 routers,

the main internet router is on .1, it does NAT and multiwan. It does not do WIFI, DHCP or IPv6.

my asuswrt-merlin (380.57) is on .2 and does the DHCP and wifi access. The WAN port is not used.

I was able to add a static default route (0.0.0.0/0.0.0.0 > 192.x.x.1) which lets me ping public ips on the asus, out through my wan.

Pinging outside public ips work, however I haven't been able to get DNS to resolve.

I can ping 8.8.8.8 but can't ping www.google.com.


I was able to get dns ping working by disabling wan > connect dns automatically and manually setting dns servers.

But what I would really like to be able to do is, get my ip6 tunnelbroker tunnel working.

Using the asus as my network ip6 gateway, which then uses my multiwan gateway to create the ip6 tunnel over ip4.

I'm not sure it will be possible other than plugging my wan connection into the asus WAN port.

Any ideas or suggestions?
 
I am not completely sure what you are all trying to do.
One thing for sure is that the tunnel broker must be able to ping the IPv4 address of your tunnel endpoint.
 
after much hair pulling, removing my multi-wan, and factory defaulting asus-wrt, I figured out that my old dsl modem wasn't passing proto-41.

I had been running pppoe on the modem, with the modem passing the public ip for 10+ years, but eventually determined that the 'pseudo bridge mode' was the problem and I had to put the modem in full bridge mode and run the pppoe via asus-wrt wan settings.

Now, my only issues is accessing the old modem config screen @ 192.168.0.1 (which I could do previously with no problem).

I assume I need to figure out how to add the right route so the asus-wrt will know that 192.168.0.1 is on the wan interface but not the ppp0.

Or maybe add a secondary 192.168.0.2 ip to the wan interface.

I dunno, but at least finally my ipv6 tunnel is working.

I will mess with it another time.
 

Sign Up For SNBForums Daily Digest

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