Wireless AP troubles

Walter Venable weaseal at planethalflife.com
Tue Aug 31 16:35:37 PDT 2004


Erik P. Skaalerud wrote:

Walter Venable wrote:

Walter Venable wrote:

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:
...


I wanted to also mention that dmesg is spitting out this error over 
and over:

arp: 10.0.0.48 is on dc1 but got reply from 00:02:2d:57:a3:4a on wi0

To me it really looks like the error is in the bridging but I don't 
know what to do to fix it.


You're not supposed to have a IP on both the wired and the wireless 
interface if you are going to have both the interfaces on the same 
network. Remove the IP from the wireless device, and make sure briding 
is working properly.

- Erik
The problem persists without an IP on the wireeless interface. 
Originally, it didn't have one.  Oddly, the wireless clients can't even 
get an IP from DHCP when wi0 didn't have an IP, however I have again 
removed it, although as I said the problem persists.

How can I test if bridging is working properly?  Here is the output of 
sysctl:
$ sysctl -a | grep bridge
net.link.ether.bridge_cfg: "wi0,dc1"
net.link.ether.bridge: 1





More information about the Kernel mailing list