just signed up

Posts: 2 · New Forum Member Joined: Jan 08, 2004 Posts: 2

hi all, i just signed up and got my motorola voice terminal. i also have a linksys wrt54g router and i have the voice terminal behind it as with my 2 other computers. i have opened 5060-5061,53-53,69-69,10000-20000, and 123 all udp for the voice terminals network address. is there something else i should do so that i dont have any unfortunate things happen to me such as dropped calls or things of that nature?

Posts: 83 · Vonage Forum Senior Joined: Nov 16, 2003 Posts: 83

Does it work? If so, go for it. If not, report back.

Posts: 21 · Vonage Forum Associate Joined: Jan 07, 2004 Posts: 21

The only potential problem I see is that your router (linksys wrt54g) does not allow for QoS (meaning giving one unit higher bandwidth priority than others). This means if you are using a bandwidth heavy application like p2p sharing, video streaming, or online gaming, or worst case spyware, you could choke your phone line's needed bandwidth causing static and/or drop-offs.

You might want to consider disabling nat on the vt1000 and setting it up as a passthrough between your broadband modem and the linksys wrt54g router.

Posts: 83 · Vonage Forum Senior Joined: Nov 16, 2003 Posts: 83

justpaul wrote:

**snip**

You might want to consider disabling nat on the vt1000 and setting it up as a passthrough between your broadband modem and the linksys wrt54g router.

This certainly works too. If you are going to do this don't forget to do a port scan and fix the security holes (i.e. ports left open by default) in the VT1005.

Posted: Fri Jan 09, 2004 2:23 pm Post subject:

Hmm... here's where I show my 'noob' status regarding the vt1000. After setting up the vt1000 as a passthrough to my linksys router, a port scan showed all ports as not listening (stealthed). Do you have a list of specific ports that are not transpanently passed through the vt1000 besides those used for voip?

Posts: 83 · Vonage Forum Senior Joined: Nov 16, 2003 Posts: 83

Until I moved mine behind the firewall, it can from Vonage with ports 23, 67, 137 and 139 open. It is possible that Vonage downloaded a firmware update to close these ports. Don't know. To be on the safe side run...

Shields Up: https://grc.com/x/ne.dll?bh0bkyd2
PCFlank: http://www.pcflank.com/scanner1.htm
Sygate: http://scan.sygate.com/pretcpscan.html
DSLReports: http://www.dslreports.com/scan

If you show no problems, you are good to go. BTW, Stealthed is OK but those ports that show open should be forwarded to a non-existent IP address. Good Luck.

Posts: 21 · Vonage Forum Associate Joined: Jan 07, 2004 Posts: 21

I just ran all 4 scans with no ports being reported as open.

In your case, ports 23, 137, and 139 are all ports that are open on 2000/xp boxes. Are you sure the firewall was the next device in line when you had the mta in front? There is no reason why the vt1000 would listen on 137 or 139.

As I understand it, when the vt1000 has nat disabled, imagine the vt1000 open on all ports, and when you run security tests, you are actually running the tests against the next device on your chain which should be a firewall device (not firewall software on a pc).

Posts: 83 · Vonage Forum Senior Joined: Nov 16, 2003 Posts: 83

justpaul wrote:

I just ran all 4 scans with no ports being reported as open.

In your case, ports 23, 137, and 139 are all ports that are open on 2000/xp boxes. Are you sure the firewall was the next device in line when you had the mta in front? There is no reason why the vt1000 would listen on 137 or 139.

As I understand it, when the vt1000 has nat disabled, imagine the vt1000 open on all ports, and when you run security tests, you are actually running the tests against the next device on your chain which should be a firewall device (not firewall software on a pc).

You're exactly right. No reason whatsoever. In my case, I did the port scan with nothing more than the VT1005 connected and a phone connected to it. The downstream router at the time was disconnected and NAT enabled on the VT1005. But this apparently was a common problem with the first VT1005's shipped from Vonage and a documented security bug.

Besides, it works better behind the router in my opinion anyway. Mine hung constantly when averaging about 120 port scans an hour at about the 8 hour mark. This was verified by a sniffer and the logs were sent to Vonage. They may have fixed this too, I wouldn't know since I have had the VT1005 behind my router for the last two months.