Bug #1227
closedUnifying multiple interfaces into bridge breaks connectivity
0%
Description
I have following machine:
Dual-core Atom CPU @ 1.8 GHz
1 x 1GB RAM
2 GB Flash storage
1000/100/10 Ethernet adapter built into motherboard (re0)
Expansion card with 4 physical 100/10 interfaces (rl0-3)
I had following network configuration:
re0 worked as WAN, PPPoE
all 4 100/10 interfaces were bridged together into 1 subnetwork (192.168.1.1/24) with single DHCP server
Pfsense 2.0 2GB embedded nightly snapshots worked perfectly until my attempt (on 23rd jan) to upgrade snapshot to the most recent one (i believe my previous upgrade was approximately 14-16tth jan) which resulted into failed attempts to access any external resource as well as access to web configurator and ssh.
Today i decided to look into issue, downloaded pfSense-2.0-BETA5-2g-i386-20110124-0831-nanobsd.img.gz and deployed it to the flash storage, pfsense worked perfectly right until the moment i unified couple of interfaces into bridge.
See attachments, separate.xml and bridge.xml.
separate.xml has 3 local interfaces configured to have static ips:
LAN: 192.168.0.1/24 + DHCP server
OPT1: 192.168.1.1/24 + DHCP server
OPT2: 192.168.2.1/24 + DHCP server
When i plug my laptop into any of these interfaces, i can access both WAN and configurator without any issues.
bridge.xml:
LAN: static 192.168.0.1/24 + DHCP server
OPT1: belongs to BRIDGE interface
OPT2: belongs to BRIDGE interface
BRIDGE: 192.168.10.1 + DHCP server
When i start router, plug my laptop into LAN (1) - it works perfectly again. Problems arise when i try to plug it into any of the OPT interfaces (2): no access to WAN, no access to configurator, even pings do not reach router. When i switch latop back to LAN interface (3), it fails to access WAN and configurator too until i reboot router.
I tried to check what happens using arp command. For step (1) output appears immediately:
Address HWtype HWaddress Flags Mask Iface gate.local ether 00:06:4f:66:ff:1d C eth0
For step 2 and 3 it appears with delay of 5-10 seconds, but macs seem to be correct:
Address HWtype HWaddress Flags Mask Iface 192.168.10.1 ether 6e:8a:b4:7a:39:49 C eth0
Address HWtype HWaddress Flags Mask Iface 192.168.0.1 ether 00:06:4f:66:ff:1d C eth0
I have noticed that despite i'm connected to the same LAN interface in step 1 and 3 arp detects address differently (gate.local in 1 and 192.168.0.1 in 3).
I don't have any ideas what could cause this (not very experienced with networks), but will try to provide any info you will request.
Files
Updated by Chris Buechler almost 15 years ago
- Status changed from New to Closed
there was some breakage in bridging the past few days, fixed today. If you still have issues with a new snapshot please post to the forum, and if a specific problem is found a bug report can be opened.