On Sat, Aug 04, 2007 at 08:50:59PM +0200, Jurjen Oskam wrote: > On Wed, Jul 18, 2007 at 11:56:18AM -0600, Daniel Melameth wrote: > > [ral PCI card performed poorly in hostap mode; packet loss etc] > > Have you tried setting the channel and/or forcing the mode? I also > > have a ral-based AP and while it performs fairly well, its reliability > > and consistency does not appear to be as good as the wi-based APs. > > (Sorry for the late reply - I was away for a few weeks) > > Well, the problem was the antenna and/or the placement of the antenna. I > used a separate antenna from the start, but for testing I tried another > one in a different location (unreachable with the first antenna). This > solved the problem entirely: even ping -f doesn't lose one single packet > nor reports any duplicates, and that is with ping -f running for a good > 30 seconds. > > There's one thing that I noticed though, the contents of hostname.ral0 are: > > inet 192.168.2.1 255.255.255.0 NONE media autoselect mediaopt hostap nwid > stupendous mode 11g > > When I put a "nwflag nobridge" in there, it doesn't work. It complains > about not being able to set the flag. (Sorry, I didn't copy-paste the error > message). Only after the interface is placed in hostap mode, I can set the > nobridge flag, both with ifconfig and netstart ral0. Does this sound > familiar to anyone? Should I gather more data so I can create a proper > report? > > -- > Jurjen Oskam > > Savage's Law of Expediency: > You want it bad, you'll get it bad.
You have to put nwflag nobridge on it's own line within your hostname.ral0 file. So put all the inet stuff then hit enter and add the nwflag nobridge line. -- James Turner BSD Group Consulting http://www.bsdgroup.org
