Routing. What am I missing??? - Page 2

Michael Durham · ‎01-06-2013

I can ping from Durham's PC to Sommer's PC just fine.

I can ping the Inernet from Server Switch (4.2.2.2) just fine

But I cannot ping the Interent from Office Switch or Durham's PC. What am I doing worng?

OFFICE SWITCH

version 12.2

!

ip subnet-zero

ip routing

no ip domain-lookup

ip domain-name mtd.home

!

interface FastEthernet0/21

description Switch - Server_Switch 192.168.100.101 port fa0/1, Access Point - South_AP 192.168.100.105 port Ethernet 0, Servers

switchport trunk encapsulation dot1q

switchport trunk native vlan 100

switchport trunk allowed vlan 69,100,115,125,200

switchport mode trunk

spanning-tree portfast

!

interface FastEthernet0/24

description Workstation - Sixcore 192.168.69.150

switchport access vlan 69

switchport mode access

switchport nonegotiate

switchport port-security violation protect

switchport port-security mac-address sticky

spanning-tree portfast

!

interface Vlan69

ip address 192.168.69.2 255.255.255.0

ip helper-address 192.168.69.1

no ip route-cache cef

no ip route-cache

!

router eigrp 1577

no auto-summary

network 192.168.10.0 0.0.0.3

network 192.168.69.0

network 192.168.70.0 0.0.0.3

network 192.168.100.102 0.0.0.0

network 192.168.100.0

network 192.168.200.0

!

ip classless

ip route 0.0.0.0 0.0.0.0 10.0.0.254

ip route 10.115.0.0 255.255.255.0 192.168.100.101

ip http server

!

end

SERVER SWITCH

Current configuration : 9278 bytes

!

! Last configuration change at 16:28:07 Eastern Sun Jan 6 2013 by mdurham

! NVRAM config last updated at 17:23:11 Eastern Wed Jan 2 2013 by mdurham

!

version 12.2

!

ip subnet-zero

ip routing

no ip domain-lookup

ip domain-name mtd.home

!

interface FastEthernet0/1

description BLUE - Switch - Office_Switch 192.168.100.102 port fa0/21

switchport trunk encapsulation dot1q

switchport trunk native vlan 100

switchport trunk allowed vlan 1,69,100,115,125,200

switchport mode trunk

spanning-tree portfast

!

interface FastEthernet0/7

no switchport

ip address 10.0.0.254 255.255.255.0

spanning-tree portfast

!

interface Vlan69

description - User Vlan

ip address 192.168.69.1 255.255.255.0

ip helper-address 172.16.2.2

no ip route-cache cef

no ip route-cache

!

router eigrp 1577

no auto-summary

network 10.0.0.0 0.0.0.255

network 172.16.2.0 0.0.0.3

network 192.168.50.0 0.0.0.7

network 192.168.69.0

network 192.168.100.0

network 192.168.125.0 0.0.0.7

network 192.168.200.0

!

ip default-gateway 192.168.100.102

ip classless

ip route 0.0.0.0 0.0.0.0 10.0.0.1

ip route 10.115.0.0 255.255.255.0 10.115.0.1

ip http server

!

end

Any thoughts??

Michael

Michael Durham · ‎01-06-2013

fa0/7 is connected to the wireless bridge which has no IP address. At my neighbors he has a wireless bridge connected to the Netgear router on the 10.0.0.0 network. The Netgear is then connected to the 192.168.0.0 network which connects to the cellphone which is on hte 192.168.43.0 netowrk.

If only there were DSL or cable available here I would not need to do this werid setup.

kcnajaf · ‎01-06-2013

Hi,

Belive me you have interesting setup out there. It is taking time for me to digest this :-) Now i understand why the Office switch is not sending traffic to server switch.

But you mentioned that you are able to communicate between Durham's PC to Sommer's PC fine. I need to first understand how this is happening first. Could you please provide the ping and tracert to Sommer's PC from Durham's PC?

Regards

Najaf

Michael Durham · ‎01-06-2013

Pinging 10.0.0.2 with 32 bytes of data:

Reply from 10.0.0.2: bytes=32 time=4ms TTL=254

Ping statistics for 10.0.0.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 4ms, Maximum = 4ms, Average = 4ms

C:\Users\Michael T. Durahm>tracert 10.0.0.2

Tracing route to 10.0.0.2 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms 192.168.69.1

2 7 ms 5 ms 7 ms 10.0.0.2

Trace complete.

C:\Users\Michael T. Durahm>ping 10.0.0.1

Pinging 10.0.0.1 with 32 bytes of data:

Request timed out.

Ping statistics for 10.0.0.1:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Michael T. Durahm>tracert 10.0.0.1

Tracing route to 10.0.0.1 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms 192.168.69.1

2 * * * Request timed out.

3 * ^C

FYI, I can ping 10.0.0.1 form the Server switch but not from the Office swtich or my PC. Also, I am not sure if 10.0.0.2 is a PC or a printer but I can ping it from everywhere. That is real weird to me.

kcnajaf · ‎01-06-2013

Hi Michael,

From your responce

"FYI, I can ping 10.0.0.1 form the Server switch but not from the Office swtich or my PC. Also, I am not sure if 10.0.0.2 is a PC or a printer but I can ping it from everywhere. That is real weird to me."

So you are not sure the ip address which you are ping ie.10.0.0.2 is Sommer's PC or not? Right? Can you check the arp entry for ip address 10.0.0.2 on Server switch and match it with Somer's PC Mac address?

Also another thing which i didnt understnad is you have mentioned that there is a wireless bridge connected to Fas 0/7 and this bridge does not have an ip address. If that is the case why you have assigned an ip address on Fas 0/7? Could you please confirm the same?

Regards

Najaf

Michael Durham · ‎01-06-2013

I do not know the IP addresses of any of his equipment except the routers. If need be, I could ask him. I just know that I can ping 10.0.0.2 and 10.0.0.3 but what they are, i don't know. However, I am sure one of theim is his laser printer and the other one might be the access point/wireless bridge which would make since. I think all his PC's are on the 192.168.0.0 network of which I do not want/need access to except to get to the Internet.

When the wireless bridge (my side) does not have an IP address except to set it up and if it is in that mode it does not communicate with the access point. Should I not set an IP on fa0/7? I thought I had to so I could sent packets out that port. I cannot set ip route 0.0.0.0 0.0.0.0 out a layer 2 port. How would I let my system know about the 10.0.0.0 netowrk if I remove the IP assignment?

kcnajaf · ‎01-06-2013

Hi,

It is always a good to get a full view of network configurations but unfortunatly it looks like you dont have configuration visibility of beyond your device :-(

Coming back the point.

To be frank im not sure why you need the ip address on Fas 0/7. If your intension was to forward the traffic to that from office switch, it will not work they way currently it is set up.

Also you can not have an ip route point to a layer 2 port. It should be to an L3 ip address or interface.

Ok so in order for your office switch to forward the traffic to Server switch could you please try modifying you configuration as below. Please be aware that at this point im not sure the configuration change im recommenting here will break any of your current setup and hence i would recommand you to take a backup of configuration and save the configuration of the switches before you start making any change,

On Server Switch

interface FastEthernet0/7

no ip address 10.0.0.254 255.255.255.0

!

int vlan 10

ip address 10.0.0.254 255.255.255.0

!

interface FastEthernet0/7

switchport access vlan 10

!

interface FastEthernet0/1

switchport trunk allowed vlan 1,10,69,100,115,125,200

!

interface Vlan69

ip address 192.168.69.2 255.255.255.0

!

On Office Switch

int vlan 10

ip address 10.0.0.2 255.255.255.0

!

interface FastEthernet0/21

switchport trunk allowed vlan 1,10,69,100,115,125,200

!

interface Vlan69

ip address 192.168.69.1 255.255.255.0

!

Ensure the Durham's PC has the default gateway configured as 192.168.69.1.

Once you make this change try the trace to internet from Durham's PC and see if the traffic is going to 10.0.0.254 and then to 10.0.0.1

Regards

Najaf

Michael Durham · ‎01-06-2013

Okay so I tried something totally different here is what I did and my results.

I changed Server switch port fa0/7 from a router port back to a switchport and placed it into vlan 900.

I created interface Vlan 900 and gave it an IP of 10.0.0.254 255.255.255.0

Added a workstation on fa0/5 in Vlan 900 and gave it an IP of 10.0.0.125. It DOES get to the Internet via my neighbors connection.

I then allowed Vlan 900 to cross the trunk between the two switched.

From the Office switch and my PC I staill cannot getto the Internet.

Then I placed my PC's port into vlan 900 and gave my PC an IP of 10.0.0.150 and I can now get to the Internet via my neighbors connectoin.

No matter what I tried from the Office switch it always wants to route via 192.168.69.1 and never geto to the Internet. My guess is the for some reason my neighbor's router has no clue where 192.168.69.0 is thus no packets are returning to me.

I am going for a long shot tomorrow and setting up a Windows Interent connection sharing box so I can manually enter routes back to the 192.168.69.0 netowrk. That is how I am doing it with my Internet connection and it works. I'll report back.

This is not htat way I want my final setup to be. So if someone has another ideo.... I am very OPEN to it.

Maybe once I give my neighbor a REAL router/switch and I get off the 10.0.0.0 net and on his 192.168.0.0 net, I can get it to work the way I want it to. My last resort is to run a cat 5 cabke between us but I dont like that idea because of grounding and voltage issues that may arrise. Sure wish I had some fivor cable/adapters.

Michael Durham · ‎01-06-2013

Okay, I almost tried what you suggested. I forgot to allow Vlan 900 on the trunk. So I did as u suggested but used Vlan 900 and I had to use IP 10.0.0.253 on the Office switch as .2 is in use.

From the Office switch I CAN finally ping 4.2.2.2. BUT from the Durham PC I cannot still.

Here again is my Office switch cfg. I had to reload it a few times while changing things. This is the current settings:

Office_Switch#traceroute 4.2.2.2

Type escape sequence to abort.

Tracing the route to 4.2.2.2

1 10.0.0.254 4 msec 4 msec 4 msec

2 10.0.0.1 8 msec 8 msec 12 msec

3 192.168.0.1 4 msec 4 msec 8 msec

4 192.168.43.1 12 msec 12 msec 16 msec

5 66.174.39.17 144 msec 40 msec 48 msec

6 69.83.36.33 56 msec 36 msec 68 msec

7 * * *

8 69.83.33.13 52 msec 40 msec

Gateway of last resort is 10.0.0.254 to network 0.0.0.0

192.168.10.0/30 is subnetted, 1 subnets

C 192.168.10.0 is directly connected, Vlan1000

192.168.125.0/29 is subnetted, 1 subnets

D 192.168.125.0 [90/3072] via 192.168.69.1, 00:18:20, Vlan69

[90/3072] via 10.0.0.254, 00:18:20, Vlan900

172.16.0.0/30 is subnetted, 1 subnets

D 172.16.2.0 [90/28416] via 192.168.69.1, 00:18:20, Vlan69

[90/28416] via 10.0.0.254, 00:18:20, Vlan900

D 192.168.200.0/24 [90/3072] via 192.168.69.1, 00:18:20, Vlan69

[90/3072] via 10.0.0.254, 00:18:20, Vlan900

10.0.0.0/24 is subnetted, 1 subnets

C 10.0.0.0 is directly connected, Vlan900

192.168.50.0/29 is subnetted, 1 subnets

D 192.168.50.0 [90/3072] via 192.168.69.1, 00:18:20, Vlan69

[90/3072] via 10.0.0.254, 00:18:20, Vlan900

C 192.168.69.0/24 is directly connected, Vlan69

192.168.70.0/30 is subnetted, 1 subnets

C 192.168.70.0 is directly connected, FastEthernet0/23

192.168.100.0/24 is variably subnetted, 4 subnets, 2 masks

D 192.168.100.0/24 [90/3072] via 192.168.69.1, 00:18:20, Vlan69

[90/3072] via 10.0.0.254, 00:18:20, Vlan900

D 192.168.100.106/32

[90/156160] via 192.168.70.2, 00:22:36, FastEthernet0/23

C 192.168.100.102/32 is directly connected, Loopback1

D 192.168.100.103/32 [90/156416] via 192.168.69.1, 00:18:20, Vlan69

[90/156416] via 10.0.0.254, 00:18:20, Vlan900

S* 0.0.0.0/0 [1/0] via 10.0.0.254

Office_Switch#

!

interface FastEthernet0/21

description Switch - Server_Switch 192.168.100.101 port fa0/1, Access Point - South_AP 192.168.100.105 port Ethernet 0, Servers

switchport trunk encapsulation dot1q

switchport trunk native vlan 100

switchport trunk allowed vlan 69,100,115,125,200,900

switchport mode trunk

spanning-tree portfast

!

interface Vlan900

ip address 10.0.0.253 255.255.255.0

!

router eigrp 1577

no auto-summary

network 10.0.0.0 0.0.0.255

network 192.168.10.0 0.0.0.3

network 192.168.69.0

network 192.168.70.0 0.0.0.3

network 192.168.100.102 0.0.0.0

network 192.168.100.0

network 192.168.200.0

!

ip classless

ip route 0.0.0.0 0.0.0.0 10.0.0.254

ip http server

!

end

FROM THE DURHAM'S PC

C:\Users\Michael T. Durahm>ping 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:

Request timed out.

We ar egetting close!!!

kcnajaf · ‎01-06-2013

Hi Michael,

Indeed we getting close:-)

What is the switch port configuration looking like where Durham's Pc is connted? Could you please get the tracert from this PC to internet?

Regards

Najaf

Michael Durham · ‎01-06-2013

C:\Users\Michael T. Durahm>ping 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:

Request timed out.

!

interface FastEthernet0/24

description Workstation - Sixcore 192.168.69.150

switchport access vlan 69

switchport mode access

switchport nonegotiate

switchport port-security violation protect

switchport port-security mac-address sticky

spanning-tree portfast

!

kcnajaf · ‎01-06-2013

Hi Micheel,

Tracert to internet please from this Pc?

Regards

Najaf

Michael Durham · ‎01-06-2013

Sorry, that was a ping. Here is the tracert:

Tracing route to 4.2.2.2 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.69.1

2 * * * Request timed out.

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

Michael Durham · ‎01-06-2013

I still think there is a problem with the 10.0.0.0 network not knowing how to get back to the 192.168.69.0 network.

I think the packet leaves my frouter with a FROM 192.168.69.0 netowrk headder so the 10.0.0.1 router does not know where that is. The FROM IP address is a 192.168.69.0 address becuse I have all the networks on the 3550 switch. If I had a router with tow network ports on it and I just had one network on each port then entered static routes back to my other IP's, that might fix the problem.

Or, if there is a way to make sure all packets leaving out the 10.0.0.0 network hada FROM address on the 10.0.0.0 network, that would work even better.

kcnajaf · ‎01-06-2013

Hi Michael,

It will help me if you could provide me the trace from this PC to internet. This will let me understand how far the traffic is going.

Regards

Najaf

Michael Durham · ‎01-06-2013

Sorry I sent the wrong thing. Its getting very late and I am tired/wasn't thinking.

Tracing route to 4.2.2.2 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.69.1

2 * * * Request timed out.

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.