Project

General

Profile

Actions

Regression #13666

closed

Assigned bridge interfaces are not configured at boot

Added by Steve Wheeler 3 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Category:
Interfaces
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.01
Release Notes:
Default
Affected Version:
Affected Architecture:
All

Description

Under some circumstances a bridge interface assigned as LAN is not configured correctly at boot. It comes up without an IPv4 address, subnet or description:

[23.01-DEVELOPMENT][admin@6100.stevew.lan]/root: ifconfig bridge0
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 58:9c:fc:10:5e:39
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: igc3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 4 priority 128 path cost 2000000
    member: igc2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 3 priority 128 path cost 2000000
    groups: bridge
    nd6 options=1<PERFORMNUD>

Resaving the interface after boot applies the expected config:

[23.01-DEVELOPMENT][admin@6100.stevew.lan]/root: ifconfig bridge0
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    description: LAN
    ether 58:9c:fc:10:5e:39
    inet 192.168.241.1 netmask 0xffffff00 broadcast 192.168.241.255
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: igc3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 4 priority 128 path cost 2000000
    member: igc2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 3 priority 128 path cost 2000000
    groups: bridge
    nd6 options=1<PERFORMNUD>

I can only replicate this on one test box here. That one was upgraded from 22.05.

See: https://forum.netgate.com/topic/175882/bridge0-lan-ip-not-present

Tested:

23.01-DEVELOPMENT (amd64)
built on Tue Nov 15 06:04:44 UTC 2022
FreeBSD 14.0-CURRENT

Actions #1

Updated by Reid Linnemann 3 months ago

  • Assignee set to Reid Linnemann
Actions #2

Updated by Reid Linnemann 2 months ago

The resolution to #13225 appears to have caused this. The rebuilding of the bridge interfaces after logical ovpn interfaces are created does not reconfigure the bridges. I'm working on a solution.

Actions #3

Updated by Reid Linnemann 2 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Alhusein Zawi about 2 months ago

  • Status changed from Feedback to Resolved

fixed

after reboot :

[23.01-DEVELOPMENT][]/root: ifconfig bridge0
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: test13666
ether 58:9c:fc:10:c3:76
inet 172.17.99.1 netmask 0xffffff00 broadcast 172.17.99.255

23.01-DEVELOPMENT (amd64)
built on Fri Dec 02 06:04:48 UTC 2022

Actions

Also available in: Atom PDF