Date: Wed, 24 Oct 2001 01:30:35 +0000 (GMT) From: Kris Kirby <kris@catonic.net> To: Kirk Strauser <kirk@strauser.com> Cc: <freebsd-net@freebsd.org> Subject: Re: Silly problem has me stumped Message-ID: <Pine.BSF.4.33.0110240123240.98768-100000@spaz.catonic.net> In-Reply-To: <87vgh5naag.fsf@pooh.int>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 Oct 2001, Kirk Strauser wrote: > I already RTFM, and TFM doesn't say a thing about how to do what I want, > except for command line options of specific clients, which doesn't solve my > problem. Yeah. The issue here is that the machine is picking the IP address as the "closest" IP to the internet -- the RFC1918 address over the WAN link. My mind is also mud at the moment, but this much I can thing of: By forcing ssh, et al. to bind to a specific IP, you can avoid the non-traceable issue. And a tidbit just surfaced from the mud! Use ipfw + natd to nat anything that would directly come from / to the private address and use "natd -u -a 1.2.3.1" (assumes .1 is the gateway). Careful that you don't wind up looking at every single packet though. The other solution would be to accuse your ISP of being incompentent / cheap, etc. and complain until you get a public /30 for the WAN link. I'm a fascist; I wouldn't have taken a link without a public WAN ip. ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. <kris@nospam.catonic.net> | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0110240123240.98768-100000>