wireless access point

just an update in frustration over the instructions in the freebsd handbook.
when setting up a FreeBSD wireless access point that is ALSO your
gateway one must add the loopback device to the list of bridged interfaces.
handbook shows:
# sysctl net.link.ether.bridge_cfg="wi0,xl0"

for <=5.1, where you should instead have:
# sysctl net.link.ether.bridge_cfg="wi0,lo0,xl0"

hope this saves someone a headache in the future. the problem i was
having was that data recieved on the wireless would be blindly sent out
on the local net. pings to the gateway were responded to on the lan as
well instead of being sent back to the wireless connection. when the
ssid on the AP was changed, it was seen on the clients so i knew that
was working at least.
now if only i can get some sort of mac filtering working
i wonder how many services FreeBSD on a pentium 166 w/64mb ram can
support
i'd like to see a Windows "server" running on a 166 doing printing, dns,
dhcp, nt domain controller, gatteway, wireless, and scheduled backups to
tape.

--
- - J A M E S - - P O O L - -
< james AT hal-pc.org >

C:\WINDOWS C:\WINDOWS\GO C:\PC\CRAWL
- - - - - - - - - - - - - - -

On Wed, 04 Feb 2004 12:34:13 -0600
"james <at> hal-pc.org" <"james <at> hal-pc.org"> wrote:

J> i wonder how many services FreeBSD on a pentium 166 w/64mb ram can
J> support

Quite a lot if you keep memory hungry things like X11 off it
Once upon a time ftp.cdrom.com (aka ftp.freebsd.org then) was a P90 with
72GB of disc.

--
C:>WIN | Directable Mirrors
The computer obeys and wins. |A Better Way To Focus The Sun
You lose and Bill collects. | licenses available - see:
| http://www.sohara.org/