Hi all,

Just putting some thoughts down and maybe it'll help with a situation.

At home, I was using HE Tunnelbroker to connect my OpenWRT router to
the ipv6 network. This worked well, it served ipv6 addresses to my
systems, however Google blocks a lot of Tunnelbroker traffic, as do
other sites, which makes it unreliable.

The idea is to use something like Wireguard to create an ipv4 tunnel
between OpenWRT and the VPS and use either part of the /64 subnet or a
fd77:: network.

Obviously, the OpenWRT router would have to give out ipv6 addresses.
Any suggestions with this? Anyone tried similar or have a better method?
--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23
--- SBBSecho 3.23-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)

On 1/6/2025 20:10, Nigel Reed wrote:

Hi all,

Just putting some thoughts down and maybe it'll help with a situation.

At home, I was using HE Tunnelbroker to connect my OpenWRT router to
the ipv6 network. This worked well, it served ipv6 addresses to my
systems, however Google blocks a lot of Tunnelbroker traffic, as do
other sites, which makes it unreliable.

The idea is to use something like Wireguard to create an ipv4 tunnel
between OpenWRT and the VPS and use either part of the /64 subnet or a
fd77:: network.

Obviously, the OpenWRT router would have to give out ipv6 addresses.
Any suggestions with this? Anyone tried similar or have a better method?

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...

I'm unsure about IPv6 providers, like to rent a /48 /52 /56 even a /60
(o Lord, what would I give for native /60) I guess a search for that on
you region on Google would yield something.

--
Hasya la Vista Baby!
David G
SysOp @SkyNet BBS (bbs.skynetbbs.com:20023)

--- Mystic BBS/NNTP v1.12 A48 (Linux/64)
* Origin: SkyNet BBS Colombia bbs.skynetbbs.com:20023 (4:930/1)

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)