Not a scientist. I have a litany of complex topics that I just can’t really talk to anyone about. I’m a big computer networking nerd, and once upon a time, when I didn’t know what I didn’t know, I was curious what computer networking really entailed… It seemed dead simple, you connect things to a switch, connect that switch to the internet router, not much more.
Then I learned about VLANs, which are cool but it seemed like unnecessary complexity. Then I learned about Routing and L3 switching, and routing protocols and… Holy shit, how deep is this?
Now-a-days, I want to have conversations about the merits of one routing protocol over another in various contexts, and see/build a spine and leaf network infrastructure that’s nearly infinitely scalable.
I want to explore the nuance of IP unnumbered routing. I can’t find anyone who will chat about it on a level that’s close to my understanding, either someone knows way more than I do, or they know way less.
IP unnumbered routing is a way of connecting devices without setting an IP on the interface that is being routed to/from. The other end uses the routing protocol on top of layer 2, and while the two might have a router ID, often in the form of an IP address, the interface that is connecting the two has no IP. It’s basically advanced point to point protocol (PPP) that breaks away from traditional TCP/IP routing in ways that people who have never used anything besides TCP/IP can’t really comprehend. The two “IP addresses” (actually router IDs) in play can have nothing in common. Traditional TCP/IP requires that two IPs share a subnet. In routing, this is typically a /30 for IPv4, and the two IPs are adjacent to eachother, eg, 10.254.123.1 and 10.254.123.2
IP unnumbered can have 10.254.123.2 talking directly with 172.30.88.207, with no layer 3 interfaces in-between.
It’s really fascinating and interesting and I’ve been trying to find a good model or guide to help me learn this better, but I keep ending up at dead ends, and I have nobody to talk to about it.
Now-a-days, I want to have conversations about the merits of one routing protocol over another in various contexts, and see/build a spine and leaf network infrastructure that’s nearly infinitely scalable.
bro i just want screensharing that isn’t using the hell that is webrtc.
How hard is it to send video packets over IP, it can’t be that difficult. Half the job is already done, and i can’t imagine building a reliable networking protocol, even if you had to do it from scratch would be particularly hard.
See, I only recently came into awareness that web RTC was a thing. I have a lot of learning to do on how it even works as a protocol.
I’m sure it runs on top of IP, so I think web RTC meets your curriculum here. Regardless of that, I think I know what you mean, and if I knew enough about the protocol, I might even agree.
I need to brush up on the new protocols that are getting to be very common. I’m almost entirely up to date on the 802.11 specs, but there’s so much to keep track of… Yikes.
Did my fair share of networking back in the day, but never heard of IP unnumbered. I was curious about the same idea back in the day and it is possible, but I haven’t much seen anyone doing it for realsies. If you have any good longreads/vids on the topic, it’d be much appreciated.
I’ll look at my resources and see what I can dig up. No promises, but the concepts are simple as long as you can separate yourself from the TCP/IP restrictions on two things needing to be in a subnet, and the idea that NAT is something that needs to happen.
Honestly, I’ve seen so many people get hung up on the fact that NAT isn’t universal, or necessary.
Bringing a website online sounds a lot more like development stuff.
Networking is all about how to get data from one place to another that is reasonable, manageable and scalable. Knowing what devices are increasing latency and when you should adjust the settings to route around a high latency (and/or high loss) link to enhance performance and reliability. Visibility into network flows in real time and monitoring for every link and port that’s connected to a device, switch, router, or computer.
Web hosting is system admin and development.
What networking concerns do you have with this website?
Not a scientist. I have a litany of complex topics that I just can’t really talk to anyone about. I’m a big computer networking nerd, and once upon a time, when I didn’t know what I didn’t know, I was curious what computer networking really entailed… It seemed dead simple, you connect things to a switch, connect that switch to the internet router, not much more.
Then I learned about VLANs, which are cool but it seemed like unnecessary complexity. Then I learned about Routing and L3 switching, and routing protocols and… Holy shit, how deep is this?
Now-a-days, I want to have conversations about the merits of one routing protocol over another in various contexts, and see/build a spine and leaf network infrastructure that’s nearly infinitely scalable.
I want to explore the nuance of IP unnumbered routing. I can’t find anyone who will chat about it on a level that’s close to my understanding, either someone knows way more than I do, or they know way less.
IP unnumbered routing is a way of connecting devices without setting an IP on the interface that is being routed to/from. The other end uses the routing protocol on top of layer 2, and while the two might have a router ID, often in the form of an IP address, the interface that is connecting the two has no IP. It’s basically advanced point to point protocol (PPP) that breaks away from traditional TCP/IP routing in ways that people who have never used anything besides TCP/IP can’t really comprehend. The two “IP addresses” (actually router IDs) in play can have nothing in common. Traditional TCP/IP requires that two IPs share a subnet. In routing, this is typically a /30 for IPv4, and the two IPs are adjacent to eachother, eg, 10.254.123.1 and 10.254.123.2 IP unnumbered can have 10.254.123.2 talking directly with 172.30.88.207, with no layer 3 interfaces in-between.
It’s really fascinating and interesting and I’ve been trying to find a good model or guide to help me learn this better, but I keep ending up at dead ends, and I have nobody to talk to about it.
bro i just want screensharing that isn’t using the hell that is webrtc.
How hard is it to send video packets over IP, it can’t be that difficult. Half the job is already done, and i can’t imagine building a reliable networking protocol, even if you had to do it from scratch would be particularly hard.
everything is webrtc, it always has been.
See, I only recently came into awareness that web RTC was a thing. I have a lot of learning to do on how it even works as a protocol.
I’m sure it runs on top of IP, so I think web RTC meets your curriculum here. Regardless of that, I think I know what you mean, and if I knew enough about the protocol, I might even agree.
I need to brush up on the new protocols that are getting to be very common. I’m almost entirely up to date on the 802.11 specs, but there’s so much to keep track of… Yikes.
Did my fair share of networking back in the day, but never heard of IP unnumbered. I was curious about the same idea back in the day and it is possible, but I haven’t much seen anyone doing it for realsies. If you have any good longreads/vids on the topic, it’d be much appreciated.
I’ll look at my resources and see what I can dig up. No promises, but the concepts are simple as long as you can separate yourself from the TCP/IP restrictions on two things needing to be in a subnet, and the idea that NAT is something that needs to happen.
Honestly, I’ve seen so many people get hung up on the fact that NAT isn’t universal, or necessary.
I need some help with networking and eventually getting an organisation website online; if you want to geek out a bit, please send me a dm. :)
Bringing a website online sounds a lot more like development stuff.
Networking is all about how to get data from one place to another that is reasonable, manageable and scalable. Knowing what devices are increasing latency and when you should adjust the settings to route around a high latency (and/or high loss) link to enhance performance and reliability. Visibility into network flows in real time and monitoring for every link and port that’s connected to a device, switch, router, or computer.
Web hosting is system admin and development.
What networking concerns do you have with this website?
yeah uh… you lost me at ‘protocols’