Bridge interface broken with upgrade
-
QOTOM Q355G4
4 x Intel I211-AT 10/100/1000 GbE Controller
Intel Core i5-5200U ProcessorWAN (wan) -> igb0 -> v4: 24.89.64.78/24
LAN (lan) -> bridge0 -> v4: 192.168.177.1/24
P4 (opt1) -> igb2 ->
P3 (opt2) -> igb3 ->
P2 (opt3) -> igb1 ->
WLAN (opt4) -> ath0_wlan0 ->Had been functioning as expected prior to upgrade to currrent snapshot from FreeBSD 12.3-STABLE snapshot. (all CE 2.7.0).
There is no ip connectivity on the lan interfaces and no associated evidence of dhcp. Wan works as expected so not likely a driver issue.
Possible bug or regression?
Help appreciated.
Ted Quade
-
Run
ifconfigat the command line and check the bridge is being created correctly.Steve
-
@stephenw10 Following is the ifconfig output (this has been transcribed and carefully confirmed).
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: LAN
ether 02:97:3e:2e:3c:00
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: igb1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 2 priority 128 path cost 55
member: igb3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 4 priority 128 path cost 2000000
member: igb2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 3 priority 128 path cost 55
groups: bridge
nd6 options=1<PERFORMNUD>What is missing is the line as follows (taken from a functioning installation):
inet 192.168.177.1 netmask 0xffffff00 broadcast 192.168.177.255
Ted Quade
-
@stephenw10 I tried to set the lan / bridge0 ip address via the console option 2) and the following error was thrown (again transcribed):
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /etc/rc.initial.setlanip:75
Stack trace:
#0 /etc/rc.initial.setlanip(364): Console_get_interface_from_ppp('bridge0')
#1 /etc/rc.initial.setlanip(375): Console_configure_ip_address(4)
#2 (main)
thrown in /etc/rc.initial.setlanip on line 75
PHP ERROR: Type: 1, File: /etc/rc.initial.setlanip, Line: 75, Message: Uncaught TypeError: Cannot access offset of type string on string in /etc/rc.initial.setlanip:75
Stack trace:
#0 /etc/rc.initial.setlanip(364): Console_get_interface_from_ppp('bridge0')
#1 /etc/rc.initial.setlanip(375): Console_configure_ip_address(4)
#2 (main)
thrownpfsense - Netgate Device ID: (obfuscated by me)Ted Quade
-
@tedquade said in Bridge interface broken with upgrade:
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /etc/rc.initial.setlanip:75
Stack trace:
#0 /etc/rc.initial.setlanip(364): Console_get_interface_from_ppp('bridge0')
#1 /etc/rc.initial.setlanip(375): Console_configure_ip_address(4)
#2 (main)
thrown in /etc/rc.initial.setlanip on line 75Ah, nice catch!
You didn't see any similar php errors generated trying to set it via the GUI?
-
What snapshot are you running exactly? I'm failing to replicate that in the current snap.
Edit: Rather I can replicate the console menu bug but not the main issue. Assigning it in the gui comes up as expected.
-
@stephenw10 I have no lan access so no gui (see my original post).
Ted Quade
-
Hmm, the bridge comes up with an ip address at boot for me. As I expect it to.
I assume you have rebooted since the upgrade and it's still failing?
Any errors shown in the boot log when it tries to bring up LAN?
Steve
-
@stephenw10 Has been rebooted and no errors during boot that I can catch. I only have the vga console access to the appliance. I have no lan access which makes for more difficult troubleshooting.
I have since trashed the installation and will take another run at it next week (it's Canadian Thanksgiving this weekend).
Ted Quade
