[arm-allstar] Debugging port forwarding

[Dave Miller]

Andrew,
So this would be done externally?

I can try to get someone to do that.
Thanks
Dave
VE7PKE

On Fri, Feb 27, 2015 at 8:56 AM, Andrew Sylthe <asylthe at kc9ona.com> wrote:

> Checking to see if a UDP port is responsive with a tool like nmap is
> extremely easy.
>
> The syntax is:
>
> $ sudo nmap -sU -p port target
>
> This tool will tell you if the state of a specified port is "open" or
> "closed" for the desired target.  You'd want to change "port" to 4569 (if
> using the default port number) and "target" to the hostname or ip of the
> remote target you're running the port scan against.
>
> I hope this helps.
>
> On Fri, Feb 27, 2015 at 10:47 AM, Doug Crompton <doug at crompton.com> wrote:
>
>> Dave,
>>
>>  It is very hard if not impossible to port check a udp port remotely.
>> Port checkers will show erroneous info on udp ports. tcp ports should show
>> correctly on a port checker. You are right in checking a TCP port like http
>> or ssh and see if they work. The BBB has httpd running for lsnodes but if
>> you simply send a web browser to your BBB's local IP address you will get -
>>
>> THIS IS A TEST !
>>
>> If you are not using port 80 then make sure you put the port in the url -
>>
>> Ex - http://192.168.1.100:8080
>>
>> on the web browser. If you have port 80 (or whatever you have changed it
>> to) forwarded to your BBB anyone on the Internet should also get that by
>> going to your public IP.
>>
>> You could also setup ssh which defaults to port 222. If you port forward
>> 222 (or whatever you have it set to) anyone on the Internet going to your
>> public IP at that port should get your login. No need to actually login. If
>> you get the login it is working.
>>
>> You might also check and make sure that both of you have each others node
>> entry in your rpt_extnodes file. It is located in /tmp  - you can grep for
>> the info.
>>
>> [root at wa3dsp-40961-cm /]# grep 27225 /tmp/rpt_extnodes
>> 27225=radio at 73.30.112.57:4569/27225,73.30.112.57
>>
>> There should be an entry and the lookup for the distant node will show
>> their public IP address.  You can use this IP info to connect ssh or
>> http.
>>
>> Another thing you should do is on the end that is NOT receiving the
>> connect be in the Asterisk client - asterisk -rvvv   - when the other node
>> is connecting. If you see nothing then you know it is not getting through.
>> If you see a connect attempt but with errors you can  troubleshoot from
>> there an in that case at least you know it is getting through.
>>
>> I hope that helps. Some routers can be a problem.
>>
>>
>>
>> *73 DougWA3DSPhttp://www.crompton.com/hamradio
>> <http://www.crompton.com/hamradio>*
>>
>>
>> ------------------------------
>> Date: Fri, 27 Feb 2015 08:19:47 -0800
>> From: ve7pke at gmail.com
>> To: arm-allstar at hamvoip.org
>> Subject: [arm-allstar] Debugging port forwarding
>>
>>
>> I am going in a real nice circle that is every decreasing to zero radius.
>> To get to the solution I could use some details.
>> I am using the latest BBB code.
>> Tom VE7DID is unable to connect to my node but I am able to connect to
>> his. Things work fine once I connect.
>> So I figure the issue is either my router or my DSL modem/???
>>
>> I am trying to get a simple test case working to hit the correct party
>> squarely on the head.
>>
>> I have been try to use the various online port checkers to see if I am
>> open. They all show closed. Even tried a different DSL router that
>> allegedly was in bridge mode. Still same results.
>>
>> My thought is to ignore port 4569 for now and try to open up a path to
>> the BBB on HTTP to test first. I see if I use my browser locally got to my
>> IP I get a test message that says This is a Test!. That is cool. I assume
>> that is on port 80?? Where do I change that port to something else like
>> 8080 as my glorious ISP Telus block all ports below 1000. ;-(
>>
>> I don't know what these port checker do but I expect if the is a web
>> server responding they will give correct information.
>>
>> I want to keep it simple for now and just prove that the router is moving
>> data to the right IP locally.
>>
>> Thanks for reading to the end of this rather long winded message.
>> I am using a Netgear Prosafe FVS318G
>>
>> Many thanks
>> Dave
>> VE7PKE
>>
>>
>> _______________________________________________ arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the
>> BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB web page -
>> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>>
>
>
>
> --
> Andrew Sylthe
> KC9ONA
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB web page -
> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150227/863a649f/attachment-0001.html>