YES, IT WORKS! I can use my Geode based fit-pc (http//www.fit-pc.com
) as a bridge between my ethernet based internet to my wireless laptop (core2 duo Hasee)!
Both use the rt73usb module.
The bridge module didn't work, but I did get iptables up and running.
Here's what I needed to do
1. Compile a git-sources kernel under gentoo for the fit-pc (version 2.6.27-git9), add ip_filter modules and rt2x00 modules.
2. Copy the kernel sources to my laptop and compile for my Ubuntu based laptop
3. Fiddle about until the wireless network started working.
4. Follow the directions on creating a iptable - based bridge since the bridge.ko module didn't work from [url5u7e1mck]http://kunxi.org/archives/2007/05/poor-mans-wireless-network[/url5u7e1mck]
5. Curse, cry do it all 5 times till it started working.
I just want to thank all who contributed to this.
I guess I was a little too hasty, something is not working right in the Ad-Hoc networking.
Setup two computers using rt73usb chips, kernel 2.6.27, Ad-Hoc networking, no encryption.
When one of the computers drops out and then comes back, the network usually comes back up no problem.
But every now and then both sides get different cell ids, and doing
iwconfig wlan0 essid myid
does not reset the device, it still reports the old, incorrect, cell id. Of course there is no connection if the cell ids on both sides are not identical.
Is this a bug?
By cell id, do you mean the essid, or bssid?
essid. I don't even know what is bssid. For what it's worth, here is my iwconfig wlan0
wlan0 IEEE 802.11bg ESSID"Home"
ModeAd-Hoc Frequency2.422 GHz Cell 1660C89E5AE4
Retry min limit7 RTS throff Fragment thr=2352 B
Link Quality0 Signal level0 Noise level0
Rx invalid nwid0 Rx invalid crypt0 Rx invalid frag0
Tx excessive retries0 Invalid misc0 Missed beacon0
The bssid is the mac address. If you run "iwconfig wlan0 ap XXXXXXXXXXXX", where XXXX... is the mac address of the other cell, does that help?
If you cannot get things to work, you should see if there isn't already a thread about this issue in the rt2x00 section. If not, create one, and post a debug trace when the problem occurs.