Showing posts with label Netgear. Show all posts
Showing posts with label Netgear. Show all posts

Friday, 3 December 2010

DG834 resolved - v5 is where it's at

After much wrangling, I didn't get the Netcomm to work properly, the VPN was still no good and I was unable to get VOIP running across it. Fortunately I ran into an old buddy and he suggested using the v5 of the Netgear router. Lo and behold, it uses a Conexant chipset, not Broadcomm and I put two in, one at either end. Both have been very stable, no dropouts and the VPN works perfectly.

Following this small victory I then deployed one at home and it's working fantastically well. I've been hammering it too so it's all going along nicely and my VPN is working properly too.

While the Netcomm is undoubtedly a powerful device, the lack of configuration in the VPN side of things and the fact it won't send VOIP data properly are big strikes against it. I've redeployed one of these routers elsewhere and the user loves it so that's a win and no financial loss on my part.

The love affair with Netgear is renewed!

Tuesday, 23 November 2010

Netcomm NB8WVPN and the Netgear DG834

After the woes I've experienced with the DG834 I cast about looking for a replacement device. It needed to be a decent ADSL 2+ router (with built in modem) and support site-to-site VPN tunnels - none of this VPN pass through garbage. After looking around a bit, I found the NB8WVPN from Netcomm which promises all sorts of things about how wonderful it is etc etc. So I purchased two and set them up at one of my problem sites - both ends. Now each of these sites has an Alcatel-Lucent phone system that use a VOIP link to put calls through to each other. Naturally this VOIP link has to go across a VPN.

With the VPN established between the two sites, I had some connectivity between them - that is, I could ping and browse the network etc but the phone systems couldn't talk to one another. The initial part of the VOIP signalling goes through, but the call itself doesn't. Remarkably frustrating I must say. After alterations to the phone systems (and I must add: the VOIP worked perfectly over the Netgear VPN) we got partial signalling through.

Eventually I put the stable Netgear back in and here's where it gets tricky. When I created the VPN between the NB8WVPN and the DG834 I had to make it quite basic. No Perfect Security or anything like that. Also, in the Advanced settings on the NB8, I had to change the settings to SHA-1 from it's original setting. Once this was all done I got a VPN back up! Yay! Before I performed jumps of joy, I tested it with my trusty sidekick. He could call me (from the Netgear side) but couldn't hear me and I couldn't call him from the NB8 side. The support on this is very sketchy out there. I was surprised by how little there is about these routers out there. I eventually upgraded the firmware on the NB8 and it's nearly time to test.

The good thing out of all this is, that the VPN was able to carry data like pings (ICMP) NetBIOS queries and various TCP streams like HTTP. It just doesn't seem to like the VOIP signalling. Additionally I found it very useful to disable the QoS on the Netcomm's. I tested the VOIP signalling by using two Linux notebooks with extra NIC's bridged and running Wireshark to see what was happening. I now need to go back to site and test it all.

Netgear DG834 woes

For quite some time I've used the Netgear DG834 as my router of choice, particularly as a low end router providing easy site-to-site VPN's. These little white routers will support up to 5 VPN tunnels and have proven themselves to be quite reliable under most circumstances.

Unfortunately, I think I've discovered the circumstances that these routers do not work well under. I have two sites under my management that have had no end of trouble with these routers. Here is the situation and the symptoms:
  • both sites are ADSL2
  • both sites have a single VPN connection to them as the responder
  • both sites have appropriate ADSL2+ capable filters and short cables etc
  • both sites drop their ADSL connection (not line sync) after 13 to 16 days and then fail to reconnect.
  • A restart of the device (soft or hard) and the connection will stay up for anywhere between 5 and 16 minutes - whatever the time length is, it will always die after that time e.g. if it's 10 minutes, then it will lose connection every 10 minutes.
  • both lines have been tested (and charged to the end user) by the carrier and the wholesaler and no line problems have been found. There are some very mild anomalies but nothing that should cause these sorts of issues
  • both routers have the latest firmware, have been reset to default and still show the same errors.
Netgear have shown no willingness to engage with me on this issue. After calling them four times and speaking with four different 1st level techs I can't get them to acknowledge that the routers might have a problem. Mind you, it's only 2 routers out of 40+ that I have in place out in the real world. Replacing the routers with devices running different hardware results in a stable connection again so it's not the lines! Once everything has been eliminated as points of failure, the final location of the problem is the Netgear Router. So I've had to replace them and that's the subject of my next entry.

Omarchy - the new darling of the Linux world

 Omarchy is the buzzword at the moment, with it turning up on Network Chuck's YouTube channel. I came across it via DHH's blog post ...