[Ham-Mac] MacSense router configuration

[Dennis Hudson]

I've found port triggering to be problematic at best on many  
different routers. I've never worked with a MacSense router, but in  
general I prefer to do static port mapping to either static private  
IP addresses or statically reserved DHCP. If you choose to run  
echolink on another machine you'll need to change the IP, but it  
assures you've taken the damn router out of the equation.


--
Dennis Hudson, N2LBT
449.525/R 100hz
IRLP 4680 EL 4670
Albany, NY



On Mar 25, 2006, at 18:58 PM, Mark Klocksin wrote:

>
>
> I am having a frustrating time setting up Echomac and EchoLink.  I  
> cannot connect to remote stations.  Also, I can’t hear them. I’m  
> pretty sure it’s a router issue.
>
> I have a DSL connection and a MacSense router plugged into the DSL  
> modem.  I also have a 4-port switch plugged into the router.
>
> The router is a MacSense MIH-130A with 1.19f firmware.  I have set  
> it up as follows:
>
> Block wan port scanning   “Enable”
> Block WAN Ping response “Disable”
>
>
> Under Special Applications, I entered the following names  
> “EchoLink” and “Echomac.”  I selected both.  I set both the  
> outgoing trigger and incoming port range to: 5198~5200.  (By the  
> way, there is a third box for "QuickT and RealP"  Outgoing  is  
> 554~554 and incoming is 6970~7170.  I don't know how this was set.)
>
> (Later) After reading some posts, I also tried the following  
> settings for both EchoLink and EchoMac:
>
> Outgoing trigger: 5200 ~ 5200 and
> Incoming  port range: 5198 ~ 5199
>
> This doesn't seem to make any difference.
>
> One final question--is there any manual selection process I need to  
> do in order to "activate" the port trigger and range when booting  
> the EchoLink and EchoMac software?
>
> Thanks for any help you can provide!