[App_rpt-users] Connection troubles and NAT FYI

Jim Duuuude telesistant at hotmail.com
Sun Oct 28 15:32:10 EDT 2012


i dunno.. I asked "around" (or maybe it was "a square" ??) and Tomato seemed like the
better answer given the complete lack of preparation I could do for the install I did it on.

It seems like it was good advice.

> Subject: Re: [App_rpt-users] Connection troubles and NAT FYI
> From: buddy at brannan.name
> Date: Sun, 28 Oct 2012 14:10:59 -0400
> CC: ajp26 at buffalo.edu; app_rpt-users at ohnosec.org
> To: telesistant at hotmail.com
> 
> Not to start a holy war, but does anyone have any sort of preferences as to Tomato vs. dd-wrt? It might be a moot point, as the Asus RT-N12 I'm currently using may only be supported by dd-wrt, but anyway, thought I'd ask if there was any advantage to switching. 
> --
> Buddy Brannan, KB5ELV - Erie, PA
> Phone: (814) 860-3194 or 888-75-BUDDY
> 
> 
> 
> On Oct 28, 2012, at 12:22 PM, Jim Duuuude <telesistant at hotmail.com> wrote:
> 
> > There is utterly no question that this is a COMMON problem.
> > 
> > I am not going to do the <soapbox> No one ever makes anything that works anymore </soapbox>
> > type of thing here. :-) (although I am rather tempted)
> > 
> > The best solution I have found is put some DSL modem in bridging mode and then put a NAT router
> > in back of it that works. 
> > 
> > For example, in one of these cases, I replaced an Actiontec DSL router/modem with a Zyxel (which was
> > a second choice, I also had a *REAL* Cisco 174X router with an ADSL WIC that wouldnt talk to the provider's
> > DSL protocol) in pure bridging mode, and a Linksys WRT54-GL running Tomato.
> > 
> > Needless to say, I have not had any problems with Asterisk not being happy since.
> > 
> > Jim WB6NIL
> > 
> > > From: ajp26 at buffalo.edu
> > > To: app_rpt-users at ohnosec.org
> > > Date: Sun, 28 Oct 2012 02:45:21 -0400
> > > Subject: [App_rpt-users] Connection troubles and NAT FYI
> > > 
> > > While Asterisk works behind NAT just swell, it seems several of the problems I have run into can be traced back to a terrible NAT implementation on our router. We have some rangebooster DLink that NATs even DMZ traffic, and generally breaks inbound anything. portal updates, phone portal, etc, works rarely if at all. 
> > > 
> > > Something to keep in mind is to try and remove the router if you have one, and see if it is problematic. I would not leave the system like this, it will be probed via SIP and SSH, but you can quickly eliminate that element from your frustration.
> > > _______________________________________________
> > > App_rpt-users mailing list
> > > App_rpt-users at ohnosec.org
> > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> > _______________________________________________
> > App_rpt-users mailing list
> > App_rpt-users at ohnosec.org
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20121028/e4d69c33/attachment.html>


More information about the App_rpt-users mailing list