Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Jun 2005 16:14:52 -0500
From:      "Jason T. Nelson" <jtn@jtn.cx>
To:        freebsd-isp@freebsd.org
Subject:   back to back bridges
Message-ID:  <20050601211452.GA49444@jtn.cx>

next in thread | raw e-mail | index | archive | help

--0OAP2g/MAC+5xKAE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I've run into a bridge problem that has got me stumped. Here's the basic
layout:

                   AP         2km 802.11a link       client
local net <---sis0|--|ath0<---------------------->ath0|--|sis0---> remote n=
et

The "local net" consists of a Soekris 4526 with a 802.11a card running in=
=20
hostap mode and other access points (non-FreeBSD) as well as a router out t=
o=20
the Internet connected to an ethernet switch. The "remote net" consists of=
=20
nothing more than 2 other APs (non-FreeBSD) and a hub. The client box=20
(Soekris 4526 with 802.11a card) associates to the AP and passes traffic=20
back and forth just great, with the exception of occational duplicated pack=
ets
which doesn't seem to harm things. BOTH the AP and the client are running
the kernel bridge code. This seems to perform just great at the AP end,
however, this is not so at the client end. Through some experimentation, I
have discovered the following:

* On the client, the IP address *must* be on the ath0 interface, otherwise
  the client is unpingable and otherwise invisible to the AP and the "local
  net". Likewise, the IP address *must* be on the sis0 interface on the AP
  or no packets ever seem to make it to the wireless link.
* Packets never seem to cross the wireless link from the local net to the
  remote net, with the exception to the IP address bound to the ath0
  interface on the client. Similarly, packets originating from the remote
  net never seem to cross the wireless link unless they come from the IP
  address on the ath0 interface.

Doing some sniffing on both networks, it would seem that ARPs from one net
are never forwarded across the wireless link to the other net. Why would th=
is=20
occur? Is there some sort of odd magic involved with two bridged ethernets=
=20
sharing a common wireless link?

--=20
Jason T. Nelson <jtn@jtn.cx>                     http://www.jtn.cx/~jtn/
GPG key fingerprint =3D 6272 5482 EDDD D0A3 FED2  262A FABB 599D FF67 6C9E
disclaimer: My opinions are my own. Don't bother my employer about them.

--0OAP2g/MAC+5xKAE
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFCniVM+rtZnf9nbJ4RAjKbAJ9UZeoe2qHa8CfjY9xPG6T8zZCzQgCgib5X
7BuYKBpK5qxHwbP/ZC4iuBg=
=I7uQ
-----END PGP SIGNATURE-----

--0OAP2g/MAC+5xKAE--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050601211452.GA49444>