Re: [44net] Routing and encap minor issue in JNOS

If you want to direct outbound packets from your 44.x addresses back through the UCSD gateway, you need to create an ip rule to do so. Michael N6MEF -----Original Message----- From: 44net-bounces+n6mef=mefox.org(a)hamradio.ucsd.edu [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Mark Phillips Sent: Thursday, September 05, 2013 10:05 AM To: AMPRNet working group Subject: [44net] Routing and encap minor issue in JNOS (Please trim inclusions from previous messages) _______________________________________________ Hi all, Firstly, if this has been done to death before please forgive me. I could not find anything in the archive. Secondly, I have noticed an "issue" with the routing and encap within JNOS. It would seem that if a 44 station tries to contact me all works fine. For example I can communicate with N2NOV and GB7CIP exactly how you would expect. However, if a "public" address contacts me, I get their connect requests in encap format via uscd but then I send them my response directly rather than back the same way it came. This means that there can be no public access to my system via the Internet. What have I missed? JNOS will not allow me to set the default route via encap/uscd and I don't really want to send all my traffic (eg DNS lookups) via there anyway. How can I respond to connections in the same way that I received them? Thinking about it, it makes sense that JNOS replies directly. Once it unpacks the packet and discovers an encap'd one inside it will work on that one exclusively. Thanks Mark