David McCullough
2007-Apr-18 17:22 UTC
[Bridge] [uClinux-dev] Is bridgeing possible with kernel 2.6.10
Jivin Juergen Pfeiffer lays it down ...> Hi > > I didn't get bridgeing to work with Linux kernel 2.6.10 (coldfire 5485) > yet. When i try to configure bridgeing > with "brctl", everything seems to be ok, but i if i try to ping through > my bridge, i see ARP-Request arriving on the other side, but the > ARP-Responses do not go back through the bridge. > Now i could read in > "http://www.tldp.org/HOWTO/Ethernet-Bridge-netfilter-HOWTO-2.html#ss2.1" > that "Use of kernel 2.6 is not yet a good idea". > So do i have a change to get it working?One of the guys here has been testing bridging with 2.6.17 from the uClinux-dist and it is working fine. Probably can't offer you much more than that though, Cheers, Davidm -- David McCullough, david_mccullough@securecomputing.com, Ph:+61 734352815 Secure Computing - SnapGear http://www.uCdot.org http://www.cyberguard.com
Hi I didn't get bridgeing to work with Linux kernel 2.6.10 (coldfire 5485) yet. When i try to configure bridgeing with "brctl", everything seems to be ok, but i if i try to ping through my bridge, i see ARP-Request arriving on the other side, but the ARP-Responses do not go back through the bridge. Now i could read in "http://www.tldp.org/HOWTO/Ethernet-Bridge-netfilter-HOWTO-2.html#ss2.1" that "Use of kernel 2.6 is not yet a good idea". So do i have a change to get it working? Thank You -- ------------------------------------------------------------------------ J?rgen Pfeiffer * _mailto:j.pfeiffer@seskion.de_ SesKion Softwareentwicklung und System Konzeption GmbH ( : +49-711-9905814 Karlsruher Str. 11/1 Fax: +49-711-9905827 D-70771 Leinfelden-Echterdingen 1 _http://www.seskion.de_ ------------------------------------------------------------------------
Juergen Pfeiffer schrieb:> Hi > > I didn't get bridgeing to work with Linux kernel 2.6.10 (coldfire 5485) > yet. When i try to configure bridgeing > with "brctl", everything seems to be ok, but i if i try to ping through > my bridge, i see ARP-Request arriving on the other side, but the > ARP-Responses do not go back through the bridge. >Now i found the error in the coldfire specific ethernet driver: "drivers/net/fec/fec.c" The driver did not set Promiscuouse Mode correct in Hardware Registers: function fec_set_multicast_list() with error: *void fec_set_multicast_list(struct net_device *dev) { // Pointer to the address list struct dev_mc_list *dmi; unsigned int crc, data; int i, j, k; // Receive the base address unsigned long base_addr =3D (unsigned long) dev->base_addr; if (dev->flags & IFF_PROMISC || dev->flags & IFF_ALLMULTI) { // Allow all incoming frames FEC_GALR(base_addr) =3D 0xFFFFFFFF; FEC_GAUR(base_addr) =3D 0xFFFFFFFF; return; } ... * function fec_set_multicast_list() correct: *void fec_set_multicast_list(struct net_device *dev) { // Pointer to the address list struct dev_mc_list *dmi; unsigned int crc, data; int i, j, k; // Receive the base address unsigned long base_addr =3D (unsigned long) dev->base_addr; if (dev->flags & IFF_PROMISC) { // Allow all incoming frames if ((FEC_RCR(base_addr) & FEC_RCR_PROM)=3D=3D0) { FEC_ECR(base_addr) &=3D ~FEC_ECR_ETHEREN; FEC_RCR(base_addr) |=3D FEC_RCR_PROM; FEC_ECR(base_addr) |=3D FEC_ECR_ETHEREN; } return; } if ((FEC_RCR(base_addr) & FEC_RCR_PROM)!=3D0) { FEC_ECR(base_addr) &=3D ~FEC_ECR_ETHEREN; FEC_RCR(base_addr) &=3D ~FEC_RCR_PROM; FEC_ECR(base_addr) |=3D FEC_ECR_ETHEREN; } if (dev->flags & IFF_ALLMULTI) { // Allow all incoming frames FEC_GALR(base_addr) =3D 0xFFFFFFFF; FEC_GAUR(base_addr) =3D 0xFFFFFFFF; return; } ... * after this the bridge worked fine! -- ------------------------------------------------------------------------ J=FCrgen Pfeiffer * _mailto:j.pfeiffer@seskion.de_ SesKion Softwareentwicklung und System Konzeption GmbH ( : +49-711-9905814 Karlsruher Str. 11/1 Fax: +49-711-9905827 D-70771 Leinfelden-Echterdingen 1 _http://www.seskion.de_ ------------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/bridge/attachments/20060814/048fffd5/attachment-0002.htm
On Wed, 26 Jul 2006 16:44:34 +0200 Juergen Pfeiffer <j.pfeiffer@seskion.de> wrote:> Hi > > I didn't get bridgeing to work with Linux kernel 2.6.10 (coldfire 5485) > yet. When i try to configure bridgeing > with "brctl", everything seems to be ok, but i if i try to ping through > my bridge, i see ARP-Request arriving on the other side, but the > ARP-Responses do not go back through the bridge.Did the bridge get set up right? Did the interfaces come up (look at 'brctl showstp br0') The bridge is sensitive to the network devices reporting carrier properly, so a bad network driver or card will make it not work.> Now i could read in > "http://www.tldp.org/HOWTO/Ethernet-Bridge-netfilter-HOWTO-2.html#ss2.1" > that "Use of kernel 2.6 is not yet a good idea".That's crap. 2.6 works great. 2.4 is now in frozen hibernation mode, there are bugs in there that are not going to ever be fixed.> So do i have a change to get it working? >
Danny Stemmet schrieb:> Good day Jürgen, > > We're doing work for a client and need bridging of the 2 FEC on > Coldfire 5474. It uses the same driver as the one you mentioned in > your mail to the list. > > I've applied the code changes as you mentioned, but get an error > saying FEC_RCR_PROM is undefined.. > > Is there more I would need to add to the code to get it to work? > > Using LTIB to build the bridge-utils package. >Hi Danny FEC_RCR_PROM is defined in "fec.h". It's quite some time ago, and i also repaired a second problem. In promiscuous mode (allways with bridging), the packet that was sent, was also received by the own receiver. This received own packet made a wrong entry in the bridging tabel. So my second change was to disable receiving while transmitting. Because i do not remember the exact location of my changes, i append a file "fec.tar", including fec.c and fec.h. greetings -- ------------------------------------------------------------------------ Jürgen Pfeiffer * _mailto:j.pfeiffer@seskion.de_ SesKion Softwareentwicklung und System Konzeption GmbH ( : +49-711-9905814 Karlsruher Str. 11/1 Fax: +49-711-9905827 D-70771 Leinfelden-Echterdingen 1 _http://www.seskion.de_ ------------------------------------------------------------------------ -------------- next part -------------- A non-text attachment was scrubbed... Name: fec.tar Type: application/x-tar Size: 51200 bytes Desc: not available Url : http://lists.linux-foundation.org/pipermail/bridge/attachments/20061228/5cdf496c/fec-0002.tar