Unless I'm reading this wrong you just need a basic interface overload
config...something like this:
int eth0/0
!interface traffic sources from
ip nat inside
int eth0/1
!interface going to devices without gateway
ip nat outside
ip nat inside source list NATDIS interface eth0/1 overload
ip
On 11/09/2017 06:10 PM, Aaron Gould wrote:
You may be able to accomplish it with proxy arp and not have to nat
I recall proxy arp will allow hosts to arp for everything, and the router to
arp reply to any and all arps on the subnet with its own mac address
-Aaron
My stupid dumb
You may be able to accomplish it with proxy arp and not have to nat
I recall proxy arp will allow hosts to arp for everything, and the router to
arp reply to any and all arps on the subnet with its own mac address
-Aaron
___
cisco-nsp mailing list
On 11/9/17 4:17 PM, Nick Cutting wrote:
There is more to it.
What is the model and code version of the router? - we need these to help you
with the configuration.
Fair enough.
Its a Cisco 7201 running 12.2(33)SRE7
Thank you.
___
cisco-nsp
@puck.nether.net
Subject: [c-nsp] cisco ip nat question
This message originated outside of your organisation.
Hi,
I have a bunch of dumb devices that don't know how to deal with a default
gateway. They all live in a subnet 172.16.144.0/20.
A router lives here @ 172.16.144.1, and my device
Hi,
I have a bunch of dumb devices that don't know how to deal with a
default gateway. They all live in a subnet 172.16.144.0/20.
A router lives here @ 172.16.144.1, and my device management
station lives on another network, say 10.0.1.0/24.
What I think I want, is for packets
@puck.nether.net
Subject: [c-nsp] Cisco IP nat question
I have a 7201 connected to network 172.16.144.0/20, and it's interface
is 172.16.144.1 (gi0/1. for example). I was wondering how I might
arrange things so that any source address - inbound to 172.16.144.0/20
is natted with a source
I have a 7201 connected to network 172.16.144.0/20, and it's interface
is 172.16.144.1 (gi0/1. for example). I was wondering how I might
arrange things so that any source address - inbound to 172.16.144.0/20
is natted with a source address of 172.16.144.1? The clients are dumb
and
