On 6/14/25 10:04 PM, Tim via users wrote: > > USB device > > 10.42.0.254 > > | <-- Top half in same IP range > > | as themselves (first three > > 10.42.0.1 quads match each other). > > PC-A > > 10.42.1.1 10.42.1.2 > > | | <-- Bottom half in their own IP range, > > | | same as themselves, different from > > 10.42.1.3 10.42.1.4 the top half (first three quads > > PC-B PC-C match each other, & don't match the > > top half).
Samuel Sieb: > You misunderstood the situation. Well, I wouldn't be surprised, but his first paragraph seems to describe what I thought it did (though I could read into it that even more PCs are connected behind PC B & C). Bearing in mind that the top of my diagram starts with a USB connection between USB device and PC-A, not ethernet. Those IPs are simply the interface IPs on those devices, whatever kind of interface it is. > There are two ethernet ports with one computer connected to each one. And that doesn't seem any different. > So the first computer that boots, regardless of which port it's > connected to, will activate the port and get the first IP range. The > second computer will get the next range on the other port. Which is the haywire bit... If the network is configured well, it's not random assignment. But checking what device is connected, whichever port it's on, and giving that device a particular IP you want it to always use. Of course it could also do what the router in my security system does, it always assigns specific IPs to specific ports. i.e. No matter what is plugged into port 1, it's 192.168.1.1. That also provides a very predictable network, and a very easy network to decide which device gets what IP (just patch it the way you want, no fiddling with any settings, at all). Of course that's a closed network, and doesn't have to accommodate anything fancy. But in his case, the assignment could be DHCP. Or, if the network is so unpredictable, then manually assign fixed IPs on each device, themselves. And considering that he says the main PC may not be on all the time, and assuming it was the one with the DHCP server that he's tried configuring, it probably is going to be the most robust solution (configure each device manually). I would do that on very small systems. Set IPs on permanent devices to have permanent IPs, in their own configuration. Set any DHCP server to accommodate that (not assign *those* IPs to anything else, and be prepared to assign those same IPs to the same PCs that I've manually configured, just in case they've reconfigured for DHCP, later). -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 (yes, this is the output from uname for this PC when I posted) Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
