1. Forum
  2. Fidonet
  3. IPV6

  • Serving IPV6 from a remote host

    From Nigel Reed@1:124/5016 to Fidonet.IPV6 on Tue Jan 7 01:10:44 2025
    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)
  • From David Gonzalez@4:930/1 to All on Tue Jan 21 14:39:09 2025
    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)
  • From Nigel Reed@1:124/5016 to David Gonzalez on Fri Feb 14 15:36:13 2025
    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)
  • From Gecko Maze@1:103/705 to Nigel Reed on Tue Jun 10 20:39:43 2025
    Re: Serving IPV6 from a remote host
    By: Nigel Reed to Fidonet.IPV6 on Tue Jan 07 2025 01:10 am

    I've played around with Wireguard quite a bit. I'm definitely not a total expert on it or IPv6 but do have IPv6 working on my home network.

    During my initial foray into Wireguard, I found that for IPv4, Wireguard doesn't work on Layer 2 where the broadcasts that DHCP needs would exist. IPv6 replaced broadcasts with multicast, which are still Layer 2 and most of the autoconfiguration of IPv6 relies on it, including RA/RS messages, SLAAC and DHCPv6.
    So I *think* you can make a Wireguard tunnel with IPv4 on the outside and 2 interfaces with IPv6 on the inside, you'll just have to assign the "inside" wgX addresses manually. E.g. fd77::1/64 and fd77::2/64. You might need to add fe80:: addresses manually as well.

    OpenVPN does work on Layer 2 if you use tap mode (Wireguard is like OpenVPN in tun mode), and DHCPv4 will definitely cross it if you have the tap junctioned into a bridge that a physical NIC is part of. I got a Windows file share working over an Internet connection with it once. I haven't played with IPv6 over OpenVPN yet.
    --- SBBSecho 3.27-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)