[kamalpa]

I have read through the forum and found some conflicting answers on what my issue may be and potential solutions and would appreciate it if someone could clarify what my next step should be.

I have the following setup using Broadvoice(BV):

Motorola Cable Modem->SPA-2100->Netgear MR814->2 PC's (wired+wireless)

Initially BV worked but I was not able to connect to the internet then I read on the SPA website that in this config that the IP of the router should not be 192.168.0.x so I changed it to 192.168.13.x and everything worked BUT my PC's frequently lose internet connection and when this occurs I am unable to even access my router.

Now, I've read a couple of posts that suggest that the IP addresses of the router and SPA-2100 should have the same first 3 sets of digits i.e. I should have the router as 192.168.0.2 - would this fix my issue?

I've also read that people have the router in front of the SPA-2100 - I tried this and although BV worked fine I was unable to connect to the internet at all.

I've seen some posts suggesting that I upgrade the firmware (it's currently 2.0.5a) but on the Sipura site it seems to suggest that BV remotely upgrades this on a as-needed basis.

Okay, enough rambling. here are some simple questions:
- should I change my setup to have the router before the SPA-2100?
- should I change the IP address of the router to 192.168.0.2?
- should I upgrade the firmware to 2.0.5d without contacting BV?
- should I contact BV and have them sort this out :wink:

Thanks in advance.

[jadams]

What firmware are you running? I had the exact same problem with mine until I updated to the lastest one.

[kamalpa]

I have 2.0.5a, I believe the latest is 2.0.5d.

Did you have the same setup? Modem->SPA->router and the router as 192.168.x.x and the SPA as 192.168.0.x.

[jadams]

Yup. I even setup so I had the cable modem hooked right into the sipura. Then from the sipura into a hub and then out to my network. It would work for a random amount of time then just die out. I would have to restart the cable modem to get the internet connection back. Just restarting the router wouldn't fix it. I upgraded to the newest firmware and that fixed it.

[kamalpa]

I will upgrade the firmware when I get home tonight and post the results.

Thanks for the help.

[kamalpa]

I called Broadvoice BV to see if they'd update the firmware and I was told by the really nice & helpful tech support person that they've had other users call with this problem and their current unofficial but soon-to-be official solution is to simply change the IP on the SPA-2100 to 10.10.10.1.

Apparently, I'm paraphrasing, if the router & SPA IPs too close ressemble then it causes these issues. I'm not an expert so I will take this on face value and hope that this fixes my problem.

Failing this I might ask them to update my firmware remotely, otherwise I'll try & do it myself. They're waiting to approve the latest firmware 2.0.5d until the fax support is implemented or something...

[kamalpa]

FYI

I was still experiencing dropped internet with the SPA IP set to 10.10.10.1. So I called Broadvoice back and the said that it was strange that my setup was doing this and that it was also strange that the previous tech had set my IP to 10.10.10.1?!?

This next tech said he would remotely upgrade my firmware version and change the IP to 172.x.x.x. Well he didn't upgrade the firmware because I checked & it's still at 2.0.5a.

However it's been a couple of days and I haven't experienced any dropped connections yet...

I did move it to behind my router today because for some reason it was stopping me using Windows remote desktop connection via my co.'s VPN.

[mberlant]

VPNs, like SIP, can tolerate no more than one NAT transition between the client device and the public internet. This is why you needed to put your SPA behind your router.

As for the addressing problem, it is always unwise and sometimes unworkable to have adjacent NAT segments share overlapping IP address space. Let's look at your example where your SPA-2100 was connected to your modem and your Netgear router was behind it with your PCs daisy chained behind the router.

Let's say that your SPA-2100 assigned LAN addresses in the range 192.168.0.x and took 192.168.0.1 as its own LAN address. So far, so good. Let's say next that your Netgear woke up. It starts up its DHCP server and assigns addresses also in the range of 192.168.0.x, assigning 192.168.0.101 and 192.168.0.102 to your two PCs, and also takes the address 192.168.0.1 for its own LAN address. Simultaneously, it asks the SPA-2100 for a WAN address and is assigned 192.168.0.50 by the SPA.

You sit down behind computer 192.168.0.101. You want to surf to Google, so your PC looks up the address and sends a request to 66.102.7.104. Your PC knows to forward the request via its gateway, 192.168.0.1, and sends it on to the Netgear. The Netgear sees that the request is destined for 66.102.7.104, and it knows the route to reach there is via its own WAN port via its WAN gateway at 192.168.0.1, so it sends it on to the SPA-2100. The SPA-2100 sees that the request is for 66.102.7.104, and it knows that the way to reach there is via your ISP, so it forwards the request out its WAN port and you have your session.

Next, however, you want to register a new Speed Dial number on Line 1 of your SPA-2100. You open your browser and ask to be connected to 192.168.0.1, which is the LAN address of the SPA. Unfortunately, when this request hits your Netgear router it recognizes that address as being its own, so it presents you with the login screen for the Netgear Management server instead of forwarding your request on to the SPA.

In a nutshell, this is why you can't have adjacent or successive segments with overlapping address spaces.

[ko01u]

>However it's been a couple of days and I haven't experienced any >dropped connections yet...

I have also a Motorola Cablemodem SB4200. Before 2.0.5(d) the SPA sent some wrong Ethernet-Frames. Because of this the Cablemodem detected a "new" MAC-Adresse from this bad Frames and after some time his MAC-Adresstable was full and that was the reason why the Cablemodem stopped working. Sometimes this doesnt happen and it will running days, but the next time you powercycle the cablemodem the same procedure starts again and you cannot say if you have the same luck again. So if you want it stable you have to upgrade to 2.0.5(d)

ko01u

[kamalpa]

mberlant - I had originally changed the router address to 192.168.13.1 - and was told by Broadvoice support was that still too close in that the 1st two segments were shared - is that true?

When you say the VPN does not tolerate 2 NAT translations, does that mean that it shouldn't have even allowed me to connect or simply that the results would be unpredictable?


ko01u - the funny thing was that I never lost the connection through the modem it was always just my PCs via the router that were unable to connect to the internet. Est-ce que vous etes francais(e)? Je demande simplement parce-que vous avez ecrit "adresse".


Thank you both for you help.