|
Your message is the first one I receive because of the virtual routing idea. I didn't produce more than the NAT-paper, i.e. there's no code for this function yet (from me). Currently I'm working on a static NAT only release to get a stable base. Adding the virtual server stuff into the design produced some hardly readable code and instabilities, because it was done in a hurry to see if and how it worked at all. The basic design ideas will still be the same, however. I've decided to go towards a (more?) stable release with less functions because most of the feedback I got was from people who wanted/want (or are using(!)) the (static NAT) code in production systems. Again, the basic design will stay the same. I will be able to reuse almost all my virtual server code when (if?) I start re-adding it to this new base. I'm currently unable to test anything I write, though, since I don't have my own test network. If you're interested in developing your stuff on top of the new base just drop me a line. First I'd like to know what you've got so far, of course. Since I didn't think about implementation details for virtual routing there might be some design decisions to make that could influence the base code. PS: Something completely unrelated: I was skiing in Keystone, Colorado, over Thanksgiving (5 days), see the pictures named like "ski*.jpg" (I'm the guy in the yellow jacket) |
Messages
Outline:
virsual route by lan, 5/26/98
No problem,... by Michael Hasenstein, 5/26/98