Slashdot Mirror
Hinrich Eilts, Author of ipxtund, Where are You?
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?"
Get it in you!
Oh well, back to dowloading pr0n...
Pr0n K1ng
If he died, he can work on BSD in the afterlife.
Hold on. Someone just knocked over the concrete wall enclosing the parking lot across the street. I'll be back.
I have been pwned because my
And Hinrich Eilts said... nothing you idiots!
Hinrich Eilts's dead, he's locked in my basement!
I'm right here, bud! ;)
Downmix - The Artscene News Source!
\meow, me\ow, meow, m\eow!\
\meow, meow, meo\w, meo\w!!\
\me\ow, meow, m\eow, meow, meow, meow, meow, meow!!!\
Perhaps your looking in the wrong place for the author - the intenet. The author can be easily found on that Mormon-net, the global IPX network that Novell made. Mormon-net uses imprisoned Scientology members that have reached OT-3 and their resulting thought-rays for the transport layer. Good luck in finding a network card that works for it.
(kidding)
Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.
Mozilla still has some missing hackers as well.
Mainly... David Nebinger, 'Uncle George', Makoto Kato, and Thierry LeBouil.
Hi Diaper guy
Have you been in the Meow Mix? It's full of lesbians..
NaveWeiss forever
You could configure GRE tunnels between the sites and run IPX-over-GRE-over-IP. You can encrypt them, too, if you'd like. Fully supported, yadda yadda.
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.
To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.
To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.
To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.
Future
I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.
However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.
You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.
= Mike
--
- poopbot: for all your crapflooding needs
My god, I was going to start with a pitch for a non-GPL solution (I'll end with it instead) ... but did you not follow your own link? There are THREE IPX tunnel packages on that page, not one. Sure, the other two are not much more recent, but the situation is hardly as dire as you make out.
LSM links:
ipxtunnel by Andreas Godzina, from May 2000 (free for non-commercial purposes)
ipxtund by Hinrich Eilts, from August 1998 (GPL) - the one you referenced
& ipxbridge by Kir Kostuchenko, from January 2000 (GPL)
And, to be sure, any IPX-compatible VPN will also solve your problem, permitting IPX traffic to traverse an IP-only link.
But if it were me, I'd go to the source. If you are using IPX, you are most likely using Novell's Netware. Any recent version (5.x, 6.0) will support IPX tunneling using CMD (Compatibility-mode) drivers. This solution has the advantage of being commercially supported (an important consideration for an ISP), relatively easy to configure, and, if you are running the appropriate version of Netware already, won't cost you anything additional.
Out of curiosity, what is the application? Doom? Not many applications (aside from old IPX-only Netware clients and compatibles such as ncpfs) require IPX exclusively.
The Crystal Wind is the Storm, and the Storm is Data, and the Data is Life
Kali? That's what you're looking for. Definately Kali.
Man, get out there now and steal yourself some rubble!
My god himself, this is amazing!
Should we really be making a big 'Ask Slashdot' question out of this subject? It seems like it exposes one of the 'ugly faces' of Free Software that some organization has committed to this package, they apparently can't maintain it themselves, and now the developer can't be found.
Throwing this out as an 'Ask Slashdot' topic makes it a hard-data example that entities pushing proprietary software, i.e. Microsoft, can point to when making the case that 'you won't have anybody to call' with Free Software.
Hmmm, as far as I know Microsoft doesn't support Win95 any more. Isn't that just the way of all old software, free or non-free?
Windows 95 is supported. You can purchase the upgrade from Microsoft for the low-low price of $200. It's called Windows XP.
Help! I've been desparately looking for this missing, uh... coder.. yeah. Her name is Anna Kournikova. I've tried contacting all of the email addresses that I've found listed but she is unreachable. If anyone could give me her current contact information, I would sure appreciate it. Thanks!
There's no place I can be, since I found Serenity.
This page lists an e-mail address for him, eilts@tor.muc.de. I hope that helps.
Best Slashdot comment ever
It takes a decent amount of force to bend that reinforcing reinforcing bar.
(It's comments like this that make me wish 'no bonus' was the default.)
But then again, I could be wrong.
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.
Microsoft doesn't support Windows 95 or 98, NT 4.0 is pretty much left adrift (beyond access to SP6), and Windows 2000 has 9 months left before it too gets cut from new sales. It's the MS way. Upgrade or you lose support. That's the best argument FOR open-source software.
cheers,
Andrew
XP will not run on a 486, Windows 95 will. Upgrades aren't always an option.
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
someone help me find that guy laden ..
...The ghost in the machine...
I'm kidding, of course, but that was the first thing I thought of when I read the article.
Sorry if I spelled it wrong, it's been a long time since I last watched Brazil.
Under capitalism man exploits man. Under communism it's the other way around.
Actually, Windows 98 is still supported...for a little bit at least. Donno about NT 4.0 since I don't use it. Windows 2000 may have 9 more months of OEM sales, but that doesn't necessarily mean that you won't be able to find it on store shelves in shrinkwrapped plastic. Support for 2000 will extended beyond just the cutoff date of selling it in stores. Think Windows 95. They just recently cut off all support for it long after you couldn't find it in stores.
While I'm at it, I'd like to make a list of a few people who I have a grudge aga^W^W^W^Wowe money to. I would like to give them what they deserve.