Le jeudi 07 février 2013 22:37:36, Hauke Mehrtens a écrit : > On 02/07/2013 06:50 PM, Rafał Miłecki wrote: > > 2013/2/7 Rafał Miłecki <[email protected]>: > >> The problem is that in failsafe my ethernet driver works fine (I can > >> ping router and the other way), but in normal mode (with virtual > >> interfaces) it stops working. My intention is to create all virtual > >> interfaces manually, to see where exactly my eth driver fails. > > > > OK, I've discovered something weird. First of all: > >> # brctl show > >> bridge name bridge id STP enabled interfaces > >> br-lan 8000.c83a3540c1a8 no eth0.0 > > > > It seems there is something wrong with eth0.0. When I switch br-lan to > > > > eth0 (from eth0.0) using: > >> # brctl delif br-lan eth0.0 > >> # brctl addif br-lan eth0 > > > > Ethernet starts working! > > > > Please see attached file for log with "ifconfig -a" calls. > > > > Does anyone have any idea what may be wrong with that eth0.0 > > interface? Why using it for br-lan fails? Why swtiching br-lan to eth0 > > succeeds? I expected eth0.0 to work the same way as eth0. > > > > > > There is one more tricky part. You may wonder what happens if I switch > > br-lan back to eth0.0 (from eth0). Well pinging works again, but only > > for a limited amount of time. Sometimes I can't see even one > > "ping-pong" and sometimes it keeps working even for 20 seconds. > > > > Anyway, after a moment it stops again. Repeating the whole scenario: > >> brctl delif br-lan eth0.0 > >> brctl addif br-lan eth0 > >> brctl delif br-lan eth0 > >> brctl addif br-lan eth0.0 > > > > Makes pinging work again for few seconds. > > I assume the switch driver you are using is broken. I do not get some of > my devices to work with the bgmac driver + BCM53125 at all. After some > modifications to the switch driver I was able to transmit some packages > but did not receive anything. I do not want to invest many efforts in > the old switch driver that's the reason I want to get a separate phy > driver and use the b53 switch driver any try this out or fix it if > necessary. I assume your problem is also related to the switch.
Another thing you might want to check, is to ensure that your driver accepts and correctly processes ethernet frames with a vlan tag (especially enough room was made for the incoming skb etc ...) in both TX and RX paths. > > Did you apply the patches I added to OpenWrt [0] and send for linux > mainline kernel inclusion? They are needed to make bridge the switch > interface, otherwise you get the problems described in this ticket [1]. > > Hauke -- Florian _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
