Routing with gateway on a different subnet

Unanswered Question
Jun 20th, 2009

I'm trying to configure a router but ISP provided address doesn't match up.

range: 10.30.153.1 to 128

subnet mask: 255.255.255.0

Gateway: 10.23.99.1

If I use any IP from the range above on Windows XP, I can connect to the internet.

The ISP said it should work. And most of their clients are configured that way. And they don't have problems.

It just doesn't make sense.

Anybody have any idea why its working? Can someone provide more info why it works on XP but not on my router?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Giuseppe Larosa Sat, 06/20/2009 - 09:04

Hello Riann,

what if you configure on the router a default route and you specify only the outgoing interface

ip route 0.0.0.0 0.0.0.0 fas0/0

in this way your device relies on proxy-arp on ISP device

I guess that is only a fake GW and PCs use proxy-ARP concept to find their way to the internet.

Hope to help

Giuseppe

r.banez Sun, 06/21/2009 - 01:18

After I've added the following:

ip route 0.0.0.0 0.0.0.0 fa0/0

no ip route 0.0.0.0 0.0.0.0 10.23.99.1

I can now ping the gateway (10.23.99.1) but still no route to the internet. I cannot also ping any other IP outside/past the 10.23.99.1.

I was told by ISP that the IP range they gave and the gateway is on the same vlan. And that IP is on a Router with Firewall.

My guess is that his equipment checks all packets and see next hop is his IP, it picks up the data and route it. But wouldn't it be noisy on his network?

Giuseppe Larosa Sun, 06/21/2009 - 03:29

Hello Riann,

until the provider device doesn't build a NAT entry for your router ip address you cannot reach the internet.

Also you need a DNS server.

Be aware that some provider device can be configured with a limit in max. number of MAC addresses to be served that is usually the reason to place a router there to overcome this limitation.

However, you also need to NAT on your router to use a PC that is connected to an internal interface in another subnet: you should nat using the "WAN" interface name: that IP subnet is not known to the service provider device.

int f0/0

ip nat outside

int f0/1

ip nat inside

ip addr 10.100.100.1 255.255.255.0

access-list 11 permit 10.100.100.0 0.0.0.255

ip nat inside source list 11 int f0/0 overload

Hope to help

Giuseppe

r.banez Sun, 06/21/2009 - 09:06

Giuseppe,

Hi!

I just reviewed my original post. I forgot to mention that the IP were changed to private IP numbers for security reason, but keeping it close to the original IP as much as possible.

The IPs that was provided by the ISP are all public routable IPs.

NAT is already in place in my router (for internal network PCs).

The XP workstation is connected in parallel with the router. That one works but router doesn't. The router can only ping the ISP gateway but I can't route to it.

Actions

This Discussion