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,823 of 4,612   
   Victor Sudakov to Alexey Vissarionov   
   List of IPv6 nodes   
   09 Jan 22 14:03:50   
   
   REPLY: 2:5020/545 61da7f32   
   MSGID: 2:5005/49 61da88e0   
   CHRS: CP866 2   
   TZUTC: 0700   
   TID: hpt/fbsd 1.9.0-cur 2019-12-05   
   Dear Alexey,   
      
   09 Jan 22 09:21, you wrote to me:   
      
    TK>>>>> I have a wireguard server running in my VPS (Ubuntu 20.04.3   
    TK>>>>> LTS). It is using a /112 of /64 for it's clients.   
    VS>>>> Do you mean to say you can have a /64 network on your VPS' main   
    VS>>>> interface and at the same time a /112 from the *same* *network*   
    VS>>>> on a wg0 interface? Is this even permitted by the OS?   
    AV>>> Yes - at least properly configured Linux allows this.   
    VS>> What do you mean by "properly configured"? You mean the   
    VS>> out-of-the-box configuration still does not allow this?   
      
    AV> Obviously.   
      
   What do you need to configure to enable this behaviour on Linux?   
      
    VS>> A Cisco router would not allow the same L2 network on two   
    VS>> different L3 interfaces IMHO, even if one of the prefixes is more   
    VS>> specific.   
      
    AV> That's a limitation of BSD-style IP stack.   
      
   Interestingly enough, FreeBSD 12.3 has just let me do exactly that (sorry, an   
   IPv4 example), without any additional configuration. The world is full of   
   wonders:   
      
   root@vas:~ # apply ifconfig lo{2,3}   
   lo2: flags=8049 metric 0 mtu 16384   
           options=680003   
           inet 192.168.13.1/24   
           groups: lo   
           nd6 options=29   
   lo3: flags=8049 metric 0 mtu 16384   
           options=680003   
           inet 192.168.13.129/25   
           groups: lo   
           nd6 options=29   
   root@vas:~ #   
   root@vas:~ # apply 'route get ' 192.168.13.2 192.168.13.200   
      route to: 192.168.13.2   
   destination: 192.168.13.0   
          mask: 255.255.255.0   
           fib: 0   
     interface: lo2   
         flags:    
    recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire   
          0         0         0         0     16384         1         0   
      
      route to: 192.168.13.200   
   destination: 192.168.13.128   
          mask: 255.255.255.128   
           fib: 0   
     interface: lo3   
         flags:    
    recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire   
          0         0         0         0     16384         1         0   
   root@vas:~ #   
      
      
      
   Victor Sudakov, VAS4-RIPE, VAS47-RIPN   
   --- GoldED+/BSD 1.1.5-b20170303-b20170303   
    * Origin: Ulthar (2:5005/49)   
   SEEN-BY: 1/123 15/0 30/0 50/109 80/1 90/1 105/81 106/201 120/340 123/131   
   SEEN-BY: 153/7715 154/10 221/1 6 226/30 229/110 424 426 428 550 664   
   SEEN-BY: 229/700 240/1120 5832 249/206 317 400 266/512 280/464 5555   
   SEEN-BY: 282/464 1038 301/0 1 101 113 812 317/3 320/219 322/757 342/200   
   SEEN-BY: 396/45 460/58 463/68 467/239 888 633/280 712/848 920/1 5000/111   
   SEEN-BY: 5001/100 5005/49 53 5015/46 5020/715 830 846 1042 2047 2140   
   SEEN-BY: 5020/4441 5054/8 5058/104 5064/56 5080/102 5083/1 444   
   PATH: 5005/49 5020/1042 301/1 229/426   
      

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


(c) 1994,  bbs@darkrealms.ca