301–310 of 461 posts
Using Hexadecimal instead gives over 6.5 times as many possibilities in the same 4 characters - should be more than adequate. I know airline systems have a lot of legacy code so it might be difficult, but at least logistically (having adequate space to print / display them), and for humans to deal with it's not too difficult.
Earlier quoted context omitted.
> Do you know enough to assign addresses in a way that you, not your router, wants? If I want to manually assign addresses it's still pretty simple, but in the end I normally just don't care. I don't want to know what IP my printer is, I just want to reach it. Which isn't a challenge at all. Even for things at my home that are IPv4 only they're practically all DHCP. Because there's little reason to ever really care a…
> as mine only took me an hour or so while yours took multiple days. Yeah, because the first time I had no idea what I was doing, except vague feelings about ipv4 works. Did you factor in your pre existing ipv6 knowledge when you counted just an hour? > Network Prefix Translation can be done pretty easily. What's "easily"? How many services do I need to setup? Some other helpful HNer tried to explain to me once and t…
Your standard was "It's unusable on your fucking home network."
I've set up and managed IPv6 at work before, yes. I don't know if I'd call them "complex" networks though. Either way I set it up at home several years before. And I had been running IPv6 at home before I even bothered setting it up in a way I wanted, as my ISP's box previously had a decently competent SLAAC and IPv6 firewall setup in their CPE router. So that took me 0 minutes of time past plugging it in.
As for this disdain of running such complicated systems like "DNS", so many things support mDNS these days and plenty of home routers will automatically update their local DNS with DHCP entries. I didn't have to manually configure a DNS entry for my printer, I just gave it the hostname "brother" when I first set it up and now when I need to add it, I just do "brother" on a new computer and boom it finds it wherever it is. If I want to check the toner level, I open a browser and go to http://brother and its there. And even though I've radically changed my networking setups over the years, all my configurations pointing to "brother" still just work.
> What's "easily"?
https://docs.netgate.com/pfsense/en/latest/nat/npt.html
There's seven configuration options here including the Disable/Enable checkbox and a description field.
If you're using ip6tables on your router, it is just two commands for a POSTROUTING and PREROUTING nat rules.
ip6tables -t nat -A POSTROUTING -o eth0.99 -j NETMAP --to 2607:xxx::/64 -s fd12:3456::/64
ip6tables -t nat -A PREROUTING -i eth0.99 -j NETMAP -d 2607:xxx::/64 --to fd12:3456::/64
From the sibling comment:
> No, with ipv4 i can just change the default route :)
Are you suggesting you're running around and changing the default route on all the devices on your network when a gateway goes down? What a nightmare. Just have your router have multiple WAN connections and have it do the failover for you.
> I have absolutely no problem remembering the last byte of any machine on my network
If you want, you can do the same with IPv6. You could set your stuff to have your IP addresses be fd12:3456::1, then fd12:3456::2, then fd12:3456::3, then fd12:3456::4, then fd12:3456::5, etc. Remembering 123456 as your home ULA prefix isn't too challenging, is it? You can then set up an NPT rule like the one above on your router to translate this prefix fd12:3456::/64 with whatever your public prefix is from your ISP. Most wouldn't do this though, as its essentially the Fisher Price of networking designs.
Earlier quoted context omitted.
Reminds me of the line that network engineers love implementing IPv6 so much they have been doing it for years
We could also have bumped 255.255.255.255 to 999.999.999.999 = 1 trillion IP addresses, easy-to-remember and backward compatibility with legacy devices. Modern clients and servers get IP addresses in these new whole IP ranges and can communicate together. Relatively easy to adapt the code of modern software also since it's about removing a restriction from a client-perspective. Load-balancers and legacy clients use I…
Earlier quoted context omitted.
> it’s actually “IP + Port#” that is globally unique So which globally unique box is 192.168.1.1:443? Can you point to exactly one device out there with that IP:PORT combo? There's probably hundreds of millions of that IP:Port combination currently running and listening. Which globally unique box is 8.8.8.8:53? You think there's seriously just one network adapter listening for traffic at 1.1.1.1:53? These aren't "bro…
Well the 192 case would probably have an external IP + Port uniquely mapped to it in the router’s NAT table. I think you’re missing the larger point though. No one said IPs are exclusively used as GUIDs. Just that they are used as GUIDs, which they are in the majority of cases, and those GUIDs are re-assigned over time. My Macbook Pro currently has unique IP + Port, associated with a single process listening to it ov…
Only on really crappy NAT implementations. My home router can have hundreds of thousands of NAT states, and yet there are only ~61k high number ports. How do you think that works?
Because it is not just "external IP at this port goes to this LAN host". Its the whole session information, SRC_PORT, DEST_PORT, SRC_IP, DEST_IP, all get figured into it.
At this moment there are several NAT states in my home router that share the same public IP:PORT combination, going to different LAN IP:PORT combinations.
An IP address is not globally unique. An IP:PORT is not globally unique. Treating them as globally unique shows a misunderstanding of networking concepts. They're often unique to a single host, but that's not a requirement.
Once again, do you really think there's a single network adapter out there that has 8.8.8.8:53?
Earlier quoted context omitted.
Hey they are inventing NAT. Nice.
Wait, how are they doing that? My mental idea of NAT is that it dyanmically links (address × port) pairs to local addresses. What would be the "port" in the case of flight numbers?
Earlier quoted context omitted.
Enormous path dependance. There's a photo in that article that shows the problem: the flip-tab sign that has space for four numerical digits. I was thinking they could just switch from 0-9 to 0-9A-Z but that photo showed why that would be a disaster. Plus any solution has to be approved for use worldwide. Fortunately the two-digit IATA codes have already switched to 0-9A-Z (e.g. JetBlue is B6) so allowing constrained…
> I was thinking they could just switch from 0-9 to 0-9A-Z but that photo showed why that would be a disaster. I guarantee those signs could easily be updated for that. They’re built to allow replacement of each cell and routinely do so since cells break. Switching to 0-9A-Z would take one night for them.
Earlier quoted context omitted.
Have you ever changed the static IP address of a computer? You just “recycled” a “globally unique” ID. Recycling unique IDs (more precisely: changing the underlying thing the ID points to) is not impossible; there’s lots of pathological failure modes; for certain ID-spaces it’s kinda a required use case; so we have to deal with it.
IP addresses (especially IPv4) are not even supposed to be globally unique. How many 192.168.1.1 devices are out there? How many different distinct physical boxes respond to traffic going to 1.1.1.1?
if you take someone elses public IPv4 address and they're using it, neither one of you will be functional, and they will come knocking on your door.
Earlier quoted context omitted.
IPv6 is seen and used directly by professionals, not the general public. Overbuilding it in the sense being mocked made sense.
Which explains why professionals have so eagerly adopted it over the last two decades
Earlier quoted context omitted.
IP addresses (especially IPv4) are not even supposed to be globally unique. How many 192.168.1.1 devices are out there? How many different distinct physical boxes respond to traffic going to 1.1.1.1?
there are a handful of ranges in IPv4 that are NOT globally unique. You're describing a much smaller set of IP ranges that are designed to be used+reused but not routable. if you take someone elses public IPv4 address and they're using it, neither one of you will be functional, and they will come knocking on your door.
Sure, but if I have the IP address 1.2.3.4 I can have lots of unique physical things have that publicly routable IP address and have them all work if I do it right.
Clearly the successor solution is to use eight groups of four hexadecimal digits each, separated by colons. Then each individual seat and peanut could be addressed to it's final destination. More seriously the solution suggested of giving the 3 companies other unused prefixes like D* U* and A* to use with their codeshares and non rev flights to start seems the easiest.