Re: [GIT PULL] IPv6 Updates

- ADDRCONF(NETDEV_UP): ifname: link is not ready and ADDRCONF(NETDEV_CHANGE): ifname: link becomes ready messages. While it may look informational, it's extremely annoying in systems with hundreds and even thousands vlan interfaces. regards, -- Hasso Tepper - To unsubscribe from this list: send

Re: /proc/sys/net/ipv[46]/conf/ issue unsolved

don't have any addresses on interface at this point therefore /proc/sys/net/ipv[46]/conf/interface/ are NOT created. That's the point - you can't configure anything before the first carrier up event - ie. cable is plugged on. regards, -- Hasso Tepper Elion Enterprises Ltd. [AS3249] IP Data

/proc/sys/net/ipv[46]/conf/ issue unsolved

. regards, -- Hasso Tepper - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: /proc/sys/net/ipv[46]/conf/ issue unsolved

, -- Hasso Tepper Elion Enterprises Ltd. [AS3249] IP Data Networking Expert - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Sysctl syscall

2.4 and 2.6 kernels and would work with capabilities (sys/capability.h)? Accessing `/proc/sys' directly isn't such alternative as it doesn't work with capabilities. regards, -- Hasso Tepper Elion Enterprises Ltd. [AS3249] Data Communication Network Administrator - To unsubscribe from

Re: [RFC IPv6] Disabling IPv6 autoconf

? regards, -- Hasso Tepper - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [RFC IPv6] Disabling IPv6 autoconf

Herbert Xu wrote: Peter Bieringer [EMAIL PROTECTED] wrote: BTW: this is also the reason why autoconf or accept_ra cannot be disabled by e.g. initscripts *per* interface before bringing one up. You can disable it in /proc/sys/net/ipv6/conf/default/... and then reenable it on the interfaces

Re: [PATCH 09/16] [IPv6] address: Convert address notification to use rtnl_notify()

jamal wrote: CCing Hasso Tepper [EMAIL PROTECTED] Hasso, please comment on this thread (apologies, I forgot the other guy's name; so if you can CC all the necessary suspects to comment, it would help). I fully agree with Herbert Xu: The pid field in the netlink header should be treated

Re: [PATCH 09/16] [IPv6] address: Convert address notification to use rtnl_notify()

Thomas Graf wrote: However, I changed IPv4 addresses to provide the pid and support NLM_F_ECHO and the same will follow for IPv6 address notifications which will mean that quagga sees a different set of IPv4 address notifications. Can you explain what exactly is changed? -- Hasso Tepper

Re: No interfaces under /proc/sys/net/ipv4/conf/

Hasso Tepper wrote: After upgrade to 2.6.16.20 from 2.6.11 I discovered that no dynamic interfaces (vlans, tunnels) appear under /proc/sys/net/ipv4/conf/. /proc/sys/net/ipv6/conf/ is OK. OK, realised out that it's feature. Entries in /proc/sys/net/*/conf/ are not created if interface doesn't

Re: No interfaces under /proc/sys/net/ipv4/conf/

Hasso Tepper: I can think of workarounds for most of problems (although it breaks a hell lot of software here), but how I suppose to configure ipv6 settings for interfaces which have to obtain global ipv6 address via autoconf so that it will work even if cable is not plugged in? I did via

No interfaces under /proc/sys/net/ipv4/conf/

After upgrade to 2.6.16.20 from 2.6.11 I discovered that no dynamic interfaces (vlans, tunnels) appear under /proc/sys/net/ipv4/conf/. /proc/sys/net/ipv6/conf/ is OK. Bug? Or feature? with my best wishes, -- Hasso Tepper - To unsubscribe from this list: send the line unsubscribe netdev

Bug in e100?

Link is Up 100 Mbps Full Duplex ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Kernel configuration and dmesg from problematic machine attached. regards, -- Hasso Tepper # # Automatically generated make config: don't edit # Linux kernel version: 2.6.16 # Mon Mar 20 09:51:47 2006

Re: [PATCH] illegal use of pid in rtnetlink

in various stages of work. -- Hasso Tepper - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH] illegal use of pid in rtnetlink

and at others it was 0 or the large (negative) number when you had more than 1 socket within the same process. CCing Hasso Tepper and more details of the original fix are here: http://lists.quagga.net/pipermail/quagga-dev/2005-June/003507.html No, that was different issue and isn't related with issue

Re: [PATCH] illegal use of pid in rtnetlink

again link to the archive to the message I posted with new netlink.7 no one bother to comment yet ;). http://www.mail-archive.com/netdev%40vger.kernel.org/msg06166.html -- Hasso Tepper - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED

Re: [PATCH] illegal use of pid in rtnetlink

jamal wrote: On Wed, 2006-08-02 at 22:50 +0200, Hasso Tepper wrote: jamal wrote: Ok, thanks for the reminder Hasso. so essentially at the moment the pid that will show up (if quagga added the v6 route) will be that of quagga, correct? No. Quote from Alexey: I sense you missed my

Re: [PATCH] illegal use of pid in rtnetlink

jamal wrote: So the question is what would be the address/nl_pid of something issued by an ioctl (refer to my earlier email to Alexey). It's the kernel who creates this message and puts it to the netlink domain, so I'd say 0. -- Hasso Tepper - To unsubscribe from this list: send the line

Re: [PATCH] illegal use of pid in rtnetlink

and negative numbers stuff is valid only if application doesn't set nl_pid. It's completely legal for application to do that before calling bind() and if there's no conflict (no already open netlink socket with this nl_pid), everything is OK. -- Hasso Tepper - To unsubscribe from this list: send

netlink.7

After seeing yet another project which had pointers in the code comments to the false statements in the netlink.7 man page, I decided to spend some time on improving man page. Comments and improvements are welcome especially regarding TODO's, XXX's and FIME's in the page. -- Hasso Tepper

Re: Patch: RFC2863 #1 (incomplete)

link is known to be usable (IFF_RUNNING) and 192.168.1.0/24 is reachable via wireless as well. -- Hasso Tepper Elion Enterprises Ltd. WAN administrator - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http

Re: Patch: RFC2863 #1 (incomplete)

information. I don't see any concept of OSPF's own link state detection here. regards, -- Hasso Tepper Elion Enterprises Ltd. WAN administrator - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http

Re: IP RECVTTL

. -- Hasso Tepper Elion Enterprises Ltd. WAN administrator - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: IP_RECVTTL

. Also comment about SOL_IP portability added to the NOTES and duplicate IP_PKTINFO removed in the VERSIONS section. -- Hasso Tepper Elion Enterprises Ltd. WAN administrator --- ip.7.orig 2005-07-18 19:02:32.0 +0300 +++ ip.7 2005-08-19 11:20:23.0 +0300 @@ -285,7 +285,7 @@ Expects

[PATCH 2.4.32-pre3] V6 route events reported with wrong netlink PID and seq number

with 2.4 kernel. Without this patch it's not possible to support IPv6 routing in Quagga without race conditions. Users (including myself) are using this patch in production for some months and haven't noticed any issues with it. -- Hasso Tepper Elion Enterprises Ltd. WAN administrator diff -Nur kernel