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...   [1702 / 1834] RSS
 From   To   Subject   Date/Time 
Message   Deon George    Arelor   Re: Just how big is IPv6?   January 3, 2025
 3:24 PM *  

  Re: Re: Just how big is IPv6?
  By: Arelor to Deon George on Thu Jan 02 2025 06:34 am

Howdy,

 > Take SLAAC as an example. It only works on a narrow set of scenarios and
 > can't convey all the information traditional DHCP does. On a regular IPv4
 > network where you want hosts to acquire a gateway, ntp server and dns server
 > upon boot, you use DHCP to provide them all with it. SLAAC only gets the
 > basics right (IP, gateway and dns) but if you are serious you are back to
 > DHCP. For even more fun, SLAAC only works within its narrow scenario IF it
 > operates on a network segment of EXACTLY a harcoded size.

Other than ntp, what else do you need from DHCP? Most (modern?) OS's these days
have NTP setup by default - so supplying clients with NTP details is often no
longer required.

If you wanted to limit the outgoing connections to an NTP server, to use your
NTP server, (and/or DNS server), then you can use NAT rules on your gateway for
that. (That's what I do anyway.)

I thought SLAAC worked pretty well - I work for a large company (many 1000's
employees), and the IT team turned on IP6 and nobody noticed - in fact I dont
recall any announcement about it. I only noticed when I started seeing
connections (from work) to my home server over IP6.

 > Then there is the fact my current home deployment is pretty much
 > non-replicable on IPv6 at all unless the ISP wants to cooperate. Hint: ISP
 > usually don't. Long story short, I have multiple local address spaces (think

 > If you want to break an IPv6 LAN into segments such as the above you are
 > supposed to pick the prefix provided to you by your ISP and then use DHCP-PD
 > (aka prefix delegation) to break your network into smaller prefixes and
 > assign each to each segment. This would be good and fancy if it worked, but

Hmm... its worked for me, but then my setup my not be as complicated as yours? I
get an /60 from my current ISP (my previous one gave me a /56) - and my router
dished it out as /64's to each lan interface as it needed to. At one point, I
dished out a /62 to a downstream router, and it split it up to /64s for it's lan
interfaces.

I've since turned all that off, as when I changed ISPs, my prefix changed and I
wanted to flatten my network a bit anyway.

I know not all ISPs here are providing IP6 to clients, but that's normally one
of the things I look for when changing. Even my mobile phone uses IP6 over IP4
from my mobile provider.


...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.0181 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