Bridge, networking, wireless cards, and ypbind.... (*sigh*
Paul Pathiakis
paul at pathiakis.com
Sat Jun 10 02:46:13 UTC 2006
Hi,
I wish this was a little less complicated, but it seems pretty straightforward
and I got it to work in no time at all, so I think I have it right.
Machines:
Two AMD Socket 462 boxen
512 MB RAM
RTL8169 Gb chipset (reX) cards
Wireless card is Atheros 5212 based
OK. Everything on the NIS/NFS machine has worked fine and I just added a
wireless card. I'm going wireless on a few machines to test the wireless as
I'm in an apartment and I'm thinking the landlord isn't going to like me
hacking up the walls for wall plates, etc
So... I add the Atheros card, configure it to be the hostap (ap->access point
and voila' it works. Nice)
On the NIS Server machine, I have the 192.168.1.x with 255.255.255.0 address
space.
In loader.conf, I have:
if_ath_enable="YES"
In rc.conf, I have:
nis_server_enable="YES"
nis_client_enable="YES"
nfs_server_enable="YES"
cloned_interfaces="bridge0"
ifconfig_bridge0="addm re0 addm ath0 up"
ifconfig_re0="inet 192.168.1.11 netmask 255.255.255.0"
defaultrouter="192.168.1.12"
ifconfig_ath0="ssid my_ap mode 11g mediaopt hostap"
my ifconfig -a shows:
ath0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::213:46ff:fe94:75c5%ath0 prefixlen 64 scopeid 0x1
ether 00:13:46:94:75:c5
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
status: associated
ssid my_ap channel 1 bssid 00:13:46:94:75:c5
authmode OPEN privacy OFF txpowmax 30 protmode CTS burst
dtimperiod 1 bintval 100
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::20e:a6ff:fe71:45b1%vr0 prefixlen 64 scopeid 0x2
inet 192.168.1.11 netmask 0xffffff00 broadcast 10.1.1.255
ether 00:0e:a6:71:45:b1
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active
bridge0: flags=8043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether ac:de:48:f4:6b:4e
priority 32768 hellotime 2 fwddelay 15 maxage 20
member: ath0 flags=3<LEARNING,DISCOVER>
member: vr0 flags=3<LEARNING,DISCOVER>
my sysctl.conf has (these were gotchas I wasn't expecting..)
net.inet.ip.check_interface=0
net.link.bridge.pfil_member=0
net.link.bridge.pfil_onlyip=0
net.link.bridge.pfil_bridge=0
Everything good so far. I have a wireless card bridged to my Gb ethernet and
it seems to work.
ypwhich shows the machine bound to this server as it is the only master.
Ok, the first wireless client gets the next Wireless card (for those wanting
to know the name and model, they are D-LINK DWL-G520 108G card).
my rc.conf has:
ifconfig_ath0="inet 192.168.1.24 netmask 0xffffff00 ssid my_ap mode 11g
mediaopt adhoc"
defautrouter="192.168.1.12"
nis_client_enable="YES"
ifconfig -a shows:
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::213:46ff:fe94:75c3%ath0 prefixlen 64 scopeid 0x1
ether 00:13:46:94:75:c3
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <adhoc>
status: associated
ssid my_ap channel 3 bssid 02:13:46:94:75:c5
authmode OPEN privacy OFF txpowmax 36 protmode CTS burst bintval 100
I assume that since the bssid shows the MAC address of AP, it is bound.
I can ping the x.x.x.11 address. I can ping the x.x.x.12 gw address. I can
resolve out to the world. Life is great, right?
No, I can't ypbind and only the default accounts are coming up.
I can mount NFS exported drives from the server with no issue.
if I ypwhich it tells me the domain is not bound. (Yes, the domainname is
correct)
I believe I'm missing something with UDP or ICMP or some such. This is
driving me 3 days crazy. Is there a sysctl or something I'm missing? Does
this seem like an RPC or UDP issue.
Part of my trouble shooting had me hardwiring the machines instead of
wireless. No sooner did I boot up the client then it was bound to the
server. Why does it refuse to do this on the wireless?
Thank you for your wisdom oh-wise-and-powerful list....
Paul Pathiakis
More information about the freebsd-questions
mailing list