All of lore.kernel.org
 help / color / mirror / Atom feed
From: nisse@southpole.se (Niels Möller)
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, Jonas Bonn <jonas@southpole.se>
Subject: Re: What's the right way to use a *large* number of source addresses?
Date: Fri, 23 May 2014 16:12:22 +0200	[thread overview]
Message-ID: <6za9a8vb21.fsf@southpole.se> (raw)
In-Reply-To: <20140523101144.GH24523@breakpoint.cc> (Florian Westphal's message of "Fri, 23 May 2014 12:11:44 +0200")

Florian Westphal <fw@strlen.de> writes:

> Niels Möller <nisse@southpole.se> wrote:

>> 3. Just set the desired local address with the bind call. Currently,
>>    this gives an EADDRNOTAVAIL error, so the first step would be some
>>    option to allow arbitrary source addresses.
>
> See 'Making non-local sockets work' in Documentation/networking/tproxy.txt

I'd just like to say that I followed these docs, and I got a working
connection. Thanks again, I really couldn't locate this info on my own.

I do find the EINVAL error I got from connect, when only using sysctl
net.ipv4.ip_nonlocal_bind=1, and using bind with a nonlocal address, a
bit puzzling. I don't see any obviously better error to return, though.

Regards,
/Niels

  parent reply	other threads:[~2014-05-23 14:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  9:38 What's the right way to use a *large* number of source addresses? Niels Möller
2014-05-23 10:11 ` Florian Westphal
2014-05-23 10:49   ` Lukas Tribus
2014-05-23 12:26   ` Niels Möller
2014-05-23 14:12   ` Niels Möller [this message]
2014-05-23 12:53 ` sowmini varadhan
2014-05-23 14:14   ` Eric Dumazet
2014-05-24 12:06     ` Jamal Hadi Salim
2014-05-23 22:39 ` Cong Wang
2014-05-26  6:39   ` Niels Möller
2014-05-24 11:58 ` Jamal Hadi Salim
2014-05-24 14:44   ` Richard Weinberger
2014-05-24 15:13     ` Jamal Hadi Salim
2014-05-24 16:02       ` Richard Weinberger
2014-05-24 17:54         ` David Miller
2014-05-24 18:30         ` Jamal Hadi Salim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6za9a8vb21.fsf@southpole.se \
    --to=nisse@southpole.se \
    --cc=fw@strlen.de \
    --cc=jonas@southpole.se \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.