[mailto:lwip-users-bounces+fabian.koch=de.abb@nongnu.org] On Behalf Of Joel
Cunningham
Sent: Dienstag, 18. November 2014 15:51
To: Mailing list for lwIP users
Cc: Mailing list for lwIP users
Subject: Re: [lwip-users] Sending to a non-local network without default netif
set
we do have a setup
[mailto:lwip-users-bounces+fabian.koch=de.abb@nongnu.org] On Behalf Of
goldsi...@gmx.de
Sent: Freitag, 14. November 2014 21:29
To: Mailing list for lwIP users
Subject: Re: [lwip-users] Sending to a non-local network without default netif
set
HaaCee2 wrote:
I beg to differ
I've added
Isn't 1 Link-layer multiplexing instead of multihoming? The rfc1122
mentions this explicitly as NOT being multi-homing:
quote
Finally, we note another possibility that is NOT
multihoming: one logical interface may be bound to multiple
physical interfaces, in order
. November 2014 21:29
To: Mailing list for lwIP users
Subject: Re: [lwip-users] Sending to a non-local network without default netif
set
HaaCee2 wrote:
I beg to differ
I've added a task for this to the tracker:
https://savannah.nongnu.org/task/index.php?13397
Simon
In response to the remark:
Simon is right: routing doesn't have anything to do with the source address
and it shouldn't have to
I think Simon is not right (no pun intended).
I am not entirely familiar with the ideas behind LwIP. But sourcebased
routing is very much in line with rfc1122 (ip for
HaaCee2 wrote:
I am not entirely familiar with the ideas behind LwIP. But sourcebased
routing is very much in line with rfc1122 (ip for hosts). I quote:
Under the Strong ES model, the route computation for an outgoing datagram
is the mapping:
route(src IP addr, dest
On 14-11-14 20:27, Simon Goldschmidt [via lwIP] wrote:
HaaCee2 wrote:
I am not entirely familiar with the ideas behind LwIP. But sourcebased
routing is very much in line with rfc1122 (ip for hosts). I quote:
Under the Strong ES model, the route computation for an outgoing
datagram
HaaCee2 wrote:
I beg to differ
I've added a task for this to the tracker:
https://savannah.nongnu.org/task/index.php?13397
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Hey Mark, Simon,
well it does work when introducing the source address in the routing algorithm
and thats what I did for now.
But obviously, Simon is right: routing doesn't have anything to do with the
source address and it shouldn't have to.
The underlying problem in LwIP at the moment is
Hello,
I have two network interfaces: ethernet and ppp (they obviously don't
share a subnet). I need to open a number of TCP connections with the
requirement, that certain connections must be opened via a particular
interface. I was trying to achieve that by binding to an address-port
prior to
Mark Lvov wrote:
[..] certain connections must be opened via a particular
interface. I was trying to achieve that by binding to an address-port
prior to connecting, where the address corresponds to an address of a
particular interface.
[..]
Is there anything that could be done? I see, that
Thanks for the great suggestion, Simon!
Yes, what you suggest would work.. almost! Indeed, the destination
addresses are there in the configuration (along with the interfaces
associated with those destinations), so, theoretically, I could indeed
route based on destination address only. Problem
12 matches
Mail list logo
