Could this be an issue with the duplex. Maybe different speeds on the lan the wan and switches?????
I see the wan is on 1G connections. Is it the same on the wan. See if you can checkout an earlier version I was on 0.88 and 0.89.2 today with no troubles but I was only working on 100mb switches all the same with vlans > -----Original Message----- > From: Peter Zaitsev [mailto:[EMAIL PROTECTED] > Sent: 24 October 2005 23:45 > To: [email protected] > Subject: [pfSense Support] bridging troubleshooting (i guess 0.89.2 is > broken ?) > > Hi, > > Might be this one would point out why it works for everyone but not for > me. > > As I mentioned firewall rules fail to load in such configuration, which > is obviously the problem but it looks like it is not the only one. > > I've replaced real IP prefix with 111.111.111. in this example > > > # ifconfig > em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > options=b<RXCSUM,TXCSUM,VLAN_MTU> > inet 111.111.111.154 netmask 0xfffffff8 broadcast > 111.111.111.159 > inet6 fe80::214:22ff:fe0a:644c%em0 prefixlen 64 scopeid 0x1 > ether 00:14:22:0a:64:4c > media: Ethernet autoselect (1000baseTX <full-duplex>) > status: active > em1: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > options=b<RXCSUM,TXCSUM,VLAN_MTU> > ether 00:14:22:0a:64:4d > media: Ethernet autoselect > status: no carrier > pfsync0: flags=41<UP,RUNNING> mtu 2020 > pfsync: syncdev: lo0 maxupd: 128 > pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33208 > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 > bridge0: flags=8041<UP,RUNNING,MULTICAST> mtu 1500 > ether ac:de:48:f6:b9:13 > priority 32768 hellotime 2 fwddelay 15 maxage 20 > member: em0 flags=7<LEARNING,DISCOVER,STP> > port 1 priority 128 path cost 55 forwarding > member: em1 flags=7<LEARNING,DISCOVER,STP> > port 2 priority 128 path cost 55 forwarding > > > As you can see "em1" for some reason has "no carrier" status. The > funny thing is the cable is there and It worked great before bridging > configuration. > > > Now If I do "ifconfig em1 up" the bridge starts to function. > > So it looks like we have 2 problems in 0.89.2 in bridge configuration: > > 1) The rules are built wrong in case there is no IP on the LAN > 2) The LAN interface is not brought up in bridging configuration. > > > Please let me know if more details are needed to troubleshoot these. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
