26 Dec
2014
26 Dec
'14
1:52 p.m.
Ok Michael, I just misread that post. Sorry.
You are right. And the rules do exactly that.
Traffic originating on the ampr interface with destination outside the ampr
network will go to table 'default', and that one will have a default route
via the UCSD gateway.
Marius, YO2LOJ
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of
Michael E Fox - N6MEF
Sent: Friday, December 26, 2014 21:48
To: 'AMPRNet working group'
Subject: Re: [44net] How to make traffic coming in on the tunnel interface
get answered from that interface?
(Please trim inclusions from previous messages)
_______________________________________________
-----Original Message-----
Just to clarify this: The unterstanding on how a full mesh works is wrong.
Not from, to. The user's (from) IP address was given as 11.22.33.44. See
previous message.
Michael
N6MEF
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
Now, suppose the public user connects to
44.44.44.44. His packet comes
in
via the UCSD gateway and over the AMPRnet link to
that gateway to my
amprnet
interface, 44.44.44.44. The reply should go back
out the 44.44.44.44
interface, via the AMPRnet, through the UCSD gateway, and back to the
user.
No. It doesn't. If the user connects from 44.44.44.44 his packet comes