Re: [CentOS] IPv6 mailing list?

2021-10-27 Thread Kenneth Porter

On 10/27/2021 9:24 AM, Benson Muite wrote:
There being no end-user IPv6 mailing list, it seems possible to set 
one up. 


I'd hoped that DSLReports would have a dedicated sub-forum but no luck. 
But I did discover that Reddit has one:


https://www.reddit.com/r/ipv6/

Meanwhile, I found the right search expression for what I want. IPv6 
redundant routing. Further refined by searching for "first hop". I doubt 
the ISP gateway has any support but it's something to ask for.


https://en.wikipedia.org/wiki/Virtual_Router_Redundancy_Protocol

And a related article that turned up in my search:

https://packetlife.net/blog/2011/apr/18/ipv6-neighbor-discovery-high-availability/


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] IPv6 mailing list?

2021-10-27 Thread Benson Muite

Maybe this is helpful:
https://www.ietfjournal.org/ietf-support-for-ipv6-deployment/

There is a working group mailing list where you might get an answer:
https://datatracker.ietf.org/wg/ipv6/about/

Seminars on IPv6 that may be of interest:
www.industrynetcouncil.org/past-webinars
https://industrynetcouncil.org/webinars

IANA seems to manage IPv6:
https://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xhtml

There being no end-user IPv6 mailing list, it seems possible to set one up.

On 10/27/21 5:28 PM, Kenneth Porter wrote:
Can anyone recommend an end-user IPv6 mailing list? (A web forum would 
also be acceptable.)


I've been looking at available lists and they all seem targeted at 
backbone players and ISPs. I'm looking for something where we can report 
and resolve problems with our ISPs.


For example, I just got an AT business connection and the Edgemark 
fiber gateway doesn't provide RA or prefix delegation. It assumes the 
customer equipment is all leaf nodes that are statically-configured. It 
doesn't recognize RA from the customer, either. So I'm using ndppd 
(added to EPEL7 this morning!) to proxy neighbor announcements through 
my CentOS7 gateway/firewall.


I have a backup/secondary C7 gateway and it got confused when the 
primary sent RA for the LAN-side subnet upstream to the common WAN link 
(via the radvd package) and the secondary added a default routing table 
entry pointing to the primary gateway instead of using its own 
statically-configured default gateway setting. That was a head-scratcher 
until I noticed my firewall logs on the main gateway showing dropped DNS 
packets from the secondary that should have been going to the ISP 
gateway. IPv6 DNS was failing on the secondary with timeouts (10 
seconds!) and I couldn't figure out what was eating the packets.


So I'm wondering how multiple gateways sharing a link are supposed to 
cooperate and inform each other without confusing each other about the 
desired topology.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] IPv6 mailing list?

2021-10-27 Thread Kenneth Porter
Can anyone recommend an end-user IPv6 mailing list? (A web forum would also 
be acceptable.)


I've been looking at available lists and they all seem targeted at backbone 
players and ISPs. I'm looking for something where we can report and resolve 
problems with our ISPs.


For example, I just got an AT business connection and the Edgemark fiber 
gateway doesn't provide RA or prefix delegation. It assumes the customer 
equipment is all leaf nodes that are statically-configured. It doesn't 
recognize RA from the customer, either. So I'm using ndppd (added to EPEL7 
this morning!) to proxy neighbor announcements through my CentOS7 
gateway/firewall.


I have a backup/secondary C7 gateway and it got confused when the primary 
sent RA for the LAN-side subnet upstream to the common WAN link (via the 
radvd package) and the secondary added a default routing table entry 
pointing to the primary gateway instead of using its own 
statically-configured default gateway setting. That was a head-scratcher 
until I noticed my firewall logs on the main gateway showing dropped DNS 
packets from the secondary that should have been going to the ISP gateway. 
IPv6 DNS was failing on the secondary with timeouts (10 seconds!) and I 
couldn't figure out what was eating the packets.


So I'm wondering how multiple gateways sharing a link are supposed to 
cooperate and inform each other without confusing each other about the 
desired topology.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos