Your first email stated that the problem was that your response was going back directly, instead of through the gateway, causing a problem for public access to your system via the Internet.
I'll make my answer to that question more clear: If you want to direct outbound packets from your 44.x addresses back through the UCSD gateway, and if your gateway is in linux, then you need to add an ip rule (or rules), as in: "ip rule add from ... to ... pref ... table ...". If you are performing the gateway function directly in JNOS, then sorry, I don't know what is necessary.
But your second email says you don't want the responses to go through the gateway. So evidently, I answered the wrong question.
Perhaps you could restate the question more specifically, including where you perform the gateway function (JNOS or linux) and what, specifically, you're trying to accomplish.
Michael
-----Original Message----- From: 44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Mark Phillips Sent: Thursday, September 05, 2013 11:42 AM To: AMPRNet working group Subject: Re: [44net] Routing and encap minor issue in JNOS
(Please trim inclusions from previous messages) _______________________________________________ And by IP rule you mean what? This is not a firewall issue. Traffic flows back and forth perfectly.
What JNOS should be doing is to respond to packets in the same manner in which they arrived. If they came in via encap they should go out via encap, if they come in directly they should go out directly.
Simply adding a default route via the encap interface is not right as it will send all non 44 traffic to ucsd even if I don't want it to go there. I'm sure ucsd could do without the extra traffic too.
Mark
On Thu, Sep 5, 2013 at 1:15 PM, Michael E. Fox - N6MEF n6mef@mefox.orgwrote:
(Please trim inclusions from previous messages) _______________________________________________ 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@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 -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://hamradio.ucsd.edu/mailman/private/44net/attachments/20130905/ad 9dff9 b/attachment.html> _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html