| To: | Hasso Tepper <hasso@xxxxxxxxx> |
|---|---|
| Subject: | Re: primary and secondary ip addresses |
| From: | Henrik Nordstrom <hno@xxxxxxxxxxxxxxx> |
| Date: | Fri, 17 Dec 2004 20:25:10 +0100 (CET) |
| Cc: | "Martin A. Brown" <mabrown@xxxxxxxxxxxxxx>, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <200412172053.28016.hasso@xxxxxxxxx> |
| References: | <41912F7A.6000408@xxxxxxxxxx> <200412172003.22319.hasso@xxxxxxxxx> <Pine.LNX.4.61.0412171206200.10943@xxxxxxxxxxxxxxxxxxxxxxxxxx> <200412172053.28016.hasso@xxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 17 Dec 2004, Hasso Tepper wrote: All these tricks don't help if you are using dynamic routing. Are you seriously saying you are doing dynamic routing for your locally attached lans? source address assignment for routed traffic via gateways is automatically derived by the source address assignment for traffic addressed to the gateway itself. So even with routing protocols etc you can control the source address assignment simply by setting up routing to use the correct source address to speak to your gateways, the added routes will then inherit the intended source address. But I am not sure about how you can control this on multicast or broadcast traffic in a reasonable manner, mostly because I rarely have to care about this on such traffic. Regards Henrik |
| Previous by Date: | Re: [Coverity] Untrusted user data in kernel, David S. Miller |
|---|---|
| Next by Date: | Re: primary and secondary ip addresses, David S. Miller |
| Previous by Thread: | Re: primary and secondary ip addresses, Hasso Tepper |
| Next by Thread: | Re: primary and secondary ip addresses, Hasso Tepper |
| Indexes: | [Date] [Thread] [Top] [All Lists] |