- 1. n to 2.4.20rc1 (score: 1)
- Author: pf@xxxxxx>
- Date: Fri, 15 Nov 2002 12:38:12 -0500
- 1) Awhile ago there was a flame war about using SIOCGIFCONF/SIOCGLIFCONF to get lists of interfaces. This was suggested as being a bad way. 2) bind 9.3snapshot is able to get a list of IPv4 addresses
- /archives/netdev/2002-11/msg00135.html (8,199 bytes)
- 2. . (score: 1)
- Author: xxxxxx>
- Date: Fri, 15 Nov 2002 20:00:51 +0100
- Physical devices are read using /proc/net/dev If you want IPv6 addresses you can read and parse /proc/net/if_inet6 That is the old fashioned way. The new fashioned one is to query them using rtnetlin
- /archives/netdev/2002-11/msg00136.html (8,706 bytes)
- 3. restart locking bug? (score: 1)
- Author: x>
- Date: Fri, 15 Nov 2002 17:46:55 -0500 (EST)
- ... Here is a comment and our standard snippet of code to do this: ________________ char linebuf[400]; /* Max possible line is 192 chars. */ FILE *fp; int ifnum; /* Yes, the only list of physical net
- /archives/netdev/2002-11/msg00139.html (11,047 bytes)
- 4. : looking for help with scanning of IPv6 interfaces (score: 1)
- Author: >
- Date: Fri, 15 Nov 2002 23:52:00 +0100
- Check iproute2 or zebra source. iproute2 has a libnetlink which is quite useful. I also wrote some manpages (netlink(3),netlink(7),rtnetlink(7) etc, but admittedly they are not very good) Somewhere
- /archives/netdev/2002-11/msg00140.html (9,294 bytes)
- 5. : ifconfig TX/RX errors (score: 1)
- Author: xxxxxx>
- Date: Mon, 18 Nov 2002 21:31:17 -0500 (EST)
- You forgot the draft, Andi. Although doesnt document every little detail (someone should) -- it goes a long way to describe the architecture and concepts behind netlink. A not final version: ftp://oa
- /archives/netdev/2002-11/msg00159.html (9,463 bytes)
- 6. looking for help with scanning of IPv6 interfaces (score: 1)
- Author: Michael Richardson <mcr@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 15 Nov 2002 12:38:12 -0500
- 1) Awhile ago there was a flame war about using SIOCGIFCONF/SIOCGLIFCONF to get lists of interfaces. This was suggested as being a bad way. 2) bind 9.3snapshot is able to get a list of IPv4 addresses
- /archives/netdev/2002-11/msg00353.html (8,214 bytes)
- 7. Re: looking for help with scanning of IPv6 interfaces (score: 1)
- Author: Andi Kleen <ak@xxxxxxx>
- Date: Fri, 15 Nov 2002 20:00:51 +0100
- Physical devices are read using /proc/net/dev If you want IPv6 addresses you can read and parse /proc/net/if_inet6 That is the old fashioned way. The new fashioned one is to query them using rtnetlin
- /archives/netdev/2002-11/msg00354.html (8,776 bytes)
- 8. Re: looking for help with scanning of IPv6 interfaces (score: 1)
- Author: Donald Becker <becker@xxxxxxxxx>
- Date: Fri, 15 Nov 2002 17:46:55 -0500 (EST)
- ... Here is a comment and our standard snippet of code to do this: ________________ char linebuf[400]; /* Max possible line is 192 chars. */ FILE *fp; int ifnum; /* Yes, the only list of physical net
- /archives/netdev/2002-11/msg00357.html (11,091 bytes)
- 9. Re: looking for help with scanning of IPv6 interfaces (score: 1)
- Author: Andi Kleen <ak@xxxxxxx>
- Date: Fri, 15 Nov 2002 23:52:00 +0100
- Check iproute2 or zebra source. iproute2 has a libnetlink which is quite useful. I also wrote some manpages (netlink(3),netlink(7),rtnetlink(7) etc, but admittedly they are not very good) Somewhere
- /archives/netdev/2002-11/msg00358.html (9,417 bytes)
- 10. Re: looking for help with scanning of IPv6 interfaces (score: 1)
- Author: jamal <hadi@xxxxxxxxxx>
- Date: Mon, 18 Nov 2002 21:31:17 -0500 (EST)
- You forgot the draft, Andi. Although doesnt document every little detail (someone should) -- it goes a long way to describe the architecture and concepts behind netlink. A not final version: ftp://oa
- /archives/netdev/2002-11/msg00377.html (9,506 bytes)
This search system is powered by
Namazu