On 12/27/19 7:15 AM, Mike Wright wrote:
On 12/26/19 5:21 PM, Gordon Messmer wrote:
> On 12/26/19 4:47 PM, Patrick Mansfield wrote:
>> 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 think you probably had configured lan1 and lan2 in a specific
> firewall "zone" but now that the interfaces aren't being renamed, they
> aren't in a zone and don't have rules. If you are going to give up on
> renaming, you'll want to put those interfaces in the appropriate
> firewall zone.
>
>
>> 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
"ip" is your friend. To rename an interface it must be down.
"ip link set enp4s0 down"
"ip link set enp4s0 name eth0"
"ip link set eth0 up"
Note that when you take an interface down it disappears from the routing
tables. You'd again use "ip" to add the route. This example adds the
default route.
"ip route add default via <GATEWAY_IP> dev eth0"
Note that eth0 was used for example purposes. You'd use "lan1" or
"lan2".