Skip to contentSkip to conversation

Netlink Implementation.

DISCUSSION Eric Bambach 1 participant 1 message Oct 24, 2004 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

LKML,

Here is my post from Linux-net. I am re-posting here because it's appropriate
and I have not met with a resolution on linux-net :(

Hello again code gurus :)

Yes another fight in my netlink saga. Thanks to all who have replied before
and I have learned alot from the rfc's and zebra/iproute and have contructed a much more robust implementation. I have sent the kernel a message defined as below. However I have not learned what exactly I should be expecting from the kernel. That is, my message gets a reply from the kernel about eth0, however on my machine i have eth0,1,2,ppp0 and I would like information about them all. I have NLM_F_ROOT set on the packet as I was under the impression that this would dump information about all the interfaces. I have also tried
incrementing msg.info.ifi_index to 0,1,2,3 etc. No matter what these values
I always recieve this output form my program.
#./nl_test_prog
Found device: eth0 - 1
Found address: <--(Dont care about blank yet, main problem is only
1 if shows. This is minor)
Received end of msg.

-Am I wrong to expect the kernel to send me data about all the interfaces? -Am I calling this wrong?
-What can I do to query all the interfaces?

I do loop through all the rta messages and I receive only 1 nlmsg packet from
the kernel when calling recvmsg(). I have also tried without OR'ing NLM_F_MATCH. I have run it through a debugger and confirmed although there are multiple RTA atributes in my netlink packet but they all refer to eth0.

-Should I be expecting multiple packets (NLM_F_MULTI)?

Here is my nl_packet construction.

  msg.hdr.nlmsg_len = sizeof(msg);
  msg.hdr.nlmsg_type = RTM_GETLINK;
  msg.hdr.nlmsg_flags = NLM_F_REQUEST | NLM_F_ROOT | NLM_F_MATCH; 
  msg.hdr.nlmsg_pid = getpid();
  msg.hdr.nlmsg_seq = seq++; 
  msg.info.ifi_family = AF_UNSPEC; //AF_UNSPEC for ipv4
  msg.info.ifi_type = NETLINK_ROUTE;
  msg.info.ifi_index = 0;
  msg.info.ifi_change =  (0-1); 

----------------Looping over the attributes later in code-------------- /* Loop over the attributes in this message */

    while(RTA_OK(rta, len))
    {
      switch(rta->rta_type)
      {
      case IFLA_IFNAME:
        cout << "Found device: " << (char *)RTA_DATA(rta)<< " - " <<  
info->ifi_index << endl;
        break;
      case IFLA_ADDRESS:
        cout << "Found address: " << (char *)RTA_DATA(rta) << endl;
        break;
      }
      rta = RTA_NEXT(rta, len);
      /* We hit the next packet */
    }// Packet Looping while()

More info/code available upon request.

Any help would be appreciated.

----------------------------------------
EB

Quoted 4 lines

All is fine except that I can reliably "oops" it simply by trying to read from /proc/apm (e.g. cat /proc/apm).
oops output and ksymoops-2.3.4 output is attached.
Is there anything else I can contribute?

The latitude and longtitude of the bios writers current position, and a ballistic missile.

		--Alan Cox 2000-12-08 

----------------------------------------