I know this is off topic but...
check out the Jouni Malinen's HostAP driver homepage at:
http://hostap.epitest.fi
It enables the special "HostAP" functionality of the Harris/Intersil
Prism
2/2.5/3 chipset which allows your card to act as a full AP (and also do
wireless -> ethernet bridging.)
Some Atmels work with this driver, YMMV...
-Chris
----- Original Message -----
From: "Christoph Kaminski" <mangel@gmx.de>
To: <bridge@lists.osdl.org>
Sent: Wednesday, March 17, 2004 9:13 AM
Subject: [Bridge] bridge wlan-eth
> Hi!
>
> I have some problems with an bridge between wlan0 and eth0 device...
>
> It works and I can from both sides ping the router with the bridge device
but> I cant ping the devices from other net so I cant ping wlan devs from eth
net> and other way around
>
> the wlan card is an atmel usbw11 from linksys and eth is a intel e100
> 10/100mbit nic
>
> I have configured the bridge according to the how to and dont see any
errors> in kern.log or somewhere else....
>
> What is wrong?
>
> PS: sorry for my english but I hope you can understand what I mean
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> http://lists.osdl.org/mailman/listinfo/bridge
On Wed, 17 Mar 2004 18:13:58 +0100 Christoph Kaminski <mangel@gmx.de> wrote:> Hi! > > I have some problems with an bridge between wlan0 and eth0 device... > > It works and I can from both sides ping the router with the bridge device but > I cant ping the devices from other net so I cant ping wlan devs from eth net > and other way around > > the wlan card is an atmel usbw11 from linksys and eth is a intel e100 > 10/100mbit nic > > I have configured the bridge according to the how to and dont see any errors > in kern.log or somewhere else.... > > What is wrong? > > PS: sorry for my english but I hope you can understand what I mean > _______________________________________________ > Bridge mailing list > Bridge@lists.osdl.org > http://lists.osdl.org/mailman/listinfo/bridgeMore info in bridge FAQ http://bridge.sourceforge.net/faq.html It doesn't work with my Wireless card! This is a known problem, and it is not caused by the bridge code. Many wireless cards don't allow spoofing of the source address. It is a firmware restriction with some chipsets. You might find some information in the bridge mailing list archives to help. -- Stephen Hemminger mailto:shemminger@osdl.org Open Source Development Lab http://developer.osdl.org/shemminger
The answer to this is in the bridge FAQ at: http://bridge.sourceforge.net/faq.html Have Fun! -M On Wed, 17 Mar 2004, Christoph Kaminski wrote:> Hi! > > I have some problems with an bridge between wlan0 and eth0 device... > > It works and I can from both sides ping the router with the bridge device but > I cant ping the devices from other net so I cant ping wlan devs from eth net > and other way around > > the wlan card is an atmel usbw11 from linksys and eth is a intel e100 > 10/100mbit nic > > I have configured the bridge according to the how to and dont see any errors > in kern.log or somewhere else.... > > What is wrong? > > PS: sorry for my english but I hope you can understand what I mean > _______________________________________________ > Bridge mailing list > Bridge@lists.osdl.org > http://lists.osdl.org/mailman/listinfo/bridge >Mark S. Mathews AbsoluteValue Systems Web: http://www.linux-wlan.com 715-D North Drive e-mail: mark@linux-wlan.com Melbourne, FL 32934 Phone: 321.259.0737 USA Fax: 321.259.0286
Hi. Christoph Kaminski wrote:> It works and I can from both sides ping the router with the bridge device but > I cant ping the devices from other net so I cant ping wlan devs from eth net > and other way around > > the wlan card is an atmel usbw11 from linksys and eth is a intel e100 > 10/100mbit nicYou'll have two problems: 1. The e100 is said to have a problem with bridging, depending on the driver you use. 2. You need to have your wlan device working in a special mode, which is not available to the atmel-chipsets afaik. This mode is known under many names, such as "Host-AP", "Master-Mode", "AP-Mode" and others. Without this mode, you won't be able to bridge between wlan and lan. The only way to work around this problem then would be to use proxy arp - afair there is a daemon available that cares about the wlan-lan situation in context to proxy arp. You should find it when searching freshmeat.net with "proxy arp" or thelike. Bye, Mike
Hi! I have some problems with an bridge between wlan0 and eth0 device... It works and I can from both sides ping the router with the bridge device but I cant ping the devices from other net so I cant ping wlan devs from eth net and other way around the wlan card is an atmel usbw11 from linksys and eth is a intel e100 10/100mbit nic I have configured the bridge according to the how to and dont see any errors in kern.log or somewhere else.... What is wrong? PS: sorry for my english but I hope you can understand what I mean
Hi list, I am not subscribed to this list, but I hope someone will know the solution to my problem ... I have checked the archives and there was a thread: <http://lists.osdl.org/pipermail/bridge/2004-March/000224.html> that did not really get resolved. I have discovered something about this situation that I hope someone can shed more light on. Using hostap driver in AP mode, with a netgear MA311 or linksys WMP11, (both PCI), with older firmware NIC: id=0x8013 v1.0.0 PRI: id=0x15 v1.0.7 STA: id=0x1f v1.3.6 bridge eth-wlan works great, but after "upgrading" to newer firmware (to get essid hiding feature), NIC: id=0x8013 v1.0.0 PRI: id=0x0015 v1.1.1 STA: id=0x001f v1.7.4 bridge no longer works, even though there is no apparent (to me) indication of error. Is there info somewhere that tells about what was "fixed" in different firmware versions for prism chips, or better is there some workaround in the bridge code that I don't yet know about to overcome this issue? I guess I will test all the firmware versions I can get onto my cards and see where it broke, but if anyone already knows where the problem really comes from, please let us all know. Thanks, -Bob -- Bob Beers MIEEE 2415966
Bob Beers wrote: apparently a bunch of nonsense ... Sorry for the noise on the list, but let me close this thread, just incase someone hits it in the archives during a search. The hardware I was testing on had (unknown to me) changed, for the worse. I can't say exactly what in the hardware was causing the problem, but I'm not using it any more. The newer firmware does support bridging between eth and wlan just fine. -- Bob Beers MIEEE 2415966