Date: Tue, 1 Nov 2005 18:37:16 +0100 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: Jason Morgan <jwm-freebsd@sentinelchicken.net> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Quick Routing Question Message-ID: <20051101183716.44ebc62b@localhost> In-Reply-To: <20051101171540.GA91080@sentinelchicken.net> References: <20051101171540.GA91080@sentinelchicken.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Jason Morgan <jwm-freebsd@sentinelchicken.net> wrote: > On Tue, Nov 01, 2005 at 11:24:59AM -0500, Steve Bertrand wrote: > > And again, tcpdump is a very good tool. The -i switch tells it what > > interface to listen on, so if the wireless side of the router works > > but you can't ping across to the cabled side, then apply the cabled > > interface to the -i switch and you'll be able to see if traffic is > > making that far, and if it is, if it's even attempting to go back. > > Ok, it looks like it was an issue with the default settings on the > Linksys (and is still somewhat of an issue). I can now connect to > systems in each of the two subnets and I also have routing to the > outside world from both subnets. My only remaining issue is getting > to the web app setup for the Linksys - I can only do it from a local > address (meaning a 192.168.1.x address). The Linksys refuses > connections from my 10.0.0.x subnet. Is this a NAT issue? Do you have NAT enabled between 192.168.1.0 and 10.0.0.0? If you do, the Linksys shouldn't see any 10.0.0.x addresses. If you don't, this is probably a security measure. Perhaps the Linksys supports a white list to allow access from non-local addresses. Fabian -- http://www.fabiankeil.de/ [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFDZ6fMjV8GA4rMKUQRAjz8AKCrrOL+nFlrUc2uJzR0oRZ8yxEuLwCfb3hF KnVa9zvaYVKatWqCNCa3yc8= =jsTc -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051101183716.44ebc62b>