| To: | kuznet@xxxxxxxxxxxxx, davem@xxxxxxxxxx (David S. Miller) |
|---|---|
| Subject: | Re: ipv6 global forward overrides dev-specific forwarding |
| From: | Peter Bieringer <pb@xxxxxxxxxxxx> |
| Date: | Tue, 01 May 2001 19:35:57 +0200 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <200105011717.VAA00425@xxxxxxxxxxxxx> |
| References: | <15086.32117.801470.70689@xxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
At 19:17 01.05.2001, kuznet@xxxxxxxxxxxxx wrote: 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. Ok, would be great if the IPv6 sysctls would be documented somewhere in detail (and if same name is used like in IPv4, but the usage is different, this should be highlighted) Per-device "forwarding" switch controls only autoconfiguration/ndisc aspects. Which way? Does this mean if per device forwarding is off, router advertisements are accepted and processed?
Thanks for clarification,
Peter
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: isa_read/write not available on ppc - solution suggestions ??, Arnaldo Carvalho de Melo |
|---|---|
| Next by Date: | zero copy transport API, Ky Srinivasan |
| Previous by Thread: | Re: ipv6 global forward overrides dev-specific forwarding, kuznet |
| Next by Thread: | Re: ipv6 global forward overrides dev-specific forwarding, kuznet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |