[arm-allstar] Debugging port forwarding
Dave Miller
ve7pke at gmail.com
Fri Feb 27 12:37:54 EST 2015
James,
I was using NetGear FVS318G for both my old modem Speedtouch ST516 V6 with
the Telus firmware.
And with a brand new TP Link TD-8816. I was not convinced I had it in
bridge mode as it seemed to be double NAT'ed. My internal network is
192.168.0.x and I could access teh TP-Link at 1.x which seemed strange in
bridge mode. I am not a IT pro. But know the basics probably enough to hang
myself.
I want to keep the Neatgear router internally. I am happy to switch to the
TP-Link if I can get in in bridge mode. It may have been but since the port
checkers don't seem to work on UDP I may have been confusing myself. That
is why getting the isnodes to respond on a port above 100 is a good test
case.
Thanks
Dave
VE7PKE
On Fri, Feb 27, 2015 at 8:38 AM, James K4JK <k4jk.james at gmail.com> wrote:
> Dave,
>
> As far as I know most port check tools really only work with TCP. Allstar
> uses UDP so detecting them is a lot trickier, and I wouldn't necessarily
> trust what the online port checkers tell you.
>
> That said, a likely culprit in your situation is the device that between
> your Netgear router and the POTS line going back to Telus. It could be
> functioning as a router, which would defeat the port forwarding you have
> setup on your Netgear device. When you say you tried a different DSL
> router, did you replace this device and leave your netgear router hooked
> up? Or did you replace both units with this device?
>
> Can you give us the model name/number of the DSL interface device? That
> way we may be able to see if it is capable of functioning as a router.
>
> James
> K4JK
>
> On Fri, Feb 27, 2015 at 11:19 AM, Dave Miller <ve7pke at gmail.com> wrote:
>
>> 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/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150227/60293d62/attachment-0001.html>
More information about the arm-allstar
mailing list