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 |
|
||||||
From | To | Subject | Date/Time | |||
![]() |
Arelor | Deon George | Re: Just how big is IPv6? |
January 2, 2025 6:34 AM * |
||
Re: Re: Just how big is IPv6? By: Deon George to Arelor on Fri Dec 27 2024 08:03 am > I actually like it, I think it provides more benefits than IP4 - but the > only hurdle is that both are still in play. > If only IPv6 were available, it would be a nightmare. So much IPv6 stuff is half-baked at best. 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. 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 192.168.1.0/24 for IoT, 192.168.2.0/24 for my father's junk, 192.168.3.0/24 for surveillance apliances... you get the idea). 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 a) your ISP needs support proper prefix delegation, and so many just don't. b) it sucks that you need cooperation from an external entity in order to properly administrate your internal network. And yes, I am aware I could use local addressing, but that removes the advertising point of having everything in ipv6 be Internet routable by default. This gets so bad I have seen very nasty patchwork done in order to properly separate IPv6 segments, such as NAT66 (wtf?!). -- gopher://gopher.richardfalken.com/1/richardfalken --- SBBSecho 3.23-Linux * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (618:250/24) |
||||||
|
Previous Message | Next Message | Back to Computer Support/Help/Discussion... <-- <--- | Return to Home Page |
![]() Execution Time: 0.0151 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. |