What's the proper way to traverse a getifaddrs() interface list?

I have an application where I want to collect information on the network interfaces. I've researched this and the function getifaddrs(struct ifaddrs *ifap) appears to be the way to go, but I'm having some trouble understanding exactly how to process the information returned by this call. It's

Can lagg0 failback be prevented?

We're using the lag driver to provide automatic failover in case of a network outage. The default configuration looks like this: lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether

nfe taskq performance issues

We've been hitting serious nfe taskq performance issues during stress tests and in doing some research on the problem we came across this old email: From: Ivan Voras ivo...@freebsd.org Date: April 28, 2009 3:53:14 AM PDT To: freebsd-thre...@freebsd.org Cc: freebsd-net@freebsd.org,

Broadcast packet not being sent

I am using scapy to construct a UDP broadcast packet. The code I'm using is: packet=Ether(dst=ff:ff:ff:ff:ff:ff)/IP(dst=255.255.255.255)/UDP(dpor t=3)/payload sendp(packet) Send 1 packets. This works fine when I have an IP assigned to the box. However, when no IP is assigned, I get

RE: Broadcast packet not being sent

Problem solved. I have to explicitly set cond.iface before sending the packet. User error... -Original Message- From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On Behalf Of Peter Steele Sent: Monday, January 12, 2009 4:02 PM To: freebsd-net@freebsd.org Subject

RE: Having problems with limited broadcast

Peter, leaving aside the issue of FreeBSD limited broadcast, have you considered ZeroConf, and in particular the IPv4 Link-Level Addressing portion of it to meet your basic get the boxes addressed requirement? http://www.zeroconf.org/ http://files.zeroconf.org/rfc3927.txt I don't have any

RE: Having problems with limited broadcast

Thanks for the suggestion though. I'm not familiar with ZeroConf; I'll check it out. ZeroConf is an interesting concept. Unfortunately it restricts IPs to the 169.254/16 range and it is very likely some of our customers will want to be able to configure our boxes to an IP range of their own

RE: Having problems with limited broadcast

If this is all going over an L2 LAN, why not do the initial discovery and general configuration exchange over IPv6? :P Link layer network-scope addresses to the rescue. (think: just like apple wireless base stations and MacOSX hosts doing configuration do..) It's really a matter of time. We

RE: Having problems with limited broadcast

The folk who point out that link-local addresses could be used, have an interesting suggestion which might work for you. It's definitely interesting, but it is very likely that some of our customers will want to be able to set their own IP ranges and not be limited to 169.254/16. So we need a

RE: Having problems with limited broadcast

Peter, I understand your issue with the (apparent) restriction of the 169.254/16 range, though I'd point out that the IPv4-LL addressing scheme is considered a fall-back plan by most systems implementors. Your systems could look for DHCP first then failing that, drop back to IPv4-LL and get

RE: Having problems with limited broadcast

BTW: If you guys are already looking at scapy, you may also wish to give pcs.sourceforge.net a look as an alternative. I didn't come across that in my research. I'll have to check it out. Thanks. Peter ___ freebsd-net@freebsd.org mailing list

RE: Having problems with limited broadcast

We ARE talking about just a LAN here, right? Also, these computers are not on the internet? They have absolutely no connectivity? (Unlikely). When our boxes are initially deployed, they have no IP addresses assigned to them. Their ifconfig entry looks like this: ifconfig_lagg0=laggproto

RE: Having problems with limited broadcast

You will need to go to the pcap layer to send limited broadcasts w/o any IPv4 addresses configured in a BSD stack for now. If you have an IP on the interface, you can just use IP_ONESBCAST. Yes, I can send broadcasts if my box has an IP. Since we are writing our own DHCP-like service though

Having problems with limited broadcast

We have a Python app that implements a DHCP-like protocol using limited broadcast using address 255.255.255.255. Our code works fine on Linux and FreeBSD but we cannot seem to get broadcast to work on FreeBSD. We've tried both Python and C under FreeBSD 7.0. I've found a lengthy discussion of

Having problems with limited broadcast

We have a Python app that implements a DHCP-like protocol using limited broadcast using address 255.255.255.255. Our code works fine on Linux and FreeBSD but we cannot seem to get broadcast to work on FreeBSD. We've tried both Python and C under FreeBSD 7.0. I've found a lengthy discussion of