home bbs files messages ]

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,580 of 4,612   
   Dmitry Protasoff to Victor Sudakov   
   Two ISPs and backup for a home network (   
   04 Jul 21 13:51:28   
   
   REPLY: 2:5005/49 60e14a9f   
   MSGID: 2:5001/100.1 60e19d4e   
   CHRS: CP866 2   
   TZUTC: 0300   
   TID: hpt/w64-mvcdll 1.9.0-cur 2020-04-15   
   *** Answering a msg posted in area carbonArea (Carbon Area).   
      
   Hello, Victor!   
      
   Sunday July 04 2021 12:36, you wrote to me:   
      
    DP>> For example - rerouting traffic via VPN to get thru RKN's DPI.   
    DP>> Real life scenario :)   
      
    VS> Why would you need NAT for that? Get a VPN/tunnel provider who offers   
    VS> a global /64 or /56 or even a /48, like HE does.   
      
   With he.net you'll loose access to local google caches and to local CDNs.   
   With ipv4 I can forward only blocked subnetworks via VPN, with ipv6 and   
   without NAT66 I can't do that.   
      
    DP>> Yeah, but you can have "host" part the same for several uplinks   
    DP>> and change prefix only on NPTv6 gateway. It's the best ipv6 can   
    DP>> offer for you, sorry.   
      
    VS> Too bad and a bit unexpected. There are/were rather complex things   
    VS> like Mobile IPv6 and HMIP, and they have not thought of a simple   
    VS> failover?   
      
   Mobile IPV6 is an operator controlled tool to keep your IPv6 address intact.   
   But you are asking for exactly the opposite solution - to change your IPv6   
   address.   
      
    DP>> It adds more complexity and cannot be implemented easily in   
    DP>> userland across multiple OSes.   
      
    VS> OK, let's start anew with a simple setup. If there are two routers in   
    VS> a home LAN advertising different global prefixes, and one of them goes   
    VS> offline, will IPv6 end hosts detect that and remove the corresponding   
    VS> addresses from their configuration?   
      
   Yes but you'll still have single routing table and timeout for client to   
   remove dead ipv6 address from interface and routing table is large enough to   
   be unacceptable for general use.   
      
   Best regards,   
                dp.   
   --- GoldED+/W64-MSVC 1.1.5-b20180707   
    * Origin: No rest for the wicked (2:5001/100.1)   
   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/3 100 5005/49   
   SEEN-BY: 5015/46 5020/715 830 846 1042 2047 2140 4441 5053/54 5058/104   
   SEEN-BY: 5064/56 5083/1 444   
   PATH: 5001/100 5020/1042 301/1 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca