[ previous ] [ next ] [ threads ]
 
 From:  "Christopher M. Iarocci" <iarocci at eastendsc dot com>
 To:  "Jason J. Ellingson" <jason at ellingson dot com>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Re: [m0n0wall-announce] Beta 1.2b5
 Date:  Thu, 24 Feb 2005 21:06:38 -0500
Jason J. Ellingson wrote:

>I don't have any problems.
>
>I upgraded to 1.2b5 and my Vonage still works.
>
>I use Comcast high-speed internet (3Mbit)
>The ATA is the Motorola one provided by Vonage.
>
>My configuration is as follows:
>
>Comcast
>|
>Cablemodem
>|
>Monowall (Generic PC-HD version)
>|
>Motorola ATA (bridged mode!) - Telephone wall outlet - several phones
>|
>Network switch
>|
>Several PCs
>
>
>Monowall configuration
>======================
>Alias:
>Name    Address      Description
>Vonage  192.168.1.2  Vonage Phone
>
>NAT:
>If   Proto  Ext. port range  NAT IP  Int. port range  Description 
>WAN  UDP    5061             Vonage  5061             Vonage
>WAN  UDP    10000 - 10011    Vonage  10000 - 10011    Vonage
>
>Rules:
>Proto  Source  Port  Destination  Port           Description 
>UDP    *       *     Vonage       5061           NAT Vonage
>UDP    *       *     Vonage       10000 - 10011  NAT Vonage
>
>Motorola configuration
>======================
>WAN IP Address Assignment  Static
>    IP Address             192.168.1.2
>    Subnet Mask            255.255.255.0
>    Default Gateway        192.168.1.1
>
>DNS Servers                192.168.1.1
>                           0.0.0.0
>
>DHCP Server/NAT            Disabled
>
>By setting the ATA between the firewall and the network switch, it never has
>a problem with me hogging the bandwidth.  I don't use traffic shaping and I
>can have Vonage at full 90kbps (best quality) while downloading dozens of
>files via bittorrent, eDonkey, etc... fully saturating my bandwidth... all
>while still on the phone with perfect clairity.
>
>The trick is to not use the Motorola's NAT.  Set it up with a static IP and
>then use proper NAT rules on monowall.
>
>To still browse the Motorola box when configured this way, you need to have
>your computer's TCP/IP set to normal 192.168.1.xxx IP, netmask and gateway
>*AND* add a 192.168.102.xxx IP and netmask (no gateway though)... then that
>computer can use a browser to 192.168.102.1 to configure the motorola box if
>needed.
>
>Please let me know if this helps anyone.
>------------------------------------------------------------
>Jason J Ellingson
>Sr. Web Software Developer
>
>615.301.1682 : nashville
>612.605.1132 : minneapolis
>
>www.ellingson.com
>jason at ellingson dot com
>
>-----Original Message-----
>From: Christopher M. Iarocci [mailto:iarocci at eastendsc dot com] 
>Sent: Tuesday, February 22, 2005 7:12 PM
>To: Manuel Kasper
>Cc: m0n0wall dash announce at lists dot m0n0 dot ch; m0n0wall at lists dot m0n0 dot ch
>Subject: [m0n0wall] Re: [m0n0wall-announce] Beta 1.2b5
>
>Just a note, upon installing this release, I found that my IP Telephone 
>(Vonage) would no longer work no matter what I did.  I put an all pass 
>firewall rule, disabled the traffic shaper, nothing.  Downgraded back to 
>1.2B3, phone working fine again.  Everything else seemed to work fine 
>except the AH IPsec tunnel I had, which would establish, but not pass 
>any packets.  The ESP based IPsec tunnels all worked fine.  Again, 
>downgrading to 1.2B3 got that single AH based tunnel working fine again 
>without any configuration changes.  Manuel, if you want/need anything 
>from me to solve these issues say the word.
>
>--Chris
>
>  
>
Thanks for the tip, but I have the Cisco unit, and it is totally 
non-configurable.  It pulls an automatic IP using DHCP, and that's it.

--Chris



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 2/22/2005