Skip to main content

Cisco 2600 as Internet Gateway

More
16 years 2 days ago #28138 by r0nni3
I saw that you didnt use NAT in your configuration. You might want to try the following:

access-list 160 permit ip 192.168.1.0 0.0.0.255 any
!
ip nat inside souce list 160 interface ethernet0/0 overload
!
interface e0/0
ip nat outside
!
interface e0/1
ip nat inside


Then try to ping to an internet address (like 212.115.192.193 my provider dns) from a host on the inside network.
You can also drop the ip default-gateway line. Also make sure your default route (0.0.0.0 0.0.0.0) is your ISP's gateway.
the route on the inside can be deleted to since this is a directly connected network.

Doing this should fix it.




Ron

Currently working as Cisco Engineer at Neon-Networking.

Certifications:
CCNA - Have it
CCNA Security - Have it
CCSP - Almost!!!!
CCIE Security - Not so far away dream
More
16 years 2 days ago #28140 by S0lo
Yes, I agree with r0nni3. Using NAT could solve it. Since most probably the netgear was doing the NAT for you before.

However, if that ISP switch was a router and is already doing NAT for you (which I doubt). And the old netgear was doing only internal routing (which I also doubt!!) then this will probably still not work.

Studying CCNP...

Ammar Muqaddas
Forum Moderator
www.firewall.cx
More
16 years 16 hours ago #28160 by ghostphace
Ron & Solo

Thanks very much the problem has been solved and now i'm left to do my ACL's to permit only who I want.

Regards
Chinedu
More
16 years 14 hours ago #28163 by S0lo

Ron & Solo

Thanks very much the problem has been solved and now i'm left to do my ACL's to permit only who I want.

Regards
Chinedu


Great!!. So did applying NAT solve it or was it something else?

Studying CCNP...

Ammar Muqaddas
Forum Moderator
www.firewall.cx
More
15 years 11 months ago #28244 by ghostphace
NAT Solved the problem.

Thanks
Time to create page: 0.129 seconds