Connecting home lab to the internet HELP! (Att uverse 2wire box)

Hello,

I am trying to connect my home lab to the internet, I got this ATT uverse box that has everything integrated (Wireless, switch, modem).

Here is my lab set up, I am working from host in blue

I am able to ping from HQ to the ATT box (192.168.1.254) but I cannot ping anywhere in the internet.

Here is my running config from HQ

HQ#show runBuilding configuration...

Current configuration : 891 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname HQ
!
enable secret 5 $1$Y6Zd$yhtlMkP.zPH550P/hVtYq1
!
ip subnet-zero
!

!
interface FastEthernet0/0
ip address dhcp
duplex auto
speed auto
!
interface Serial0/0
no ip address
shutdown
!
interface Serial1/0
ip address 192.168.19.233 255.255.255.252
clockrate 64000
!
interface Serial1/1
ip address 192.168.19.229 255.255.255.252
clockrate 128000
!
interface Serial1/2
ip address 192.168.19.225 255.255.255.252
clockrate 64000
!
interface Serial1/3
no ip address
shutdown
!
router rip
version 2
network 192.168.19.0
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0
no ip http server
ip pim bidir-enable
!
!
!
line con 0
line aux 0
line vty 0 4
password 7 121A0C041104
login
line vty 5 15
password 7 104D000A0618
login
!
!
end

HQ#ping 192.168.1.254

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.254, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
HQ#ping 213.86.83.116

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 213.86.83.116, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

HQ#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

C 192.168.1.0/24 is directly connected, FastEthernet0/0
192.168.19.0/24 is variably subnetted, 6 subnets, 2 masks
R 192.168.19.64/26 [120/1] via 192.168.19.230, 00:00:29, Serial1/1
R 192.168.19.0/26 [120/1] via 192.168.19.234, 00:00:16, Serial1/0
C 192.168.19.232/30 is directly connected, Serial1/0
C 192.168.19.224/30 is directly connected, Serial1/2
C 192.168.19.228/30 is directly connected, Serial1/1
R 192.168.19.128/26 [120/1] via 192.168.19.226, 00:00:02, Serial1/2
S* 0.0.0.0/0 is directly connected, FastEthernet0/0
HQ#

I cannot ping from my pc to ATT box, but I can ping HQ's S1/0

C:\Users\Jose>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Jose>ping 192.168.19.233

Pinging 192.168.19.233 with 32 bytes of data:
Reply from 192.168.19.233: bytes=32 time=18ms TTL=254
Reply from 192.168.19.233: bytes=32 time=18ms TTL=254
Reply from 192.168.19.233: bytes=32 time=18ms TTL=254
Reply from 192.168.19.233: bytes=32 time=18ms TTL=254

Ping statistics for 192.168.19.233:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 18ms, Average = 18ms

C:\Users\Jose>tracert -4 192.168.1.254

Tracing route to 192.168.1.254 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.19.1
2 22 ms 22 ms 22 ms 192.168.19.233
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * ^C

Here is also my SF running config:

SF#sho runBuilding configuration...

Current configuration : 932 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname SF
!
boot-start-marker
boot-end-marker
!
enable password cisco
!
no aaa new-model
no network-clock-participate slot 1
no network-clock-participate wic 0
ip cef
!
!
multilink bundle-name authenticated
!

!
!
archive
log config
hidekeys
!
!
!
interface FastEthernet0/0
ip address 192.168.19.1 255.255.255.192
duplex auto
speed auto
!
interface Serial0/0
ip address 192.168.19.234 255.255.255.252
!
interface Serial0/1
no ip address
shutdown
!
router rip
version 2
network 192.168.19.0
no auto-summary
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Serial0/0
!
ip http server
no ip http secure-server
!
!
!
control-plane
!
!
!
line con 0
line aux 0
line vty 0 4
password cisco
login
line vty 5 181
password cisco
login
!
!
end

SF#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

192.168.19.0/24 is variably subnetted, 6 subnets, 2 masks
R 192.168.19.64/26 [120/2] via 192.168.19.233, 00:00:07, Serial0/0
C 192.168.19.0/26 is directly connected, FastEthernet0/0
C 192.168.19.232/30 is directly connected, Serial0/0
R 192.168.19.224/30 [120/1] via 192.168.19.233, 00:00:07, Serial0/0
R 192.168.19.228/30 [120/1] via 192.168.19.233, 00:00:07, Serial0/0
R 192.168.19.128/26 [120/2] via 192.168.19.233, 00:00:07, Serial0/0
S* 0.0.0.0/0 is directly connected, Serial0/0

Thanks for your time and help.

Lab.JPG

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

joluis9

I did some more research and I found this forum (Re: U-verse for BUSINESS? : 2Wire 3600HGV bridge m... - AT&T Community Support) with how to "bridge" the ATT box. It worked for me I know have the public IP address in my outgoing interface. I have set up NAT (I thought that the ATT box would have done for me, but apparently not). I still haven't find out why I cannot ping from computer to Att box (192.168.1.254). I don't see any routing problem do you?

Thanks.

NetworkVeteran

Sleepy here, so perhaps I missed something, but the first thing that jumps out--

ip route 0.0.0.0 0.0.0.0 FastEthernet0/0

You used a lazy static route. Your cheap router may not support proxy arp. Try using a normal static route. You know, the kind where you specify the default gateway's IP address. Even if this is not the root problem, fix this so you're not proxy-arp'ing every dang address on the Internet.

Also, you don't mention configuring your ATT box to know how to route and NAT for the 192.168.19.x range. Without those, you won't have much luck pinging Internet websites.

MAC_Addy

I'd also change the speed/duplex from your HQ router to the uverse router, I've had problems with setting connections up using auto. Like NetworkVeteran said, without a route and NAT setup, you don't have much luck.

tearofs

For the subnet between ATT and HQ, are you sure it is /30? cuz you are also runing DHCP to get .72

Also, I don't think you are advertising 192.168.1.0 in RIP

Assuming ATT is runing NAT,

just point your default route to .1.254 instead of the interface

Futura

Probably need to create a nat pool on your HQ router, the create a nat overload rule for that sinigle address.
set your default gateway on the hq pointing to your AT router and see if you can ping 4.2.2.2, do this is before you start with the rest of the
network, first job is to get HQ working.

RouteMyPacket

NetworkVeteran wrote: »

Sleepy here, so perhaps I missed something, but the first thing that jumps out--
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0

You used a lazy static route. Your cheap router may not support proxy arp. Try using a normal static route. You know, the kind where you specify the default gateway's IP address. Even if this is not the root problem, fix this so you're not proxy-arp'ing every dang address on the Internet.

Also, you don't mention configuring your ATT box to know how to route and NAT for the 192.168.19.x range. Without those, you won't have much luck pinging Internet websites.

Nice catch, I caught a statement like that yesterday on my 1841, wasn't able to login to it and got an "Low Memory Try Again Later" message when consoled in.

Bounced it, logged in and saw the default route directed to the interface. Ugh!