I have been trying to teach myself tcp/ip networking, so pardon me if this is a pretty "duh!" question. I set up a home wireless network for my computer on 802.11b, through a linksys wireless nic and wireless router. A buddy of mine is also on a home network through a linksys router, though his is wired. When we tried to do an ftp tranfer with him as the server, I couldnt get any kind of connection. I had port forwarding set up on both routers, but thats not the main thing I dont understand. What I don't get is that I can't ping his router at all. We are both through the same cable ISP, and both router LAN IP's are 196.128.1.1. My main issue is the inability to ping, I can worry about the FTP later. Any insight would be greatly appreciated. Thank You!
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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Question concerning routing
- Thread starter MarkSte
- Start date
Am I reading that right, "We are both through the same cable ISP, and both router LAN IP's are 196.128.1.1."
Can you tell me what IP address you are pinging to/from?
IF you are using 192.128.1.1 and your friend is using the same address space and you two are not on the same physical network, as in LAN; then No this won't work.
Please provide more info. Todd VanDerwerken, CCNA, CCDA
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
Can you tell me what IP address you are pinging to/from?
IF you are using 192.128.1.1 and your friend is using the same address space and you two are not on the same physical network, as in LAN; then No this won't work.
Please provide more info. Todd VanDerwerken, CCNA, CCDA
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
- Thread starter
- #3
im sorry, i mistyped that, it was a bit early and i was frustrated. we are both on internal networks behind routers. both routers are using 192.168.1.1 as the lan ip address, but they have seperate wan ip addresses. we do both subscribe to the same isp, cox cable. subnet mask for routers is class c. my lan ip is 192.168.1.101, his is 192.168.1.100. not sure what else you need to know. thank you.
- Thread starter
- #4
"my lan ip is 192.168.1.101, his is 192.168.1.100" That is your issue. Your thinks that his network is directly connected to your router. It won't "route" a packet if it thinks it is connected to that network.
are you NAT'g your 192.168.1.101 into the Cox WAN address on your router before it goes to Cox? If you are and if he is then you need to ping his WAN address not his LAN address. Todd VanDerwerken, CCNA, CCDA
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
are you NAT'g your 192.168.1.101 into the Cox WAN address on your router before it goes to Cox? If you are and if he is then you need to ping his WAN address not his LAN address. Todd VanDerwerken, CCNA, CCDA
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
- Thread starter
- #6
First of all that is a private address and Cox will not router that, but let's table that for a moment.
Secondly, the IP's might be different but from what you said in your response "subnet mask for routers is class c. my lan ip is 192.168.1.101, his is 192.168.1.100"
That tells the router that 192.168.1.101 and 192.168.1.100 live on the same network.
So if you are pinging from your network with a source address of 192.168.1.101 to his WAN IP address x.x.x.x, when his router gets that ping his router will look to see where network 192.168.1.0 (based on your class C mask) lives. IF his router is configured like your, Class C mask and an IP address of 192.168.1.101, then his router will think the network 192.168.1.0 is directly connected to him and therefore it will not route it back to you.
HTH Todd VanDerwerken, CCNA, CCDA
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
Secondly, the IP's might be different but from what you said in your response "subnet mask for routers is class c. my lan ip is 192.168.1.101, his is 192.168.1.100"
That tells the router that 192.168.1.101 and 192.168.1.100 live on the same network.
So if you are pinging from your network with a source address of 192.168.1.101 to his WAN IP address x.x.x.x, when his router gets that ping his router will look to see where network 192.168.1.0 (based on your class C mask) lives. IF his router is configured like your, Class C mask and an IP address of 192.168.1.101, then his router will think the network 192.168.1.0 is directly connected to him and therefore it will not route it back to you.
HTH Todd VanDerwerken, CCNA, CCDA
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
- Thread starter
- #8
ok, i understand now. so how would i make it so that when i send the ping out, it shows to his router as being from my routers ip instead of mine? and once this is done, how will my router know that the information should go back to my computer instead of another one on my network?
You need to have your routers do Network Address Translation (NAT).
When you ping from your LAN to his WAN address, your router will change your source address from your LAN address to your WAN address, which I assume is a Cox address. So when his router see's your packet come in it will have a source address of your WAN interface and will be able to route back to it. Have your friend configure NAT the same way and it should work. Todd VanDerwerken, CCNA, CCDA
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
When you ping from your LAN to his WAN address, your router will change your source address from your LAN address to your WAN address, which I assume is a Cox address. So when his router see's your packet come in it will have a source address of your WAN interface and will be able to route back to it. Have your friend configure NAT the same way and it should work. Todd VanDerwerken, CCNA, CCDA
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
- Thread starter
- #10
- Thread starter
- #11
Then it must have NAT configured by default also, because what you have described won't work as is. Todd VanDerwerken, CCNA, CCDA
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
Technical Consultant
"If at first you don't succeed...then sky diving isn't for you!"
- Status