i was able to telnet in from here and got a login prompt from wa4zlw.ampr.org On 12/9/2016 4:06 PM, Mark Phillips wrote: > (Please trim inclusions from previous messages) > _______________________________________________ > Yep, this is what we discussed last night, Charlie. > > Your JNOS is trying to respond directly to the incoming connections rather > than traversing an encap tunnel. This will not work as the upstream > hardware does not know about you and your 44net allocation. You receive > packets over the encap bridge but you respond back directly. > > As for how to fix it? Dunno. We need to somehow encap your outgoing default > route for your 44 IP address so that packet response is along the same path > that it came in. > > On Fri, Dec 9, 2016 at 3:09 PM, Rob Janssen <pe1chl(a)amsat.org> wrote: > >> (Please trim inclusions from previous messages) >> _______________________________________________ >> >> Subject: >>> [44net] Telnet To JNOS From Public IP Users Not Working >>> From: >>> "Charles Hargrove" <n2nov(a)n2nov.net> >>> Date: >>> 12/09/2016 07:13 PM >>> >>> To: >>> 44net(a)hamradio.ucsd.edu >>> >>> >>> I am having trouble getting users to telnet from their homes to my JNOS >>> box >>> located at 44.68.41.1 on port 2300. Their seems to be an asynchronous >>> connections as they try to transverse the UCSD portal. I see my responses >>> going back to them, but they are just hanging on their side. I have in my >>> autoexec.nos file "route add default tun1 44.0.0.1" as their is a tunnel >>> interface between the JNOS and the linux box that it is running on. Does >>> anyone have any ideas? Thanks. >>> >> I get a connect but no text. Normally this means there is an MTU issue >> somewhere, >> but in this case (trying from net-44) the welcome text appears to be too >> smal for that >> kind of problem. it could be a firewall issue as well. >> >> Why do you set the default route to 44.0.0.1 instead of 169.228.66.251 ? >> Is that normal for JNOS? >> >> Rob >>