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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Passing traffic from HWIC-4ESW to WAN(s)

Status
Not open for further replies.

osuman

Technical User
Nov 22, 2000
281
US
Hello again,
So I have a semi-complicated setup that I'm trying to get working one piece at a time. I've also posted in another thread about load balancing, but before I get to that, I want to ensure that basic connectivity is working.

Basically what I have is a 2811 with a HWIC-4ESW that I will use to drop off LAN connections to my switches. I also have multiple (3) DSL connections that I want to share amongst all the LAN users.

For now I setup 1 of the 4ESW ports as part of a VLAN, but I think I'm missing a basic step about how to route traffic between the VLAN and the DSL connections.

2 of the DSL connections go through a modem and then into the integrated FE ports. The 3rd one goes into a WIC-1ADSL. I've tested both the modem DSL connections and am sure they are providing Internet access.

I am able to obtain a DHCP address through the 4ESW as well as telnet to the router. In addition, the router can resolve names so I think it has an Internet connection. (Pinging websites fails, but I think something else may be blocking ICMP). So it seems each part is working correctly.

I guess the question is, what am I missing so that I can access the Internet from the WAN connections through the 4ESW VLAN? Do I need a static route? A loopback address? Or I've also read something about bridging? Is it an access-list problem?

Here is the relevant parts from my running config:

2811#show run
Building configuration...

Current configuration : 4710 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname 2811
!
boot-start-marker
boot-end-marker
!
logging buffered 51200 warnings
!
no aaa new-model
!
resource policy
!
ip subnet-zero
!
!
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.1.254
!
ip dhcp pool everyone
network 192.168.1.0 255.255.255.0
default-router 192.168.1.254
dns-server 4.2.2.2 4.2.2.1
lease 30
!
!
ip domain name yourdomain.com
!
!

!
bridge irb
!
!
interface Loopback0
no ip address
!
interface FastEthernet0/0
description DSL(Modem) from XXX-XXXX
ip address 10.0.1.2 255.255.255.0
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
!
interface FastEthernet0/1
description DSL(Modem) from XXX-XXXX
ip address 10.0.2.2 255.255.255.0
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
!
interface FastEthernet0/3/0
description Local LAN access point
switchport access vlan 2
!
interface FastEthernet0/3/1
!
interface FastEthernet0/3/2
!
interface FastEthernet0/3/3
!
interface ATM0/2/0
description DSL(WIC-1ADSL) from XXX-XXXX
no ip address
no ip mroute-cache
no atm ilmi-keepalive
dsl operating-mode auto
hold-queue 224 in
pvc 1/150
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
!
interface Vlan1
no ip address
!
interface Vlan2
ip address 192.168.1.254 255.255.255.0
ip nat inside
ip virtual-reassembly
!
interface Dialer0
ip address dhcp
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer-group 1
ppp pap sent-username <username> password 0 <password>
!
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer0
!
no ip http server
ip http authentication local
ip http secure-server
ip http timeout-policy idle 5 life 86400 requests 10000
ip nat inside source list 1 interface Dialer0 overload
!
access-list 1 permit 192.0.0.0 0.255.255.255
dialer-list 1 protocol ip permit
!
!
control-plane
!
!

!
line con 0
login local
line aux 0
line vty 0 4
privilege level 15
login local
transport input telnet ssh
line vty 5 15
privilege level 15
login local
transport input telnet ssh
!
scheduler allocate 20000 1000
!
end

Any help is much appreciated.
 
Changing it to use vlan 1 seems to have corrected this. I'm not sure why it didn't work with vlan 2.

Oh well.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top