netgear fvs338 ROUTER SETTING NEEDED FOR VPNPHONE

[fyrman]

Hello all, I need to know what the router setting would be for the vpn remote phone? I am aware of the tip # 184. I have spoken with support and they are stuck.

vpn sets up
phone sits at discover (ip of ip ofice)
all routes are set up correctly.

Support seams to think the router is not allow the signal through to the gateway.

Monitor shows nothing!!

thanks

ron k

 

[tlpeter]

Can you provide more details?
What is the iproute in the ipo?
What is the iprange used in mode config?
What phone did you use?
Can you provide everything? (no logins or external ip needed)


When you pay peanuts, you get monkeys!

I'm not insane, my mother had me tested!

 

[intrigrant]

http://www.4shared.com/document/8-yViaW6/Avaya_-_Netgear_VPN_Phone.html

you van use this as a config form

 

[fyrman]

tlpeter: here goes

IP OFFICE SITE:
172.16.1.0/24 NETWORK
172.16.1.1 ROUTER/GATEWAY
172.16.1.125 IP OFFICE 406V2 5.0
(TB 184 OPTION 2) IKE/VPN
ROUTER =NETGEAR FVS338
alg =option checked
172.16.1.12 tftp server (3rd party)


vpn phone site
type=5610sw
192.168.1.0/24
192.168.1.1 gateway/router
192.168.1.55 ip of telephone on lan
172.16.22.55 vrtual ip of telephone

IP OFFICE
ROUTES=
virtuaL IP ARDRESS 172.16.22.5

IP ROUTES
0.0.0.0 > 255.255.255.254 > 172.16.1.1
0.0.0.0 > 0.0.0.0 >172.16.1.1
0.0.0.0 > 0.0.0.0 >172.16.1.125

THE VPN does connect, i show no traffic with monitor.

rmk

 

[amriddle01]

In the IP Office you can't have two 0.0.0.0 routes, the system will not alarm about it but it doesn't work properly if at all. Reason being they are a catch all route and two routes catching all traffic but sending to different locations = no workie

You just need the 0.0.0.0 route for the LAN port going to the net for the other LAN port you need to be slightly more specific even if it's only the first octet or so

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[amriddle01]

If those two 0.0.0.0 - 0.0.0.0 routes are for the same LAN port you only need the one actually targetting the router/gateway for that subnet.

The "0.0.0.0 > 255.255.255.254 > 172.16.1.1" route is nonsense and will never match anything

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[intrigrant]

You can have two or more routers on the same subnet each having a different connection to maybe the same destination ( one Internet and one Dial-UP ? ).
You can select which route is preferred above the other by giving it a lower metric as the second route.
This way you can have a lot of gateways in a single subnet.

 

[amriddle01]

True, but is that the case here? I suspect it's the usual easy mistake (as it doesn't error)

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[intrigrant]

As most people don't know how metrics work I always assume it is a fault.
It is sad to see what some people can make of a routing list, I see a lot of installations were they put the local LAN IP Address in the routing table pointing to the local router, how to upset a stupid electronic device? By adding silly routes...

 

[fyrman]

thanks all.

found router at remote site blocking o/b traffic.

rmk

 

[amriddle01]

Cool, still best to tidy those routes up though

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[hairlessupportmonkey]

andy - think of those two blank routes as a backup ;-)

but it should be OK, as the IPO reads from the top down determining which matches and which works.

ACSS - SME