Re: Fake address for NAT connection support (IPv4)

Ken Sims <ng3122@kensims.#nospam#.net.invalid> writes:

Hi Mark -

On Tue, 27 Mar 2007 11:00:01 -0400, Mark.Carroll@xxxxxxxxxx (Mark T.B.
Carroll) wrote:

But, can I achieve the same effect without needing another machine?
(Or another ISP. (-:)

With my DSL modem the default configuration was to function in NAT
mode, however it was easy to change it to bridge mode, which allowed
my own Linux-based router to have my public static IP address on the
WAN interface.

Unfortunately, I can't currently do that with my ISP: to get my traffic
in and out I /have/ to have on my WAN interface the RFC1918 static
address they assigned to me. If I could have my public static IP address
on the WAN interface there'd be no problem whatsoever. (So I was
wondering if I can have the protocol-content-rewriting work as if my WAN
interface had a different IP to what it actually does.)

-- Mark
.

Relevant Pages

  • Re: How to redirect ftp port for inbound traffic?
    ... redirected to a designated internal hosts. ... I thought it should be very simple to do SDM but I can not get it ... My WAN interface has ISP dynamically assigned IP address. ...
    (comp.dcom.sys.cisco)
  • Re: Fake address for NAT connection support (IPv4)
    ... (Or another ISP. ... With my DSL modem the default configuration was to function in NAT ...
    (comp.os.linux.networking)
  • Re: Possible DNS problem
    ... > packets as spoofed packets, ... a Cisco IOS IP access rules. ... WAN interface. ... As for NAT, all NATs don't allow U-Turns, just as a traffic ...
    (microsoft.public.win2000.dns)
  • Re: Terminal release ip command?
    ... and configuration is much easier. ... In my case I have two dynamically assigned IP addresses from my ISP. ... I run without NAT, or firewall, everything works, and my configuration ...
    (comp.sys.mac.system)
  • Re: PIX 501 Routing vs. NAT
    ... what are you trying to accomplish? ... You can assign as many IP address to the wan interface, however without NAT, you can not publish any services behind the firewall unless your machines reside on the same subnet as the outside interface, which means you are using no nat rules. ...
    (comp.dcom.sys.cisco)