Router/GS502 Help!

[chpalmer]

The Lan ip not the wan ip...

The grandstream will attempt to block anything it thinks is on its own subnet from getting out of its wan port. If its close enough things can get messy.

[dswartz]

Sigh, I thought you meant the address of the 502 on the LAN, not it's LAN address. Yes, having these overlap is a recipe for disaster, and not all routers diagnose this

[chpalmer]

Its the old double nat pitfall...


I would set up the 502 so that it hands out addresses in its new lan subnet also so that getting into its lan port is not a problem.

[dswartz]

this is not really double NAT, it's a routing issue. routers can't have two interfaces in the same subnet...

[digger16309]

Thanks for all of your replies. Although I'm still kind of confused.

I have the 502 behind my Linksys router, so I'm not using the LAN port on the 502 at all.

I'm only using the WAN port connected to an open port coming off the router.

There is no double NAT issue and even if that was a possibility, I set it to Bridge mode anyway.

What is happening is that yes, the 502 is dynamically assigned an address like 192.168.1.103. All is well until the router decides to refresh the LAN IP addresses on the network for some reason and then the 502 and one of my computers conflict getting the IP address renewed causing the 502 to go offline and into cycling mode. Then when I statically assign it 103, there is conflict again later as my router tries to assign 103 to something else.

So as I understand your posts, if I change the static address for the 502 to outside the DHCP range, like 192.168.1.99 (but using the same subnet 255.255.255.0), then the conflicts should go away, correct?

If so, I'll try that tonight.

I still have a question from my first post. What is the benefit of running DHCP on my home network. Couldn't I just turn that off and assign static addresses to all of my devices?

What are the drawbacks, if any, of not using DHCP?

Again, thanks for your help!

[chpalmer]

I have the 502 behind my Linksys router, so I'm not using the LAN port on the 502 at all.

I'm only using the WAN port connected to an open port coming off the router.

There is no double NAT issue and even if that was a possibility, I set it to Bridge mode anyway.

What is happening is that yes, the 502 is dynamically assigned an address like 192.168.1.103. All is well until the router decides to refresh the LAN IP addresses on the network for some reason and then the 502 and one of my computers conflict getting the IP address renewed causing the 502 to go offline and into cycling mode. Then when I statically assign it 103, there is conflict again later as my router tries to assign 103 to something else.

So as I understand your posts, if I change the static address for the 502 to outside the DHCP range, like 192.168.1.99 (but using the same subnet 255.255.255.0), then the conflicts should go away, correct?

If so, I'll try that tonight.

I still have a question from my first post. What is the benefit of running DHCP on my home network. Couldn't I just turn that off and assign static addresses to all of my devices?

What are the drawbacks, if any, of not using DHCP?

Again, thanks for your help!

Technically the voip portion of the 502 is on its lan subnet. In its own kind of way though...

But I see your problem better now after I have had a little sleep in the last hour. (new child yesterday. )

Yes assign it something else out of the Linksys dhcp range...


Yes you could turn dhcp off but it would make it more difficult to add devices or computers later. Instead you might change the range to something higher in the subnet. I set mine from xx.xx.1.201 - xx.xx.1.225 and then statically assign everything below that.

Good Luck. And sorry for my confusion...

[VOIPoTim]

But I see your problem better now after I have had a little sleep in the last hour. (new child yesterday. )

Congrats. I'm childless and glad I get to sleep as much as I want. Plan for it to stay that way for a while too.

[chpalmer]

this is not really double NAT, it's a routing issue. routers can't have two interfaces in the same subnet...

Yea I know but you would be surprised how many times I get called from friends where this is the issue. And these are guys that build their own.

[dswartz]

Yes, this should eliminate the issue.