think that *if* your ISP is cooperative enough, he can create routing rules saying
that your ip-public can be found behind their's own. Also he can make an aliases (YOUR
public in THEIR's machine), and a ipfilter/ipw rule saying that 'any request shoud be
redirected to YOUR private address'
A
On Tue, Oct 23, 2001 at 08:59:18PM -0500, Kirk Strauser wrote:
>
> Well, we have a whole public /24. Only the routing block is private, which
> I'm sure will seem like a better idea once I coerce this $@#!() FreeBSD box
> to bend to my will.
If you have a whole /24, and you need to do stuff oth
At 2001-10-24T01:30:35Z, Kris Kirby <[EMAIL PROTECTED]> writes:
> 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
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 in
At 2001-10-24T00:03:51Z, Barney Wolff <[EMAIL PROTECTED]> writes:
> 1. You don't need the public address configured on the same nic as the
> private - packets to the public address will be accepted even if they come
> in via the outside nic.
I will occasionally need to connect *out* from gw1 f
1. You don't need the public address configured on the same nic as
the private - packets to the public address will be accepted even
if they come in via the outside nic.
2. Both ping and traceroute offer options to set the source addr. rtfm.
On Tue, Oct 23, 2001 at 05:41:18PM -0500, Kirk Strau
