Strange Aussie Vonage Blues

Posts: 1 · New Forum Member Joined: Jul 10, 2005 Posts: 1

Hey all - I've got an odd problem.
I'm posting this for a friend, but, i'm pretty familiar with the problem so hopefully y'all can help us out.

We purchased the Vonage wireless router in the US of A and set it up. It worked fine, ingoing and outgoing calls, the whole shibang.

However, in Melbourne, the service provider is e-cable, which requires users to log in via a web-based interface before browsing outside the subnet and login page.

The ip assigned after logging in is a 192.168.*.* which leads me to believe this is a private network. After plugging the router into the wall, and being assigned a wireless IP, the IP being assigned is still directly from the e-cable provider. I believe it's 192.168.180.* opposed to 192.168.15.* (which is what it should be)

Wondering if we're dealing with a lost cause. For the life of me I can't understand how the router isn't assigning the IP address. pinging 192.168.15.1 (the ip of the router) times out as well.

So, for some reason, even though the connection is wireless (which MUST be the router), the router isn't visible.

The phone1 LED is also dark.

We're havin' a hell of a time with this, and if any of you guru's could lend a hand we'd be much obliged.

thanks

Posts: 1424 · Posted: Mon Jul 11, 2005 11:20 am Post subject: Re: Strange Aussie Vonage Blues

dribble wrote:

We purchased the Vonage wireless router in the US of A and set it up. It worked fine, ingoing and outgoing calls, the whole shibang.

What model?

dribble wrote:

However, in Melbourne, the service provider is e-cable, which requires users to log in via a web-based interface before browsing outside the subnet and login page.

The ip assigned after logging in is a 192.168.*.*

Are you saying that when you connect to e-cable that you get one IP address and that after you login you get a new one?

dribble wrote:

After plugging the router into the wall, and being assigned a wireless IP, the IP being assigned is still directly from the e-cable provider. I believe it's 192.168.180.* opposed to 192.168.15.* (which is what it should be)

I assume here you are talking about a computer being assigned an address by the router. You should try this without the router connected to your ISP and see if you can verify that DHCP and NAT are enabled and specifically what address range is in use.

dribble wrote:

Wondering if we're dealing with a lost cause.

If you have to log in and then get a new ISP IP address then the only thing I can think that would work is that after you log in you tell the router to renew its DHCP lease via the router's web server.

dribble wrote:

For the life of me I can't understand how the router isn't assigning the IP address. pinging 192.168.15.1 (the ip of the router) times out as well.

I suspect that if you are being given a 192.168.180.* address that the subnet mask is set up so 192.168.15.* isn't accessible. Create a route to 192.168.15.0/255.255.255.0 through your default interface.

It might be helpful to post the results of ipconfig/all from your computer.

Directly connected to e-cable, before you log in
Directly connected to e-cable, after you log in
When connected to wireless router, router not connected
When connected to wireless router, router connected to e-cable