Re: [44net] How to make traffic coming in on the tunnel interface get answered from that interface?

Hi Marc, You are right. The good part is that all Linux networking follows this rule, and this is enforced by the kernel. Because a socket is set up with well defined endpoints before any network traffic can take place. So, as long as a software component uses plain kernel based networking, and doesn't do any "smart" networking stunts, source routing can be applied to ensure proper return paths based on source and destination. @Arno: Congratulations. Nice to hear that. -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Marc, LX1DUC Sent: Saturday, December 27, 2014 00:29 To: AMPRNet working group Cc: 44net-bounces+lx1duc=laru.lu(a)hamradio.ucsd.edu Subject: Re: [44net] How to make traffic coming in on the tunnel interface get answered from that interface? (Please trim inclusions from previous messages) _______________________________________________ Your apache server must be listening on 2 IP addresses. 1 could be a private IP address, request from commercial Internet get destination NATted to that private IP, the other could be a 44net IP address. The good thing about most networks daemons (like apache) is that they will respond from the IP address that has received the request, so you can use source based routing to distinguish between commercial Internet and 44net/AMPR outbound traffic.