News: This forum is now permanently frozen.
linktree m0n0wall Forum  >  m0n0wall Support (English)  >  Installation
linktree Topic: Problem getting Vonage to work
Pages: [1]
Topic: Problem getting Vonage to work  (Read 3020 times)
« on: July 17, 2008, 02:32:28 »
mgrove *
Posts: 7
I am struggling to get my Vonage device to work through m0n0wall.  I am pretty sure I have punched holes for all the necessary ports but the box refuses to connect.  I am not even seeing blocked requests in the log.

I am still relatively new to the m0n0wall interface, so I was hoping someone would double check my settings or maybe give me some ideas on how to troubleshoot this issue.

I am using an Alix 2c0 board and version 1.3b13.

My Vonage device is at 192.168.0.255

The outgoing ports I need are:
Ports 53, 21, 69, 2400, 80, 123, 5061 UDP

The outgoing and incoming ports I need are:
Ports 10000-20000 UDP

I have attached a screen shot of my rules.  Anyone have any ideas what is going wrong?

* rules.gif (29.06 KB, 583x780 - viewed 335 times.)
« Last Edit: July 17, 2008, 02:34:57 by mgrove »
« Reply #1 on: July 17, 2008, 02:53:51 »
ChainSaw
Guest
Vonage works fine with no NAT rules and the default LAN rule.  Also, you cant use the last octet of .255 for any host address.  It's IP-101.  Very basic stuff  Smiley

CS...
« Reply #2 on: July 17, 2008, 03:46:06 »
mgrove *
Posts: 7
If that is the case then what is this DHCP screen showing?  The device showing the .255 IP is the Vonage device.

UPDATE: Thanks for the hint.  I was able to fix the issue.  It turns out that the DHCP interface will allow you to set the last assignable IP address as 255.  I think the Vonage device is set up to grab the highest IP address available.  So it was choking on the .255 IP address.  I switched the max to .254 and everything started working.  Seems like the interface should show .254 instead of .255 in the available range field.

Thanks for the help.  I never would have sorted that out on my own.

* dhcp.gif (9.82 KB, 587x284 - viewed 362 times.)
« Last Edit: July 17, 2008, 04:06:59 by mgrove »
« Reply #3 on: July 20, 2008, 19:57:54 »
Manuel Kasper
Administrator 		*****
Posts: 364
Code to check for this type of misconfiguration (and also for including m0n0wall's own IP address in the client range) is now in the repository and will make its way into 1.3b14. The same checks also apply to the console "Set up LAN IP address" option.

- Manuel
« Reply #4 on: July 21, 2008, 00:51:03 »
ChainSaw
Guest
Thanks!!!

CS...
« Reply #5 on: July 21, 2008, 10:16:41 »
markb ****
Posts: 331
Is it just me, or have you set up the rules for your outgoing connections on the WAN port rather than your LAN interface?
« Reply #6 on: July 21, 2008, 16:19:35 »
mgrove *
Posts: 7
Yes, your correct.  The settings were in the wrong area.  After resolving the issue with the IP address I removed most of the rules and it worked fine.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines