| To: | davem@xxxxxxxxxx (David S. Miller) |
|---|---|
| Subject: | Re: ipv6 global forward overrides dev-specific forwarding |
| From: | kuznet@xxxxxxxxxxxxx |
| Date: | Tue, 1 May 2001 21:17:44 +0400 (MSK DST) |
| Cc: | pb@xxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <15086.32117.801470.70689@xxxxxxxxxxxxxxx> from "David S. Miller" at May 1, 1 02:10:13 am |
| Sender: | owner-netdev@xxxxxxxxxxx |
Hello! > It seems senseless for it to behave this way. Per-device enabling/disabling forwarding in IPv6 simply does not exist. This switch is global only: either the whole node is router or it is not a router. Per-device "forwarding" switch controls only autoconfiguration/ndisc aspects. In IPv4 it was possible because it is able to make routing decisions based on input interface. IPv6 is not. It is easy to add direct check of the flag to ip6_forward, but I see no reasons to do this as soon as the feature is not obtained for no fee (like ip). If someone wants to control forwarding per-device, this can be made with a netfilter rule. The same is with IP. And f.e. if we were able to kill policy routing, per-device forwarding switch would stop to work as well. Alexey |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: ipv6 global forward overrides dev-specific forwarding, kuznet |
|---|---|
| Next by Date: | Re: isa_read/write not available on ppc - solution suggestions ??, Arnaldo Carvalho de Melo |
| Previous by Thread: | isa_read/write not available on ppc - solution suggestions ??, mike_phillips |
| Next by Thread: | Re: ipv6 global forward overrides dev-specific forwarding, Peter Bieringer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |