| To: | ajtuomin@xxxxxxxxxx (Antti Tuominen) |
|---|---|
| Subject: | Re: IPv6 routes and RTPROT_* |
| From: | kuznet@xxxxxxxxxxxxx |
| Date: | Wed, 5 Sep 2001 19:39:42 +0400 (MSK DST) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <200109042057.XAA23356@morphine.tml.hut.fi> from "Antti Tuominen" at Sep 4, 1 11:57:07 pm |
| Sender: | owner-netdev@xxxxxxxxxxx |
Hello! > What do you mean? I missed your point, I mean if the value is not > stored, what protocol I use doesn't really change anything. Right? Think what will happen if it will be implemented. IPv6 routing requests should fill all the fields with something sensible not to fail in this case. F.e. another example: RTM_NEWROUTE for IPv6 _always_ force implicit NLM_F_CREATE|NLM_F_APPEND now, because no other way is implemented. However, careful application must set these flags. So that the day, when kernel will start to understand flags, application will not fail, because flagless RTM_NEWROUTE does not create anything and adds route to head. :-) Alexey |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IPv6 routes and RTPROT_*, Antti Tuominen |
|---|---|
| Next by Date: | Re: ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19, jamal |
| Previous by Thread: | Re: IPv6 routes and RTPROT_*, Antti Tuominen |
| Next by Thread: | Re: ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19, jamal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |