Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #14300 > unrolled thread

Networking question

Back to article view | Back to comp.os.linux.misc

Contents

  Networking question Vilmos Soti <vilmos@soti.ca> - 2015-04-01 11:43 -0700
    Re: Networking question Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2015-04-01 23:45 +0200
    Re: Networking question "Anonymous Remailer (austria)" <mixmaster@remailer.privacy.at> - 2015-04-02 01:48 +0200
      Re: Networking question Tim Watts <tw_usenet@dionic.net> - 2015-04-02 01:15 +0100
    Re: Networking question "Bill Cunningham" <mospam@nspam.invalid> - 2015-04-07 22:48 -0400

#14300 — Networking question

Hello,

I have the following situation:
I have a vpn accessible machine which is also an rsync
server/client. The rsync server listens on the vpn ip
address. Unfortunately, rsync can listen only on a single or
all ip addresses but not only on some.

If I connect from this machine to this machine with rsync, then
will the kernel be smart enough to recognize that although the
connection was made to the vpn address, it really should go via
127.0.0.1 since it is local? I have some faint memory that this
is indeed the case.

Can someone darken me up?

Thanks, Vilmos

[toc] | [next] | [standalone]

#14301

Vilmos Soti a écrit :
> 
> If I connect from this machine to this machine with rsync, then
> will the kernel be smart enough to recognize that although the
> connection was made to the vpn address, it really should go via
> 127.0.0.1 since it is local?

No. The kernel is smart enough to /not/ change the destination address
on its own. The communication will go through the loopback interface as
any local communication, but that is irrelevant to the listening socket.

[toc] | [prev] | [next] | [standalone]

#14305

Vilmos Soti <vil...@soti.ca> [VS]:
VS> I have the following situation: I have a vpn accessible machine
VS> which is also an rsync server/client. The rsync server listens
VS> on the vpn ip address. Unfortunately, rsync can listen only on a
VS> single or all ip addresses but not only on some.

Use redir(1), or (the much heavier) socat(1) to forward tcp
connections from port localhost:whatever to vpn.ip.address:873

[toc] | [prev] | [next] | [standalone]

#14309

On 02/04/15 00:48, Anonymous Remailer (austria) wrote:
>
> Vilmos Soti <vil...@soti.ca> [VS]:
> VS> I have the following situation: I have a vpn accessible machine
> VS> which is also an rsync server/client. The rsync server listens
> VS> on the vpn ip address. Unfortunately, rsync can listen only on a
> VS> single or all ip addresses but not only on some.
>
> Use redir(1), or (the much heavier) socat(1) to forward tcp
> connections from port localhost:whatever to vpn.ip.address:873
>

socat rocks!

[toc] | [prev] | [next] | [standalone]

#14392

"Vilmos Soti" <vilmos@soti.ca> wrote in message 
news:lqbnj7aduq.fsf@pia.msmri.medicine.ubc.ca...
> Hello,
>
> I have the following situation:
> I have a vpn accessible machine which is also an rsync
> server/client. The rsync server listens on the vpn ip
> address. Unfortunately, rsync can listen only on a single or
> all ip addresses but not only on some.
>
> If I connect from this machine to this machine with rsync, then
> will the kernel be smart enough to recognize that although the
> connection was made to the vpn address, it really should go via
> 127.0.0.1 since it is local? I have some faint memory that this
> is indeed the case.
>
> Can someone darken me up?
>
> Thanks, Vilmos

comp.os.linux.networking

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.misc

csiph-web