|reply to harry |
Re: Client has no internet access but router is connected to int
Here's the specific items I see messed up in your config OP
- VLAN 1 is "IP NAT OUTSIDE" -- generally VLAN 1 is used for your INSIDE hosts and interfaces
- you've specified "ip route 0.0.0.0 0.0.0.0 Dialer0" -- generally speaking, if your WAN interface facing the
ISP is getting an address via DHCP, you do NOT need to set a static like this.
ip nat inside source list NAT interface Dialer0 overload
ip access-list standard nat
Got the right config here, but watch out about your ACL names... they CAN be case-sensitive.
To keep it simple, redo your config as
ip nat inside source list 1 interface Dialer0 overload
ip access-list 1
Fa0 on the 1801 is the ROUTED port, as you can assign an IP address to the INTERFACE itself.
Fa1 - 8 are the SWITCHED ports, they can be put INTO a VLAN, and the VLAN can have an IP address,
but NOT the individual interfaces themselves.
You can reconfigure this yourself, or you can take a look at the forum FAQ for a basic config to crib.
ip address 192.168.1.1 255.255.255.0
ip nat inside
The "inside" LAN interface needs a fixed address -- it's your router and DHCP server.
The default route to dialer0 is correct -- it's a PPP interface (dsl). 'tho unnecessary, as the ATM interface will trigger the dialer as soon as the interface comes up.