DragonFly BSD
DragonFly kernel List (threaded) for 2004-08
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Wireless AP troubles


From: Walter Venable <weaseal@xxxxxxxxxxxxxxxxxx>
Date: Tue, 31 Aug 2004 07:31:04 -0400

I'm trying to set up a Wireless AP with DragonFly 1.1-CURRENT (cvsup'd 8/24).

The problem I am having is very strange: the machine contains 3 network interfaces, 1 is hard wired and goes to the outside world, and is called dc0. Another is a wired card that is hard wired and connects to the local network and is called dc1, which has an IP of 10.0.0.1 netmask 255.255.255.0. The last network interface is the wireless card, which is picked up by the wi driver, so it is wi0. It has the network IP of 10.0.0.3 netmask 255.255.255.255. Here is the output of ifconfig:

wi0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::201:3ff:fe79:82d9%wi0 prefixlen 64 scopeid 0x1
        inet 10.0.0.3 netmask 0xffffffff broadcast 10.0.0.3
        ether 00:01:03:79:82:d9
        media: IEEE 802.11 Wireless Ethernet DS/11Mbps <hostap>
        status: associated
        ssid awesome-wi 1:awesome-wi
        stationname DF-AP
        channel 6 authmode OPEN powersavemode OFF powersavesleep 100
        wepmode OFF weptxkey 1
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::2a0:ccff:fed2:a8d%dc0 prefixlen 64 scopeid 0x2
        inet 130.85.220.246 netmask 0xfffffffc broadcast 130.85.220.247
        ether 00:a0:cc:d2:0a:8d
        media: Ethernet autoselect (10baseT/UTP)
        status: active
dc1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
        inet6 fe80::2a0:ccff:fed6:d2f9%dc1 prefixlen 64 scopeid 0x3
        inet 10.0.0.2 netmask 0xffffffff broadcast 10.0.0.2
        ether 00:a0:cc:d6:d2:f9
        media: Ethernet autoselect (100baseTX)
        status: active

DHCP is running, and both wired and wireless clients get an IP without trouble. Wired clients are able to reach the outside world, the server, and each other.

Wired clients, however, may only ping each other. They cannot reach the server, nor the outside world.

I have followed the directions for FreeBSD 4 on http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html

So here is my /etc/sysctl.conf:
net.link.ether.bridge=1
net.link.ether.bridge_cfg="wi0,dc1"
net.inet.ip.forwarding=1


If anyone has any input it would be greatly appreciated.


-Walter Venable



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]