Re: Atheros and SIS bridging problem

On Tue, Jan 11, 2005 at 09:23:08AM -0800, Ben Becker wrote:
> [Laptop]--------(sis0)-[FreeBSD Bridge]-(ath0)--------[FreeBSD AP]
>  
> There seems to be a problem with bridging ath0 and sis0.  I have 1 IP
> assigned to ath0 which is 192.168.1.3, and I've sysctl'd
> 'net.link.ether.bridge.enable=1' and
> 'net.link.ether.bridge.config=ath0,sis0'.  From the bridge, I can ping
> the AP (192.168.1.1) and the laptop (192.168.1.5).  However I can't
> ping from the laptop to the AP or from the AP to the laptop.

Hi,

    Have you tried ng_bridge(4)? My own experience is similar with
yours, and the problem like yours is sovled via ng_bridge(4).  Example
scripts to setup ng_bridge(4) is at
/usr/share/examples/netgraph/ether.bridge.

    My setup is:
[Desktop]------(ed0)-[freebsd bridge]-(fxp0)----[LAN]

    With bridge(4), the Desktop is able to access the LAN, but not the
bridge. No response at all. With ng_bridge(4), both LAN and the
freebsd bridge are accessible. The freebsd bridge is -current, and
NICs above are:

fxp0: <Intel 82801DB (ICH4) Pro/100 VE Ethernet> port 0x8000-0x803f mem 0xc0201000-0xc0201fff irq 11 at device 8.0 on pci2
ed0: <LEMEL LM-N89TX> at port 0x4000-0x401f irq 11 function 0 config 16 on pccard0

    BTW, bridge(4) performance is better than ng_bridge(4).

Cheers,
-- 
Clive Tong-I Lin | http://tongi.org | PGP KeyID: A008C03E