Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 4371  |
|  Nigel Reed to David Gonzalez  |
|  Re: Serving IPV6 from a remote host  |
|  14 Feb 25 15:36:13  |
 TZUTC: -0600 MSGID: 8232.fido_ipv6@1:124/5016 2c150d75 REPLY: 4:930/1 afdb8a9d PID: Synchronet 3.20c-Linux master/9ffa3a6e6 Feb 14 2025 GCC 11.4.0 TID: SBBSecho 3.23-Linux master/9ffa3a6e6 Feb 14 2025 GCC 11.4.0 BBSID: EOTLBBS CHRS: ASCII 1 NOTE: FSEditor.js v1.105 Re: Re: Serving IPV6 from a remote host By: David Gonzalez to All on Tue Jan 21 2025 14:39:09 > > The issue with doing anything with a prefix larger then /64 is that you > lose SLAAC, so forget about auto-configuration of devices, so think > carefully. > > I'd suggest asking your ISP, but I'm guessing if you're not using native > IPv6 it maybe because your ISP is one of those... Thanks for the suggestions. Yes, it's one of those ISPs. The good news is that Frontier is getting bought by Verizon, I hope, and I have a direct line to pretty much anyone in Verizon so I can see if I can push the consumer IPV6 issue a bit. It's been on trial for over 20 years, supposedly. --- SBBSecho 3.23-Linux * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016) SEEN-BY: 10/0 1 103/705 104/117 105/81 106/201 124/5016 128/187 153/7715 SEEN-BY: 154/110 214/22 218/0 1 215 700 860 940 226/30 227/114 229/110 SEEN-BY: 229/114 206 317 400 426 428 470 550 616 664 700 705 266/512 SEEN-BY: 280/464 291/111 320/219 322/757 342/200 396/45 633/280 902/26 PATH: 124/5016 218/700 229/426 |
[ << oldest | < older | list | newer > | newest >> ]