Slashdot is powered by your submissions, so send in your scoop

 


Forgot your password?
Close
typodupeerror
×
Security Operating Systems BSD

FreeBSD Gets 'Fast IPsec' Implementation 62

Posted by michael from the better,-faster:-pick-any-two dept.
An anonymous reader writes "Sam Leffler (yes, one of the authors of the BSD Design and Implementation book you have on your bookshelf if you know anything with operating systems) has just committed a new FAST_IPSEC implementation to the FreeBSD 5.x source tree. It's a merge of the KAME IPsec implementation and the OpenBSD hardware crypto accelerated IPsec implementation. You can read the commit message here."
This discussion has been archived. No new comments can be posted.

FreeBSD Gets 'Fast IPsec' Implementation More

FreeBSD Gets 'Fast IPsec' Implementation

Comments Filter:
  • Heck, I might actually have a use for this. Only if CURRENT were a little more stable.

    I certainly can't wait until this get's MFC'd.

    • Re:Cool! (Score:1, Funny)

      by Anonymous Coward
      You mean, "only if -CURRENT were a little more
      -STABLE." HAHA.
    • Kernel panic for two weeks now. :(

      Hopefully things will shape up as -CURRENT has gone into feature freeze and will soon go into code freeze in preperation for 5.0 Release, but don't expect 5.0 to be too stable.

      • Re:Cool! (Score:1, Informative)

        by Anonymous Coward
        Compiles fine on my machine. The trick is to keep up with the mail lists for CURRENT and /usr/src/UPDATING.

  • Things preventing me from using FreeBSD: (Score:1, Interesting)

    by Anonymous Coward
    Although I'm well impressed with the development methodology and stability of FreeBSD, I'm tied to using Linux on my desktop right now because of the following four things. I know this is quite OT, but I've tried other places for questions...

    1) USB joypad support. Apparently non-existant, although I see some references to it in ports like BZFlag. FreeBSD USB page claims support may come in the future.

    2) Hardware 3D. Work is ongoing here, but right now it's a bit of a messy job and I'm hoping it will be fully in the kernel with 5.0.

    3) Sound -- Linux gives me two /dev/dsp[0,1] devices, but AFAICT FreeBSD only has one. Yeah, I know I can use something like EsoundD, but it'd be nicer to have it this way. Any clues?

    4) /bin/cp. Yeah, strange, but I tried to copy a large number of MP3 files from a backup CD onto my FreeBSD installation, but its cp died with "too many files" or the like. Had to "cp a* b* c*", then "d* e* f*" -- shame the GNU tools can do this without hassle.

    So, this probably deserves no mod points, but if anyone has any info here (should be clear that I've done some research!), please let me know.

    • I never used FreeBSD, but your /bin/cp problem is simple: you're bumping into the command line length limit. It exists in Linux too, although from what you say it's larger. Just work around it, for example:
      find . -exec cp {} /mp3 ';'

    • Re:Things preventing me from using FreeBSD: (Score:1, Informative)

      by Anonymous Coward
      For my SB Live card I get a bunch of devices for the different channels/mixers. Take a look inside /dev/MAKEDEV :) You'll figure it out.
    • tar cf - .|(cd /mp3 && tar xvpf -)

      It keeps permissions as well. You can even throw in a ssh and copy things over to another machine i.e.:

      tar cf -|ssh -C machinename tar xvpf -

      or

      tar cf -|gzip -c|ssh machinename 'cd /mp3 && gzip -dc|tar xvpf -'

      Or throw in your favorite archive (cpio, pax) and compress (compress, bzip2) program

Slashdot Top Deals

Adding features does not necessarily increase functionality -- it just makes the manuals thicker.

Close