Date: Sat, 29 Sep 2007 21:00:18 -0700 From: Christopher Cowart <ccowart@rescomp.berkeley.edu> To: Simon Timms <stimms@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Bridging interfaces Message-ID: <20070930040018.GI19429@hal.rescomp.berkeley.edu> In-Reply-To: <204aabdc0709292049p7f50ee47r5ec7155d338fb4c9@mail.gmail.com> References: <204aabdc0709291806t67c9f31u1ab05e5cdd83f258@mail.gmail.com> <20070930020410.GG19429@hal.rescomp.berkeley.edu> <204aabdc0709292049p7f50ee47r5ec7155d338fb4c9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--6e/6p6d7vICK/GCJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 29, 2007 at 09:49:36PM -0600, Simon Timms wrote: > That makes a lot of sense, but I suppose I still don't understand why this > isn't working. The handbook section on routing is pretty basic and it se= ems > to come down to setting net.inet.ip.forwarding to 1 if you want to route > packets between interfaces on a dual-homed host. I'm able to reach hosts= on > both subnets from the router and my routing table looks like: >=20 > Internet: > Destination Gateway Flags Refs Use Netif > Expire > default wireless UGS 0 9905 > sis0 > localhost localhost UH 0 134 > lo0 > 192.168.1 link#1 UC 0 0 > sis0 > orinoco 00:d0:09:f8:f7:5a UHLW 1 268 lo0 > 192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb 1 87 > sis0 > 192.168.2 link#2 UC 0 0 > rl0 > 192.168.2.255 ff:ff:ff:ff:ff:ff UHLWb 1 87 > rl0 Are your 192.168.2/24 machines configured to use 192.168.2.2 as their default router? They don't know where 192.168.1.2 is, because they=20 don't see it as being on the same link. The subnet mask is used to determine this kind of reachability. You could probably use 192.168.1.2 as your default router, as long as you created a static route `route add 192.168.1/24 192.168.2.2', telling the system that to get to 192.168.1/24, the next-hop is 192.168.2.2. This seems needlessly complex when you can just configure 192.168.2.2 as your default router and skip the static route configuration all together. Regardless, bridging isn't going to help unless the host and the default router have the same subnet configurations. --=20 Chris Cowart Lead Systems Administrator Network & Infrastructure Services, RSSP-IT UC Berkeley --6e/6p6d7vICK/GCJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iQIVAwUBRv8fUiPHEDszU3zYAQKvzA//aTnSVQQBjs0bY+fVzfXrzB/El4v/Lyrd SvPEs1Yz6s2bsAUQ93UhjZJlC9MsWvJFxa7j39OD4Jb1QCo5KJMIhpq/N+bZP1cJ lx12dWXctPfpkZn1e8qTvxPUm6pCyqIPAVGAlMNb3o4Sd+uHTN7hRQaU/ujkpkH/ Y8CJ11Xnu9Bo/ft5gp/TNywqdw7eRDwRNQYxD3atMJA6VNSeC5azgwe4ZKUUMfk+ 5n2OkSdF+BuXr4gkGlITDVWkBNENKQSumxg7SULvTEt4Hi1b5o8DCON+tQCcmq7J Tltm6LbMyBM8Uk359mD35Mos1xTCWXjV4WInYRZsJvqvWqFuJJq7cdAMFcpTZWUc YK1xKFFadfKtniQxzPAqKBDbrS4U0H4ETTu+K8BBV5lAj3TRdUPXoc8+18PO98CM bTGoa2ZIISpIdOy7aPP/5fckrutWTDeCDupoKm+BdO9+KZZZWcn4ZTALkqapO6L4 K0G+92b+D8kFJxlHsUXJQo8zEa03yHO6Ywqo81iiz4bcr6ESLB2izuUH1QylJ7fB i7M4LpTOY98EDG6rmqvC138usYMLOSt9tt60hz4+vhzMYCTGc/OeyAXxQZ1hqjKR iaeVa1mleb+tLAI7afXokEzS7pES3qvbP+K/Ss4uWNB9EGR1gTko1oh6UavHE4Va yeZb/aV9jro= =XcNE -----END PGP SIGNATURE----- --6e/6p6d7vICK/GCJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070930040018.GI19429>