Routing traffic from different subnets - Netgear UTM25

I have a 4 site setup connected via Intenode IBC. All cisco 800 series and managed by Internode. No problem there.

At the main site there is a SOHO Internet connection connected to a Netgear UTM25. All Internet traffic for all 4 sites is sent out this Netgear router by way of a static route in the Cisco 800 at the main office.

Internet traffic for the HQ site routes fine but the 3 remote sites cannot get any Internet pages to load, but DNS resolves fine.
It was working fine before we installed the Netgear - previously we had a Linksys ADSL Modem/Router and the Internet traffic for remote sites was fine - just had static routes setup in the Linksys and away it went.

Details:
HQ Lan:     10.6.10.0/24 (Cisco is 10.6.10.254, Netgear is 10.6.10.1 - Static Route in Cisco to 10.6.10.1 for all Internet bound traffic.
Site 1 Lan: 10.6.11.0/24 (Cisco is 10.6.11.254)
Site 2 Lan: 10.6.12.0/24 (Cisco is 10.6.12.254)
Site 3 Lan: 10.6.13.0/24 (Cisco is 10.6.13.254)

Netgear is doing PPPOE connected to ADSL modem in bridge mode.

I have tried static routes in the Netgear for each of the remote sites but no luck. RIP is turned on and the Netgear appears to be sharing routing info with the CISCO. (See pic)

I also have Lan Multihoming settings (See pic)

Any help appreciated. Lan Multihoming settingsrouting-table.jpg
TrentSlaterAsked:
Who is Participating?
 
MikeKaneConnect With a Mentor Commented:
I would say yes.    

What you need to end up with are entries that look like

10.6.10.0    255.255.255.0  0.0.0.0            0
10.6.11.0    255.255.255.0  10.6.10.254    2
10.6.12.0    255.255.255.0  10.6.10.254    2
10.6.13.0    255.255.255.0  10.6.10.254    2


Maybe you have old RIP info somehow (i'm not very familiar with the netgear stuff).   But turning it off and going to static routes should work....
0
 
MikeKaneCommented:
The static routes in the netgear should have the eqivilant of "If destination is 10.6.11.0/24 then send to 10.6.10.254", "If destination is 10.6.12.0/24 then send to 10.6.10.254"," If destination is 10.6.13.0/24 then send to 10.6.10.254".   I didn't see that.  


Can any remote router ping the Netgear?  
0
 
TrentSlaterAuthor Commented:
Static Routes 2Sorry - I had removed the routes to see if RIP was working. See new Pic.
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
MikeKaneCommented:
What is that 4th column?   Is this a gateway?   If yes, then it looks like you have the 10.6.11,12,and13 subnets defined as vlans on this device.  IS that correct?    If they are defined on the device, then the routing would use the perceived, directly connected network before the static route to 10.6.10.254


0
 
TrentSlaterAuthor Commented:
There is only 1 vlan - the default one 10.6.10.0/24. The other info I think is being polulated by the cisco RIP info
0
 
MikeKaneCommented:
No doubt about the single vlan...   But it almost looks like the 10.6.13.0/24 network has conflicting info.   Can you snip that image and include the colum headings?     I'm assuming its "Description, subnet, mask, gateway, metric"    If that is correct, it seems that 10.6.13.0 is directly connected to defaultVLAN ?  

0
 
TrentSlaterAuthor Commented:
routing with columnsYes it is gateway - I see what you mean. Should I turn RIP off and see if those direct entries disappear.
0
 
TrentSlaterAuthor Commented:
Routing 4
Looks better - it wasnt RIP but the LAN MUlti homing section. I added this when the static routes didnt work. I will try this config today and let you know if it is fixed.

Thanks.
0
 
MikeKaneCommented:
Great
0
 
TrentSlaterConnect With a Mentor Author Commented:
All fixed. The static routes were set on the WAN Interface, not the LAN Interface. Silly huh!
Thanks MikeKane - you get the points as, well....you were the only one that replied :-)

Definitely didnt need the LAN multihoming settings - I think the fact that the Netgear UTM defaults to the WAN Interface when you create a new route is what threw me. The routes actually need to be sent the CISCO router which is on the LAN - sounds really simple when you think about it.
0
 
TrentSlaterAuthor Commented:
NETGEAR TECHNICIAN picked up that routes were on the WAN Interface, not the LAN Interface
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.