Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    IPV6    |    The convoluted hot-mess that is IPV6    |    4,612 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,579 of 4,612    |
|    Victor Sudakov to Alexey Vissarionov    |
|    Two ISPs and backup for a home network (    |
|    04 Jul 21 12:44:50    |
      REPLY: 2:5020/545 60dbd819       MSGID: 2:5005/49 60e14ba9       CHRS: CP866 2       TZUTC: 0700       TID: hpt/fbsd 1.9.0-cur 2019-12-05       Dear Alexey,              30 Jun 21 05:24, you wrote to me:               VS>>>> I know that my home router can advertise multiple global IPv6        VS>>>> prefixes into the LAN, but how will LAN hosts failover to the        VS>>>> backup gateway if the primary ISP fails? They will have IPv6        VS>>>> addresses from both blocks, which should they choose for their        VS>>>> outgoing src address?        AV>>> This is the preferred mode of operation, but it has (only) two        AV>>> disadvantages: 1. All hosts in the LAN must be able to do the        AV>>> switching|balancing on thy own (that means, run Linux; the        AV>>> BSD-style networking stack, like the one used in Windoze, has        AV>>> very limited functionality). 2. This may require some manual        AV>>> configuration on every of them. Not really a problem, but may        AV>>> be boring.        VS>> This is not feasible because most of those LAN hosts are        VS>> smartphones, smart TVs, vacuum cleaners, cameras and other IoT        VS>> devices.               AV> Most of these devices have Linux kernel, but crippled userspace.               VS>>>> With two IPv4 ISPs and NAT, the setup is rather trivial,        VS>>>> outgoing connections will work via either of the ISPs because        VS>>>> the hosts needn't be aware of the failure, and their src        VS>>>> private IP is always the same. Can anyone enlighten me?        AV>>> This is second option, but you'd lose the main advantage of        AV>>> IPv6: the use of publicly routed addresses.        VS>> Indeed. I don't like the idea of using NAT in IPv6 even if I        VS>> could. So what's the solution?               AV> For dumb devices, especially portable, I'd suggest using NPT.              How well does NPT (being stateless) work with FTP, SIP and other protocols       which embed addresses into payload?               AV> Fully        AV> functional computers may be connected to some other VLANs (two at once        AV> in your case) and configured to use real addresses.              Speaking of those fully functional computers in the LAN, do you mean the setup       when there is a script pinging some outside hosts/interfaces and modifying the       IPv6 routing table, or something more advanced and interesting?              Victor Sudakov, VAS4-RIPE, VAS47-RIPN       --- GoldED+/BSD 1.1.5-b20170303-b20170303        * Origin: Ulthar (2:5005/49)       SEEN-BY: 1/123 30/0 50/109 80/1 90/1 105/81 120/340 123/131 154/10       SEEN-BY: 221/1 6 226/30 227/702 229/424 426 550 700 1016 240/1120       SEEN-BY: 240/5832 249/206 317 400 261/38 280/464 5555 282/464 1038       SEEN-BY: 301/0 1 101 113 812 317/3 322/757 342/200 460/58 463/68 467/239       SEEN-BY: 467/888 633/280 712/848 920/1 5000/111 5001/100 5005/49 53       SEEN-BY: 5015/46 5020/715 830 846 1042 2047 2140 4441 5053/54 5058/104       SEEN-BY: 5064/56 5083/1 444       PATH: 5005/49 5020/1042 301/1 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca