11:23 p.m.
Hi All,
Help!
Fedora 37
This is getting obnoxious.
The updates I installed today getting ready for
FC38 broke my bridge, AGAIN.
I opened nm-connection-editor and deleted the bridge.
Then I followed the following directions:
The last two commands corked my recreation. Why
is "br0 is strictly unmanaged"?
What am I doing wrong, THIS TIME!
Many thanks,
-T
How to set up a bridge with nmcli:
Reference(s):
https://wiki.archlinux.org/title/network_bridge
# nmcli connection add type bridge ifname br0 stp no
Connection 'bridge-br0' (a7722855-1aa1-4da8-8251-40f145f23681)
successfully added.
# nmcli connection add type bridge-slave ifname eno1 master br0
Connection 'bridge-slave-eno1' (52d4e5fa-20c5-4ccf-84fb-8f4b53b17a7a)
successfully added.
# nmcli connection show --active
NAME UUID TYPE DEVICE
Wired connection 2 3d30b55f-3675-3e71-88fd-a9796720a9f3 ethe
rnet eno2
# nmcli connection down eno2
# nmcli connection up bridge-br0
# nmcli connection up bridge-br0
Error: Connection activation failed: Connection 'bridge-br0' is not
available on device br0 because device is strictly unmanaged
# nmcli connection up bridge-br0
Error: Connection activation failed: Connection 'bridge-br0' is not
available on device br0 because device is strictly unmanaged
12:04 a.m.
On 4/30/23 21:23, ToddAndMargo via users wrote:
I opened nm-connection-editor and deleted the bridge.
Why did you delete it instead of fixing it and why didn't you add it
again using the helpful tool instead of trying to do it the hard way?
How to set up a bridge with nmcli:
Reference(s):
https://wiki.archlinux.org/title/network_bridge
# nmcli connection add type bridge ifname br0 stp no
Connection 'bridge-br0' (a7722855-1aa1-4da8-8251-40f145f23681)
successfully added.
# nmcli connection add type bridge-slave ifname eno1 master br0
Connection 'bridge-slave-eno1' (52d4e5fa-20c5-4ccf-84fb-8f4b53b17a7a)
successfully added.
I copied those lines, only substituting my ethernet device and it didn't
have any trouble.
Have you modified any of the NetworkManager config files or added any?
12:51 a.m.
On 4/30/23 22:04, Samuel Sieb wrote:
On 4/30/23 21:23, ToddAndMargo via users wrote:
> I opened nm-connection-editor and deleted the bridge.
Why did you delete it instead of fixing it and why didn't you add it
again using the helpful tool instead of trying to do it the hard way?
I did try to fix it, but could not figureit out. So I decided to start
over.
I also checked agaist backup and ther was no change in all
four of my /etc/NetworkManager/system-connections files
I did find that systemd-networkd.service had been disabled.
I re-enables and start it. Did not help.
> How to set up a bridge with nmcli:
>
> Reference(s):
> https://wiki.archlinux.org/title/network_bridge
>
>
> # nmcli connection add type bridge ifname br0 stp no
> Connection 'bridge-br0' (a7722855-1aa1-4da8-8251-40f145f23681)
> successfully added.
>
>
> # nmcli connection add type bridge-slave ifname eno1 master br0
> Connection 'bridge-slave-eno1' (52d4e5fa-20c5-4ccf-84fb-8f4b53b17a7a)
> successfully added.
I copied those lines, only substituting my ethernet device and it didn't
have any trouble.
Have you modified any of the NetworkManager config files or added any?
I did try starting over, did not work.
This command stopped me cold. Do you know what it means?
# nmcli connection up bridge-br0
Error: Connection activation failed: Connection 'bridge-br0' is not
available on device br0 because device is strictly unmanaged
1:14 a.m.
On 4/30/23 22:51, ToddAndMargo via users wrote:
I also checked agaist backup and ther was no change in all
four of my /etc/NetworkManager/system-connections files
I did find that systemd-networkd.service had been disabled.
I re-enables and start it. Did not help.
You definitely don't want that. It will be competing with NetworkManager.
1:14 a.m.
On 4/30/23 23:03, ToddAndMargo via users wrote:
On 4/30/23 22:04, Samuel Sieb wrote:
> I copied those lines, only substituting my ethernet device and it
> didn't have any trouble.
Does your
# nmcli device
show br0 as unmanaged?
No, it's trying to get an IP address.
Do you have anything in /etc/NetworkManager/conf.d?
Do you have any uncommented lines in
/etc/NetworkManager/NetworkManager.conf that aren't section headers?
Try running "nmcli d set br0 managed yes".
1:24 a.m.
On 4/30/23 23:14, Samuel Sieb wrote:
On 4/30/23 23:03, ToddAndMargo via users wrote:
> On 4/30/23 22:04, Samuel Sieb wrote:
>
>> I copied those lines, only substituting my ethernet device and it
>> didn't have any trouble.
>
> Does your
>
> # nmcli device
>
> show br0 as unmanaged?
No, it's trying to get an IP address.
Do you have anything in /etc/NetworkManager/conf.d?
Do you have any uncommented lines in
/etc/NetworkManager/NetworkManager.conf that aren't section headers?
Everything is commented out
Try running "nmcli d set br0 managed yes".
no joy:
# nmcli d set br0 managed yes
# nmcli device
DEVICE TYPE STATE CONNECTION
eno2 ethernet connected Wired connection 2
eno1 ethernet unavailable --
br0 bridge unmanaged --
lo loopback unmanaged --
# systemctl restart NetworkManager
# nmcli device
DEVICE TYPE STATE CONNECTION
eno2 ethernet connected Wired connection 2
eno1 ethernet unavailable --
br0 bridge unmanaged --
lo loopback unmanaged --
1:32 a.m.
On 4/30/23 23:24, ToddAndMargo via users wrote:
# nmcli device
DEVICE TYPE STATE CONNECTION
eno2 ethernet connected Wired connection 2
eno1 ethernet unavailable --
br0 bridge unmanaged --
lo loopback unmanaged --
Notice that br0 isn't associated with a connection. What does "nmcli c"
show?
Try removing the bridge pieces again and make sure they're actually
gone. Then do the first command and make sure that br0 is properly
associated.
Doing updates should not have changed anything. It's like you have some
weird network config hiding somewhere. Do you still have
systemd-networkd running?
1:47 a.m.
On 4/30/23 23:32, Samuel Sieb wrote:
On 4/30/23 23:24, ToddAndMargo via users wrote:
> # nmcli device
> DEVICE TYPE STATE CONNECTION
> eno2 ethernet connected Wired connection 2
> eno1 ethernet unavailable --
> br0 bridge unmanaged --
> lo loopback unmanaged --
Notice that br0 isn't associated with a connection. What does "nmcli c"
show?
Try removing the bridge pieces again and make sure they're actually
gone. Then do the first command and make sure that br0 is properly
associated.
Doing updates should not have changed anything. It's like you have some
weird network config hiding somewhere. Do you still have
systemd-networkd running?
# vi /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown
[ifupdown]
managed=false
fixed it.
Now to fix my firewall.
Thakn yo for the help!
2:22 a.m.
On 4/30/23 23:47, ToddAndMargo via users wrote:
On 4/30/23 23:32, Samuel Sieb wrote:
> On 4/30/23 23:24, ToddAndMargo via users wrote:
>> # nmcli device
>> DEVICE TYPE STATE CONNECTION
>> eno2 ethernet connected Wired connection 2
>> eno1 ethernet unavailable --
>> br0 bridge unmanaged --
>> lo loopback unmanaged --
>
> Notice that br0 isn't associated with a connection. What does "nmcli
> c" show?
> Try removing the bridge pieces again and make sure they're actually
> gone. Then do the first command and make sure that br0 is properly
> associated.
>
> Doing updates should not have changed anything. It's like you have
> some weird network config hiding somewhere. Do you still have
> systemd-networkd running?
# vi /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown
[ifupdown]
managed=false
fixed it.
Now to fix my firewall.
Thakn yo for the help!
Big thing on the firewall was trying to figure out how
to do a grep with brackets in it. But I figured it out.
nmcli device show br0 > /dev/nul
if [ $? = 0 ]; then
InternalNic=br0
else
InternalNic=eno1
fi
internal_addr=$(nmcli device show $InternalNic | grep -i
'IP4.ADDRESS\[1\]' | grep 1 | awk '{print $2}' | sed -e
's/\/.*//')
3:43 a.m.
Hi.
On Mon, 01 May 2023 00:22:38 -0700 ToddAndMargo via users wrote:
nmcli device show br0 > /dev/nul
Beware: /dev/null, not /dev/nul
if [ $? = 0 ]; then
InternalNic=br0
else
InternalNic=eno1
fi
internal_addr=$(nmcli device show $InternalNic | grep -i
'IP4.ADDRESS\[1\]' | grep 1 | awk '{print $2}' | sed -e
's/\/.*//')
That could be simplified as follows:
(not using $?, using awk instead of grep & sed)
if nmcli device show br0 > /dev/null; then
InternalNic=br0
else
InternalNic=eno1
fi
internal_addr=$(
nmcli device show $InternalNic \
| awk -F'[ /]+' '$1 == "IP4.ADDRESS[1]:" { print $2 }'
)
or even simpler by using nmcli --get-values and assuming you have only
one IP address on this interface:
internal_addr=$(nmcli --get-values IP4.ADDRESS device show $InternalNic)
internal_addr=${internal_addr%/*}
--
francis
3:49 a.m.
On 5/1/23 01:43, Francis.Montagnac(a)inria.fr wrote:
Hi.
On Mon, 01 May 2023 00:22:38 -0700 ToddAndMargo via users wrote:
> nmcli device show br0 > /dev/nul
Beware: /dev/null, not /dev/nul
Opps Thank yo . vi to the rescue!
> if [ $? = 0 ]; then
> InternalNic=br0
> else
> InternalNic=eno1
> fi
> internal_addr=$(nmcli device show $InternalNic | grep -i
> 'IP4.ADDRESS\[1\]' | grep 1 | awk '{print $2}' | sed -e
's/\/.*//')
That could be simplified as follows:
(not using $?, using awk instead of grep & sed)
if nmcli device show br0 > /dev/null; then
InternalNic=br0
else
InternalNic=eno1
fi
internal_addr=$(
nmcli device show $InternalNic \
| awk -F'[ /]+' '$1 == "IP4.ADDRESS[1]:" { print $2
}'
)
or even simpler by using nmcli --get-values and assuming you have only
one IP address on this interface:
internal_addr=$(nmcli --get-values IP4.ADDRESS device show $InternalNic)
internal_addr=${internal_addr%/*}
Thank you!
396
days inactive
396
days old
12 comments
3 participants
participants (3)
-
Francis.Montagnac＠inria.fr -
Samuel Sieb -
ToddAndMargo