Slashdot Mirror

← Back to Stories (view on slashdot.org)

Hinrich Eilts, Author of ipxtund, Where are You?

Posted by Cliff on from the are-ya-still-out-there dept.

Leandro Dardini is desperately seeking Hinrich: "As consultant for a local provider, I have to present a solution for a big problem: tunnel IPX over IP to permit old application users to connect via Internet. After digging google, I found ipxtund, written by Hinrich Eilts in 1998. It works great even after 4 years, but I have a question to the author. The author vanished. After searching again in Google, I found the last clue of Hinrich in a post on 23 Jul 1999, then nothing. I don't want to think the worst, but, Hinrich Eilts, where are you?"

2 of 55 comments (clear)

  1. you can use tunneled ethernet bridging too... by obi · · Score: 2, Interesting

    I'm using vtun.sourceforge.net (which is still under active development) combined with the universal tun/tap driver in the kernel and the linux bridging code to create a more generic solution.

    On both sides I create bridges which enslave a physical nic, and the "virtual" tap device.

    Since this is an ethernet, not an IP tunnel, it tunnels appletalk, and should tunnel IPX and other traffic too.

    It can be compressed and (of course) encrypted too. Performance is very good, even for multiple tunnel, and can be tweaked according to the processor power available.

    This way I have even bridged more than two geographical locations too. For instance with 3 connections 1,2,3 I had connections between 1-2, 2-3 and 3-1. But because of the bridging code Spanning Tree Protocol, those redundant connections will only buy you "backup" connections, there's still going to be two nodes that have to communicate via a third. (If you use vtun to do IP tunneling instead of ethernet tunneling, you can use proper routing of course.)

    I'm very happy with vtun, it's easy and extremely versatile.

  2. IPX over IP by Strog · · Score: 2, Interesting

    I was looking at the IPX over IP issue off and on.

    I like to play Red Alert 2 with my brother and a couple other friends. While it uses IP on the internet it needs IPX to run LAN games (dumb). I was thinking about IPX over IP tunnels over cable network so we can all play together every so often when we get the bug.

    I dismissed the idea pretty quick at first because it was really unnecessary and silly to mess with. I later came back and thought it would be a good way to learn more about the intricacies of networking. I learned way more about networking running an Unreal Tournament server than a lot of books will teach. It's great for learning how much you can do with your bandwidth, tune for lowest latency possible, learn how the various tradeoffs affect it all, how ram/cpu affect performance, etc.

    I played around with a borrowed Mac and atalkd to support the Macs at work (a few in Media Arts only). They bought new one and when 100% OS X so Appletalk went away. I still played with appletalk to my linux box for experience anyway. They got a piece of hardware that they needed but it didn't support OS X. The storage they wanted to connect to supported Appletalk but was in another subnet. The netadmin refused to add Appletalk to his routing/bridging/etc. for one machine (the network here is complex enough already). I put up a basic Linux box to connect to the storage by NFS and reshared it with atalkd on the subnet with the OS9 machine on it. I looked like a hero and this was right before reviews/raises.

    I don't underestimate learning a skill even if it is just for game or hacking for hacking sake. You never know when it could help you later. At least a game/whatever is an application you can test against and have some goals