Re: local network

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

 



On 6/16/25 2:38 PM, Patrick Dupre via users wrote:

On 6/16/25 2:11 PM, Patrick Dupre via users wrote:
OK,

Now it is working with
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 enp0s20f0u11
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 bridge0
10.40.0.0       0.0.0.0         255.255.255.0   U         0 0          0 bridge0
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 enp0s20f0u11
192.168.1.1     0.0.0.0         255.255.255.255 UH        0 0          0 bridge0
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 virbr0

Question
I have enp1s0 ipv4 manually set as
10.40.1.0/24   without GW, neither DNS
enp2s0 ivpv4 also manually set as
10.40.2.0/24    without GW, neither DNS

These should both be unconfigured.  They are part of the bridge.
And I'm still concerned that 192.168.1.1 is on the bridge.

It is configured in automatic DHCP
enp0s20f0u11: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.1.166  netmask 255.255.255.0  broadcast 192.168.1.255
         inet6 fe80::a594:2280:6476:1293  prefixlen 64  scopeid 0x20<link>
         ether 96:bd:e2:d4:3e:52  txqueuelen 1000  (Ethernet)


Should it be set manually?

That is the USB port.  It should not be part of the bridge.


and
enp1s0 port 1 and enp2s0 port 2 set automatic DHCP
Should I keep it like that?
Will be the IP addresses always conserved?

I don't know what you mean by this.  I would recommend that PC B and C
have static addresses.  I don't think the DHCP reservations are preserved.
They are static
The only static ones are bridge0 port1 and port2
and
USB Ethernet (enp0s20f0u11)

I don't understand what you mean about the ports. Whatever those are, they shouldn't be configured.

--
_______________________________________________
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