TZUTC: 1100   
   MSGID: 1343.fdn_ipv6@3:633/509 26449b31   
   REPLY: 2:280/5555 61dee636   
   PID: Synchronet 3.19a-Linux master/8f79438d2 Apr 24 2021 GCC 8.3.0   
   TID: SBBSecho 3.14-Linux master/8f79438d2 Apr 24 2021 GCC 8.3.0   
   COLS: 139   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.104   
     Re: List of IPv6 nodes   
     By: Michiel van der Vlist to deon on Wed Jan 12 2022 03:28 pm   
      
   Howdy,   
      
    >  de> I use /80's a lot, which in reality could be /96's but I'm being   
    >  de> generous to the network that I use the /80's on.   
    >   
    > But why? When you can have enough space to make /64 subnets?   
      
   Because in my use case, having a /64 for 2 or 3 hosts is a waste - and given   
   in that use case it is a manual config anyway, spliting up an already routed   
   /64 into smaller parts, is easier than routing multiple /64 through   
   intermediate hosts.   
      
    > And some thing will not work any more.   
      
   From an IP comms point of view, I've never not handing work anymore. From a   
   SLAAC point of view, sure - which was my earlier comment around simple setup.   
      
      
   ...ëîåï   
   --- SBBSecho 3.14-Linux   
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)   
   SEEN-BY: 1/123 15/0 90/1 105/81 106/201 120/340 123/131 153/7715 226/30   
   SEEN-BY: 229/110 424 426 428 550 664 700 240/5832 249/206 317 400   
   SEEN-BY: 266/512 282/1038 301/1 317/3 320/219 322/757 342/200 396/45   
   SEEN-BY: 633/267 280 281 410 412 416 509 640/1384 712/848 770/1   
   PATH: 633/509 280 229/426