On Thu, Dec 26, 2019 at 11:19:28AM -0800, Gordon Messmer wrote:
> On 12/26/19 8:42 AM, Patrick Mansfield wrote:
> > I have a fixed IP address in my network script, this:
> >
> > [umbrella network-scripts]$ more ifcfg-br0
> > DEVICE=br0
> > TYPE=Bridge
> > IPADDR=192.168.1.1
> > NETMASK=255.255.255.0
>
>
> It seems odd that there's no default route in that configuration.
>
> Bring up the network in that configuration and see if you can get the output
> of "ip route show" and "ip addr show". Stop firewalld if necessary to stop
> logs broadcast to the terminal.
With my old network ifcfg-br0 and more, I see:
+ ip route show
default via 20.24.123.1 dev enp6s0 proto dhcp metric 100
10.8.0.0/24 via 10.8.0.2 dev tun0
10.8.0.2 dev tun0 proto kernel scope link src 10.8.0.1
20.24.123.0/22 dev enp6s0 proto kernel scope link src 20.24.123.88 metric 100
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.1 metric 425 linkdown
+ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp6s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:48:54:62:2f:7a brd ff:ff:ff:ff:ff:ff
inet6 fe80::248:54ff:fe62:2f7a/64 scope link
valid_lft forever preferred_lft forever
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 74:d0:2b:a2:7d:a9 brd ff:ff:ff:ff:ff:ff
4: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:d0:b7:6c:7d:0e brd ff:ff:ff:ff:ff:ff
inet 20.24.123.88/22 brd 20.24.123.255 scope global dynamic noprefixroute enp6s0
valid_lft 344747sec preferred_lft 344747sec
inet6 ....::........:....:..../64 scope link
valid_lft forever preferred_lft forever
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
link/none
inet 10.8.0.1 peer 10.8.0.2/32 scope global tun0
valid_lft forever preferred_lft forever
inet6 fe80::1a91:d2b2:5884:f50f/64 scope link stable-privacy
valid_lft forever preferred_lft forever
10: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 22:65:60:c8:61:75 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global noprefixroute br0
valid_lft forever preferred_lft forever
>
>
> > But AFAIR br0 did not get an IP address. I'm not 100% sure of the exact failure, as
> > I had difficulty using the console as it that was being spammed by a firewall
> > message output apparently because the bridge was not up, and I had to disable the
> > bridge and use one network for now so I can get normal internet access.
>
>
> That message might be relevant... You probably should include it.
I used "dmesg -n 1" to stop console output.
The bridge is supposed to bridge enp4s0 (it was being named lan1 prior to the
upgrade to F31) and enp6s1 (was lan2 prior to F31 upgrade).
The messages are for my enp4s0, but it has no IP address. This is via my
iptables setup. I assume this is happening because br0 (that I would normally
NAT for me) is not up:
Dec 26 15:35:12 umbrella kernel: Input generic reject rule IN=enp4s0 OUT= MAC=ff:ff:ff:ff:ff:ff:90:6e:bb:8d:13:d7:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=128 ID=57005 PROTO=UDP SPT=68 DPT=67 LEN=308
I found these in my log files, they look very relevant to my problem, but I
haven't figured out why they are busy:
...
Dec 26 15:38:50 umbrella systemd-udevd[767]: enp6s1: Failed to rename network interface 2 from 'enp6s1' to 'lan2': Device or resource busy
Dec 26 15:38:50 umbrella systemd-udevd[767]: enp6s1: Failed to process device, ignoring: Device or resource busy
Dec 26 15:38:50 umbrella systemd-udevd[758]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 26 15:38:50 umbrella systemd-udevd[758]: enp4s0: Failed to rename network interface 3 from 'enp4s0' to 'lan1': Device or resource busy
Dec 26 15:38:50 umbrella systemd-udevd[758]: enp4s0: Failed to process device, ignoring: Device or resource busy
...
I think something has changed with the startup or the ordering so those two
interfaces are now busy when it tries to rename them.
With fedora 29, no failures were seen, this:
...
Dec 25 11:43:09 umbrella kernel: r8169 0000:04:00.0 lan1: renamed from enp4s0
Dec 25 11:43:09 umbrella systemd-udevd[764]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 25 11:43:09 umbrella kernel: 8139too 0000:06:01.0 lan2: renamed from enp6s1
...
I have two ethernet switches, I was planning to someday segrate the traffic but
was using a bridge for now, I moved everything to cascade off one of the
switches, and have gotten rid of the bridge again to avoid this problem :-(
If I have time I'll try and get it working again. I can probably just try and
rename my currently unused enp6s1 network to start with, or just use enp6s1 and
enp4s0 for the bridge and not bother renaming them.
-- Patrick
_______________________________________________
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
