> As other contributors have suggested, if you really need source routing,
> use pf or similar for that. I believe ipf also supports route-to on the
> outbound.
Another solutions would be that if there is only a known subset of
networks sending you data over the leased line (such as a few /24's),
Brian Hawk wrote:
Then what would be the reason to bind a connection to a specific
source address? We do
ping -S A.B.C.D x.y.z.t
to make ping send packets to x.y.z.t over A.B.C.D's interface (and
source address) or
telnet -s A.B.C.D x.y.z.t
I believe binding an IP's source address to an inter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Hawk <[EMAIL PROTECTED]> wrote:
>
> I believe binding an IP's source address to an interface address
> (instead of INADDR_ANY) is to make packets go out from *that*
> interface, not the default gw.
I'm afraid that's not how it works. In the abs
Brian Hawk wrote:
Dima Dorfman wrote:
I don't think it ever worked the way you described. The source IP
address doesn't usually affect how replies will be routed on the way
out.
Then what would be the reason to bind a connection to a specific source
address? We do
ping -S A.B.C.D x.y.z.t
to
Dima Dorfman wrote:
I don't think it ever worked the way you described. The source IP
address doesn't usually affect how replies will be routed on the way
out.
Then what would be the reason to bind a connection to a specific source
address? We do
ping -S A.B.C.D x.y.z.t
to make ping send pac
Here's the routing table,
#~>netstat -rn
Internet:
DestinationGatewayFlagsRefs Use Netif Expire
default85.97.0.1 UGS 0 25211312 tun0
10 10.1.1.222 UGS 0 3407666xl0
10.1.1/24 link#2
Brian Hawk <[EMAIL PROTECTED]> wrote:
> since it shouldn't really happen and it used not to happen.
> Everything was working fine until I don't know when and why, now I
> cannot send any packets out thru my xl1 interface by binding its
> source address to the packets.
I don't think it ever worked
> My problem is, packets generated with A.B.C.D source address does not go
> out thru xl1 but tun0 (which is the default gw). The problem also
> happens when an outsite packet destined for A.B.C.D arrives. The packet
> correctly arrives from xl1 interface but the response goes out from
> tun0. This
Hi ppl,
Sorry for the bizarre subject but I really didn't know how to put this on.
I have 3 interfaces: xl0, xl1 and rl0. rl0 is the where ppp daemon (for
ADSL) runs on, so I also have tun0 which grabs the default gateway. My
problem is with xl1 which is connected to a leased-line and has a st
