Can you has crunchy tacos?
----
Looking at your log, you are using dnsmasq, and radvd, makes no sense to use them together.
You can have dnsmasq hand out your IPV6 stuff rather than radvd and it can tie it back to the ipv4 lease so it combines the dns too.
You shouldn't have to turn off your firewall and you shouldn't have to put the adapter in promisc mode, it should auto do that when you turn on ipv6 from the webif.
The most important part is figuring out what your lan is, what your wan is, and what your wifi's are.
Than you use the custom dnsmasq section and put something like this in the custom config area...
The part you need to check is eth0, I don't know what your WAN (outward facing port that goes to the router) is.
I have to use a custom config file for IPv6 to work.
dhcp6c custom
-------------
interface eth0 {
send ia-pd 0;
send rapid-commit;
script "/sbin/dhcp6c-state";
};
id-assoc pd 0 {
prefix ::/64 infinity;
prefix-interface br0 {
sla-id 0;
sla-len 0;
};
};
id-assoc na 0 { };
---------------
This sends out a request via eth0 and assigns that to br0.
Oddly enough, my actual ipv6 address is never assigned to eth0, but it does calculate the correct prefix and assign it to br0 which means it is being assigned an address but for some reason (unfinished scripts, etc.) it doesn't actually assign it to the ousland wan interface When looking with ifconfig.
----
Using it this way you should be able to turn off radvd completely and all your clients will get ipv4 and ipv6 and their names will be added into the local dns cache.
Last edited by roadrun777 on Thu Apr 04, 2019 14:38; edited 1 time in total
Hi. Sorry for the long hold up, but i am back to let you all know that i beleive i finally got it working. I left it disabled for a while and went the dnsmasq route in getting ipv6 to work.
Also, @Per Yngve Berg you were short one s on that stateless. i was too careless and lost internet when i did the usual "copy and paste" in my copypasta adventures. In Linux land.
Mediacom is not supporting IPv6 yet and here is response from support: "While you should be able to receive an IPv6 address, Mediacom has not begun to offer the technical support required for these addresses just yet. Unfortunately, there is no word on when Mediacom will make the shift to fully supporting these addresses at this time". _________________ Netgear R7800
Mediacom is not supporting IPv6 yet and here is response from support: "While you should be able to receive an IPv6 address, Mediacom has not begun to offer the technical support required for these addresses just yet. Unfortunately, there is no word on when Mediacom will make the shift to fully supporting these addresses at this time".
That's not correct. I have Mediacom and I'm using IPv6. They've had IPv6 for years now.
One thing to check is that you've got the right prefix set up. Mediacom recently went to giving us a /56 instead of a /64. See here:
https://www.dslreports.com/forum/r32407538-
I'd be happy to post my configuration if you like, though I'm running an R7500v2. I can't imagine it'd be much different in terms of setup.
According to MedicomChad guru the prefix /56 for the residential accounts is not sticky and "will still be dynamic in much the same way as the IPv4 have been".
So, it will be not naturally and reliably supported by Mediacom and can stop working any minute. _________________ Netgear R7800
Here are screenshots of the relevant sections of my setup. I've got my network set to force OpenDNS to everyone, but you could obviously change that.
I also did a nvram erase when I updated to Kong's 40270M build. I had not done that for a long time, probably never, and I'd started with his 30910M build back in 2016.
Try doing a full erase, re-input your settings, and use my setup. See if that gets you going.
