Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Cisco 2 ethernet
- Thread starter zas1
- Start date
I'd go with a Cisco 1005 or 1605."
Both of which are no longer produced. With the 837 ADSL router you get a 2 logical Ethernet Ports (new IOS enables a 2nd logical Ethernet port on one of the 4 switch ports). Either that or a 1721 with a WIC-1ENET module. Cisco also have some new 800-series routers - 850 and 870 series that have 2 Ethernet interfaces (851 & 871 have 10/100 Ethernet for LAN & WAN interfaces).
If you are looking at 2nd hand then look for an 837 or a 1720/1721 (or 1750/1751) and a WIC-1ENET module.
Andy
Both of which are no longer produced. With the 837 ADSL router you get a 2 logical Ethernet Ports (new IOS enables a 2nd logical Ethernet port on one of the 4 switch ports). Either that or a 1721 with a WIC-1ENET module. Cisco also have some new 800-series routers - 850 and 870 series that have 2 Ethernet interfaces (851 & 871 have 10/100 Ethernet for LAN & WAN interfaces).
If you are looking at 2nd hand then look for an 837 or a 1720/1721 (or 1750/1751) and a WIC-1ENET module.
Andy
- Thread starter
- #4
What are you trying to achieve? NAT/PAT can be configured in different ways so if you can be a bit more specific as to what you are trying to NAT if may be more helpful.
1. Are you trying to NAT an entire network? e.g. internet access for clients?
2. Are you trying to allow access to internal hosts from the outside (internet)?
3. Do you have multiple outside IP addresses to play with?
There are many more questions really but if you could give us an idea of what it is you want to NAT then we can probably offer more help. Either that or have a look on CCO at the NAT documentation....
Andy
1. Are you trying to NAT an entire network? e.g. internet access for clients?
2. Are you trying to allow access to internal hosts from the outside (internet)?
3. Do you have multiple outside IP addresses to play with?
There are many more questions really but if you could give us an idea of what it is you want to NAT then we can probably offer more help. Either that or have a look on CCO at the NAT documentation....
Andy
- Thread starter
- #6
Do you require static NAT'ing for each of your hosts i.e.
All IP to and from host 192.168.4.10 must translate to 201.20.20.10. Or can this be dynamic and on demand i.e. Any host internally 192.168.4.x needs to be translated to an address from the range 201.20.20.1 through 201.20.20.254?
If its a one to one translation you want then you need to create static NAT entries for each of your inside hosts to its equivilent outside address:
ip nat inside source static 192.168.4.10 201.20.20.10
ip nat inside source static 192.168.4.11 201.20.20.11
ip nat inside source static 192.168.4.12 201.20.20.12
!etc
If you want it dynamic and on demand then you can create an ACL to identify the inside network addresses you want to NAT, a NAT pool to use and apply this all to one line of code:
ip access-list standard Inside-Hosts
permit 192.168.4.0 0.0.0.255
!
ip nat Outside-Addresses 201.20.20.1 201.20.20.254
!
ip nat inside source list Inside-Hosts pool Outside-Addresses
!
If this is an internet connection then be careful as you don't want to open up your network to attack from all the gremlins out there.
Good luck
Andy
For either situation you also need to identify your Inside and Outside interfaces with the interface command 'ip nat inside/outside'
All IP to and from host 192.168.4.10 must translate to 201.20.20.10. Or can this be dynamic and on demand i.e. Any host internally 192.168.4.x needs to be translated to an address from the range 201.20.20.1 through 201.20.20.254?
If its a one to one translation you want then you need to create static NAT entries for each of your inside hosts to its equivilent outside address:
ip nat inside source static 192.168.4.10 201.20.20.10
ip nat inside source static 192.168.4.11 201.20.20.11
ip nat inside source static 192.168.4.12 201.20.20.12
!etc
If you want it dynamic and on demand then you can create an ACL to identify the inside network addresses you want to NAT, a NAT pool to use and apply this all to one line of code:
ip access-list standard Inside-Hosts
permit 192.168.4.0 0.0.0.255
!
ip nat Outside-Addresses 201.20.20.1 201.20.20.254
!
ip nat inside source list Inside-Hosts pool Outside-Addresses
!
If this is an internet connection then be careful as you don't want to open up your network to attack from all the gremlins out there.
Good luck
Andy
For either situation you also need to identify your Inside and Outside interfaces with the interface command 'ip nat inside/outside'
- Status
Similar threads
- Locked
- Question