AT2k Design BBS Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Computer Support/Help/Discussion...  <--  <--- Return to Home Page
   Networked Database  Computer Support/Help/Discussion...   [1687 / 1834] RSS
 From   To   Subject   Date/Time 
Message   Deon George    Warpslide   Re: Just how big is IPv6?   December 26, 2024
 9:00 AM *  

  Re: Re: Just how big is IPv6?
  By: Warpslide to Deon George on Wed Dec 25 2024 09:24 am

Howdy,

 > I initially tried setting my config to request a /62 (4 /64s) and /61 (8
 > /64s) but it didn't seem to work, not sure if its my EdgeRouter 4 or my ISP
 > that doesn't support them but a /48 works fine.

Yeah, I havent got to work out how the backend works - but I see a similar
result.

My ISP gives me a /60, and I've played around requesting a /63, /62, and I still
get the /60.

 > I could try slicing up one /64 into 4 /66s or something, not sure if my
 > router supports that, but could be a fun exercise to try and see what
 > happens.  I suppose I really don't need to be concerned with
 > hoarding/wasting such a "small" number of addresses.

For the most, and on a VLAN, you'd probably want to stick to a /64 - it'll makes
auto configuration easy - and just works. IE: Plug in device, select IP6 and
magically it gets one and routing.

Anything less than a /64, you'll need to manage the gateway and routing
yourself.

In my case, I play with docker - and containers can have their own IP6 address
on their own virtual network. Which is where I use /112s - still gives each
docker network 65,535 addresses, and you generally would only use a few on each
network :) And since a docker host can potentially have many networks, inside
it, I route the /88 to the docker host - manually configured on my router. In
reality, I could reduce this to a /96 or even smaller.

The first thing to help, is your gateway address is a link-local fe80::/10, not
the first (or last) address in the subnet (which we traditionally do with ip4),
and you get that from the device you are routing to after its IP6 stack is
running. Generally you dont need to configure the routing back, because it will
get that from SLAAC (/64 setup).

 > happens.  I suppose I really don't need to be concerned with
 > hoarding/wasting such a "small" number of addresses.

One of the things I'm liking, and it might just be a conincidence, I see many
less bot probs on IP6. The address space is just too big for somebody to probe
each one :)


...oEoN
--- SBBSecho 3.23-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (618:510/2)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Computer Support/Help/Discussion...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0138 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2025 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.1.250224