How to set peer0 to eth0 and not loopback?

[Juli Mallett]

You absolutely should not need to go over loopback to connect to a remote
peer.  Can I ask how you're encountering that behaviour?  Can you include
your full configuration (redacting IPs if you feel it's necessary) and how
you're verifying that it's not going out over the external interface?  I
ask on the last point because it's certainly the case that in some cases
you may see traffic when doing tcpdump on a loopback interface if that
traffic originates locally.

Really, every useful configuration not involving an exterior tunnelling
system should include at least one non-local peer, so I'm a little confused
as to what your configuration must be that you're only seeing local
traffic, or have gotten the impression that WANProxy cannot make
connections across a network interface.  If you've only looked at a
configuration which uses SSH as a tunnel mechanism, such as the first
configuration on http://wanproxy.org/examples.shtml, I'd encourage you to
look at the second configuration, which connects directly over a WAN, or at
the SSH optimization examples on http://wanproxy.org/ssh.shtml, for
inspiration.

It should be enough to simply modify the peer0 definition to use a
non-local IP to which you have a route.  If something else is going wrong,
I'd guess it's some kind of portability bug that I'd like to fix urgently,
so would appreciate any more information you can give.

Thanks very much for the report!
Juli.


On Sat, Apr 12, 2014 at 10:31 AM, John Nix <jnix at vobal.com> wrote:

> Hi,
>
>
>
> The wanproxy software looks like a good fit for our equipment connected
> over satellite links.
>
>
>
> Setting it up was straightforward, but I do have a basic question that
> doesn’t seem to be addressed in the documentation or through several
> searches on Google.
>
>
>
> For various reasons, I need peer0 to be on eth0 and not the loopback
> interface.  For example, when use the command ‘set peer0.host “x.y.z.q” ‘,
> and look  at tcpdump wanproxy is sending to x.y.z.q on the loopback
> interface, which won’t readily work for our particular application.
>
>
>
> I expect there are workarounds (like trying to use iptables to redirect
> from lo to eth0, or running redir to listen on loopback, etc.), but the
> simplest would be to have the wanproxy peer on eth0.  In case it matters,
> I’m using Ubuntu 12.04.
>
>
>
> Thanks, John
>
>
>
> -------------------
> John Nix
> Founder and CEO
> Vobal Technologies
> +1-847-350-9998 (o)
> +1-847-452-3754 (m)
> www.vobal.com
>
>
>
> _______________________________________________
> wanproxy mailing list
> wanproxy at lists.wanproxy.org
> http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wanproxy.org/pipermail/wanproxy-wanproxy.org/attachments/20140412/ba029a42/attachment-0002.htm>