IPFW2 branch for testing

bycn82’s rewrite of IPFW2 is available as a git branch to try out; he’s posted the link.  Please try, especially if you are still working with the original ipfw.

(note: remember, ‘ipfw’ in DragonFly is what was called ‘ipfw2’ years and years ago because it was a replacement of the original ‘ipfw’ in FreeBSD.  It was called ipfw2 but referenced as ipfw so that the same commands worked.  Technically, this branch bycn82 is working on would be ipfw3, but he keeps referring to it as ipfw2.  Confused?  Good.)


Markus Pfeiffer has imported FreeBSD’s if_lagg to DragonFly.  It’s for talking LACP over multiple network ports, so that the traffic from those multiple ports can be aggregated – if what’s on the other end generally understands LACP.  (Failover mode may not count.)  Please test if you have that sort of surfeit of network ports.

How do you test a balloon memory driver?

I’ve wanted more support for virtualized DragonFly systems.  Sascha Wildner put together an experimental balloon memory driver to test out, and I ran it on two virtual machines separately, one with it loaded and one without, on the same host system.  The problem is, I can’t tell what it does.  The two machine reported almost the exact same RAM usage during a buildworld.

Any VMWare/virtualization experts out there able to tell me what needs to be tested to verify this?

In Other BSDs for 2014/03/22

I have a list of commits I’ve saved between the various BSDs of licenses getting corrected to the 2-clause BSD license; that would definitely be a good cross-BSD project to sync.

New USB on by default

DragonFly has moved from the old USB stack to USB4BSD by default.  That means:

  • If you are already using USB4BSD, you will want to remove WANT_USB4BSD from your kernel config.
  • If you have trouble, switch back to the old USB.
  • There’s some drivers that are not yet converted; help with them would be appreciated.  
  • A full kernel/world build and ‘make upgrade’ will be needed in either case.

Sascha Wildner’s announcement email has all the gory details, including the kernel config changes to move back to the old USB setup.  This is of course in master; 3.6 users are unaffected.

Do you have a wpi(4) or iwi(4) device?

If you have an ath(4), wpi(4) or iwi(4) wireless network link, and you’re running DragonFly-master, please update.  Sepherosa Ziehau has pushed Johannes Hoffman’s wlan_serialize branch, which means bringing up wlan0 is a bit easier – and less crashy.

It needs to be tested for wpi(4) and iwi(4), however, so if you have success or failure with those devices, please say so in reply.

(new post category starting now: “Please test”)