Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
BSD Operating Systems

Network Stack Cloning / Virtualization Extensions 44

HellRazr writes "From the FreeBSD hackers mailing list: 'at http://www.tel.fer.hr/zec/vimage/ you can find a set of patches against 4.8-RELEASE kernel that provide support for network stack cloning. The patched kernel allows multiple fully independent network stack instances to simultaneously coexist within a single OS kernel, providing a foundation for supporting diverse new applications.' We can sure have fun with this..."
This discussion has been archived. No new comments can be posted.

Network Stack Cloning / Virtualization Extensions

Comments Filter:
  • It's cloning itself.
  • Yes (Score:5, Informative)

    by Mensa Babe ( 675349 ) on Monday May 26, 2003 @09:21PM (#6043925) Homepage Journal

    I've heard about the idea and development of the vimage patch and this is a great news, that it's finally done and fully functional. Some of those ideas are not really new, as anyone who knows OS/390 could tell you, but it's really great they can now be used in FreeBSD systems.

    For those of you, who know that I'm involved in building honeynets [honeynet.org], it won't be a surprise, that I am really (by which I mean really) looking forward to use those new features in my future honeypots, firewalls and other security-related projects.

    Actually, those features seem to be created just exactly to be used for deploying virtual honeynets [honeynet.org]. Just imagine what you can do with VMware, vimage-FreeBSD and UML all running on the same machine!

    Great work, Marko.

    • Re:Yes (Score:2, Funny)

      by Jellybob ( 597204 )
      Just imagine what you can do with VMware, vimage-FreeBSD and UML all running on the same machine!


      Bring my crappy computer to a screeching halt?
  • seems like plenty of ideas from plan 9 are backporting their way to the unix-likes.

    People, if you want plan 9 you know where to find it :

    http://plan9.bell-labs.com/plan9 [bell-labs.com]
    • Re:Plan 9 blah blah (Score:4, Informative)

      by rpeppe ( 198035 ) on Tuesday May 27, 2003 @08:56AM (#6047268)
      to be more specific than Dr. Skwid, plan 9 has had multiple IP stacks from the word go (check out the man page [bell-labs.com]).

      but not only that, but the fact that resources can be distributed transparently over the network means that a specific network interface (perhaps an interface to the outside world) can be imported from another machine, and used, exactly as if it were a local IP stack.

      none of this requires any particularly deep magic; it does however require a fresh approach from the ground up, something you're unlikely to find in any of the mainstream unix-like OSes...

  • It is interesting to see monolithical kernel systems trying to implement features which are basic stuff in multiserver microkernel operating systems.
  • by Animats ( 122034 ) on Thursday May 29, 2003 @01:16AM (#6065413) Homepage
    Before BSD, before Bill Joy, there was 3COM's UNET TCP/IP package for UNIX, [quux.org] written by Greg Shaw. Originally, it had a rather weak implementation of TCP, but I fixed that and added ICMP and UDP support. We ran this at Ford Aerospace from 1981 until about 1985. It ran on PDP/11 machines, the original VAX 11/780, and the Z8000. (Our pair of Z8000 machines may have been the first single-chip microprocessors on the Internet.)

    UNET ran almost entirely in user space. All that went into the kernel were device drivers for the network devices and a psuedo-device to allow interprocess communication to the network process. This made modification and debugging much easier. You could kill and restart the network process without rebooting the system.

    Twenty years later, someone has reinvented this approach.

"I am, therefore I am." -- Akira

Working...