Re: local network

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6/15/25 1:11 AM, Tim via users wrote:
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.

The internet is connected through the USB interface. Then there are two RJ45 ports, one for each of B and C.

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.

This is the default configuration of the "shared to other computers" option. Normally, you would only have one interface with that option and you don't care what IP addresses the attached computers get, but in this case there are two interfaces. The Gnome network configuration doesn't let you set a subnet for the interface, which is why it depends on which computer of B or C connects first. nm-connection-editor lets you set a fixed subnet.

--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux