Slashdot Mirror
SLiRP Project Needs Maintainer
Karl A. Krueger hopes someone might be interested in following up on this bit of info: "SLiRP is a program by Daniel Gasparovski which lets you emulate a SLIP or PPP connection over a shell dial-up connection. In other words, it's a PPP "driver" that runs entirely as a user process. Unfortunately the last official release was in 1996, and the author is apparently no longer interested in maintaining it. The license is somewhere between BSD (requires attribution) and GPL (requires freedom). I've made a few minor fixes to it so that it compiles and runs under a modern system (Debian 2.1 -- should work under others as well) but there's quite a bit that could be done with it if someone wanted to actually maintain the thing. Anyone interested? In any event, my patched version is
here. "
I used SLiRP just a few years ago while at college in Pittsburgh (96-97).
My school didn't have anything in the way of dial-up Internet access (probably still doesn't) and the cheapest local ISP was offering shell accounts for $12 a month. Well I preferred (and still do) a shell account to a PPP-only account anyway!
I was still running DOS on a P75, but I played many a game of QUAKE using SLiRP, a DOS TCP/IP stack and that shell account.
Oh yeah. I forgot that I eventually modified the script to run under Windows' dialup networking, using the scripting feature under 95. Always struck me as kinda funny, dialing up to the freenet, using lynx, etc., without ever actually 'seeing' it being used (as there was the option to suppress text in the script).
Linux could already do this via IP Masquerade. (Yes, it not only works for LANs but over PPP too.)
The only problem with this is, of course, you need the omnipotent root to set it up. With SLiRP, you don't, which IMO the only thing that makes it beneficial compared to IP Masq.
I remember having to put wording into my old ISPs AUP to prevent use of this little darling...
Of course, it you shell into a FBSD box, you can just use ppp -direct, and not bother with this little program...
People laugh at me because I still use slirp with my primary ISP. I started using it (my first open source software) when they were charging a $50+ setup for ppp acccounts. Then, I realized slirp is keeping people out of my machine. Not only did I get ppp for the price of a shell account, but I got an instant firewall too! I'm still "grandfathered" on my ISP as a shell account, since they no longer provide them. (I couldn't manage without telnetting in to get my mail.)
So, now I got an ISDN connection (through work). Took me 3 days to get a reasonable firewall setup, and I still can't get my second NIC to give up IRQ 3 for the modem. Slirp saved me time, money, and peace of mind for many years.
Thank you, Danny!
Just a word in support of SLiRP
For students on a limited budget and as part
of your general Geek toolkit SLiRP is an
excellent item. I will continue to use it
for the foreseeable future till I can
afford DSL at home. I commend whomever will
take up the charge of supporting an unsung
but very useful piece of Linuxdom.
I can attest that one can, indeed, tunnel PPP over X.25. It was done in a commercial product I've worked on. Regards, Rene S. Hollan (posting anonymously... well sorta)
So I installed a copy of SLiRP on my netcom shell account, and used that for network connectivity until a couple months ago - when I finally got an ADSL link. I still use it as a backup for when Pack Bell dies on me.
My mail exchanger has always been separate from my ISP, reached via UUCP polling. (This lets me change ISPs without losing mail connectivity.) The mail server has two entries for it in the Systems file, the first one trying (twice!) to make a UUCP-over-IP connection if the net is up. The second dials up the exchanger via modem if the first fails and the modem is free. In the days when my network connection was also via phone - either to the fly-by-night ISP or the SLiRP hack, it used the same modem - after I tweaked my PPP install to use the same locking scheme. If the net was up, it used it in the background. If it had dropped, it made the call. All automagic. (I have an alias that forces a poll if I want to be sure something goes out right away or check for mail without waiting for the next poll.)
Now when on the road I can call into the same modem from any phone, picking up and dropping off mail (again via UUCP-over-IP-over-PPP) in parallel with tweaking the home network or doing a quick surf. (Who needs POP and fetchmail?)
If I ever decide to save a few bucks and downgrade from "enhanced" to "basic" DSL, SLiRP is one way to let my whole net of machines masquerade as a single host on the one IP number.
So these "obsolete" protocols aren't really so obsolete.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
yeah, but he has a point there - this type of network linking would be very subtle, looking just like a telnet session...
d
7 years ago, we got 20 dial-in analog lines for our userbase of 255 CIS students. Now we have 16,000 students (all students get e-mail now of course, not just CIS), but still have 20 lines.
Why? The college doesn't want to get into the ISP business. It's expensive and most students have ISP accounts of their own anyway. It's a decision I supported 100%.
But there's always the poorer students who gets screwed by policies like this. So we maintain shell access for those students to get their e-mail and -- if they can figure it out -- allow them to use SLiRP to get something approaching a PPP line.
We put up a web page explaining the steps in getting it to work, but specify that we don't support it. This way, the student who isn't burdened with a lot of cash but has half a brain can get equal access to the net at no cost.
So far, policy works fine. Most students use their own ISP, and our 20 lines don't get maxed out, but most of those that DO use it, are running slirp.
It'd be nice to see it maintained. I've seen cases where it drops the last byte of an FTP transfer and haven't been able to figure out why, for example. (We run DG/UX boxes here, might be an OS compatability issue... Also, DG/UX doesn't have a pppd that will work on a non-serial connection, ruling out that...)
Now the next slirp question I'm sure to hear is -- can it be hacked to work with Dreamcast? Beings I just bought one this morning and my first analysis of it -- answer is no. Doesn't seem to support a connection script... just PAP or CHAP I suppose... :-(
I'm the SysAdmin for the machine that hosts the "Official" SLiRP homepage at http://blitzen.canberra.edu.au/slirp/. Looking through the logs reveals that people are indeed still downloading it, despite it being several years since a proper release. Something on the order of 200 to 400 FTP downloads of SLiRP related stuff a week, and 2000 to 3500 hits on the SLiRP related web pages a week.
I can probably continue to provide hosting for SLiRP should anyone choose to continue development.
Hello,
I have been maintaining slirp since mid 1998 on an odd-fix basis.
The current version is 1.0g and it contains some fixes compared to 1.0c
that should not be lost. See the changelog on
http://smith.esat.kuleuven.ac.be/~vdb128/slirp .
I am a conservative maintainer and do not have the time to implement
new flashy features. I urge every patch-submitter to verify the changes made
and, if thought acceptable, to verify them again. I will check the newest
changes in a month or so.
A new maintainer should now that this may take more time than initially
bargained for. For the new maintainer: notify me if
1. you're serious
2. if the changes from 1.0c --> 1.0g are merged.
Sincerely,
vdb128@tele.kotnet.org
Argh. Will someone please take this fucking idiot out of the gene pool? It's enough he's got to spread his worthless comments all over the W. Stevens death article, now he's sucking our bandwidth elsewhere. Fuck off and die, you moron.
Forgive me for ranting... it's jerks like this who make me question the viability of the human race.
And I'm sure I'll get a comment calling me a Jizzwhacker or somesuch for this. Shut up. Just shut up, Junior, until you get a clue.
/FLAME
Ok, lots of posts but I haven't seen my two
favorite related slirp virtues.
1) Security. Slirp does *NOT* forward arbitrary
packets back down your phone line for you
to deal with using your firewall setup. If
you don't configure incoming connections, there
won't be any. Plus if someone portscans the
other end of the TCP connection, they will be
portscanning the server system.
I've never really felt as safe with PPP+
firewall as I did running slirp.
2) Anonymity. Sort of. All connections look like
they are coming from the server machine. (I
guess if they run ident the jig would be up).
-- cary
I wrote/maintained the FAQ for the alt.dcom.slip-emulators usenet group for
;-) adapted the then current PPP
;-)
awhile - it's been included in the release
of slirp for eons -and hasn't been updated
for just as long.
Slirp maybe one of the first Open Source
projects that helped put a company out of
business! TIA, "The Internet Adapter" has
been mentioned here a few times already.
TIA initially did Slip only, and would have
PPP Real soon now. Slirp came on the scene,
and was working pretty well after a couple
releases. We complained to Dan about PPP,and
a clever programmer in Finland(lots of those
around here
driver from Linux to Slirp! TIA didn't have
it for several months after that - at which
point they were probably too late. Slirp
just acquired a working PPP driver in a
period of a few weeks!
Ah the memories
Steve Wilson
Have you compiled your kernel today??
I have been using it for 3 years. I know lots of students here use it too. Most of time, I can connect at 33.6k. That is enough for surfing web.
I'm behind a firewall all day and have a non-firewalled machine that I can telnet to. Using a second, serially linked machine inside the firewall, I can use ICQ where I couldn't before, thanks to SLiRP, and that second machine is pretty much totally isolated from the internal network - so even if it does get hacked (which would be even rarer because no ports are being forwarded), it could sever the slirp link but then the machine becomes quite useless from the outside...
Is there some remotely constructive way of getting this off your chest?
I have no idea what you are complaining about, and the tone of your post makes you look a lot worse than the guy you're flaming.
Try counting to 10 before posting.
At least one of our shell users uses it. He prefers to pay the reduced price for a dialup shell and in return, get a semi-complete internet connection. We're not going to stop the guy. :) --Michael Bacarella
I remember how it was, I'm sure you all do too
..
I thought I was so cool bumming a 14.4 K free "Internet connection" of a shell account from school.
Oh well, those were the days...
Now we have 56K ISP connections at ~ $5 - $10, decent ADSL connections ~ $3.0
Reminiscing
-----Transmission Complete----- If you want to email me...Don't
So, who does have a use for this?
Hello,
:)
One of the new features getting ready for 2.4 is the so called "generic" PPP layer. This is a generic implementation of PPP which supports both modem and ISDN connections and possibly others, I'm not sure. What I'd be curious in knowing is whether it would be easy to make a module for 2.4 that exports the kernel PPP code / pppd into a nice file stream such as used by SLiRP in PPP mode. This would effectively allow Linux machines "internal" SLiRP without any additional cost. Why? I don't know.
This would not however resolve the number one reason for using SLiRP (or, at least the only reason I've ever used it): shell accounts. Most ISPs or places where you would have non-PPP shell accounts would not typically be running Linux and especially would not likely be running a recent kernel. So, there is most definately a continuing need for SLiRP but would a lot of changes and "maintenance" be needed in SLiRP to reach that goal of legacy support? I don't know that either.
So, does anyone know if the Linux 2.3/2.4 ppp layer can be munged in this manner? That could be so much fun...
Joe
I guess I wouldn't mind seeing it maintained just for sheer historical coolness, but most people (myself included) would rather work on a more useful project. And of course, maintaining a package without a userbase is a little hard (no bug reports!)
I remember using this program with my first graphically capable internet connection. It was great, but thank god for my current T1 connection. =) I would be willing to help out with maintaining the project, but I don't have to time to take it on by myself.
-- Just my $0.02 worth...
One could use slirp via telnet on an existing PPP or ethernet connection to make two distinc networks appear to be local to your slirp host.
---- aut viam inveniam aut faciam
Oh man! I used this neat program back in my college days (1995+). Man, I think I was the first one to discover this program and use it on my university shell account while Internet was new over there. Eventually the firewall came along. DOH!
Anyone remember TIA? Another SLIP emulator I believe.
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
My god, what a useful hack. I remember how wicked I felt getting PPP access over a dialup shell account...
What'd be really nice: A signed Java applet that can access the serial port (the comm api, but I'm not sure how it interacts with signatures / applets), uses ppp to talk to the device, and then sets up a secure tunnel to a remote site. Then an appropriate web browser and a serial port could make a mostly secure VPN link for PDAs. (The serial port can be sniffed easily. A better solution would source the encrypted tunnel from within the PDA, but this is better than nothing.)
Jason, ejr@cs.berkeley.edu
I first used it years ago, with a shell account on a certain national provider. I still have that shell account, every once in a while I find a use for it, just enough that I haven't dumped it yet. Mostly telnetting in and doing traceroutes and the like. But when I went on vacation to Hawaii earlier this year and decided I wanted to stay in touch via email, I realized I could do it, with my PalmPilot, Palm modem, said shell account, 800 number to said shell account ($8/hr from Hawaii), and SLiRP! I even still had SLiRP all set up to go. It was great, worked flawlessly. Granted, if I had to get a new account to do it, I would have just gotten a PPP account, but having the shell account anyway, SLiRP was a perfect solution.
SLiRP was the last in a string of programs of that sort that I used regularly. The first was DNet on the Amiga. Man was that ever a hack! But it worked really well within it's limits. After I started running NetBSD on that Amiga, and when I first moved to Linux, it was Term for a short time until SLiRP appeared.
That little matchhead sized web server, iPic that's been featured on slashdot several times, was for a while connected to the net through a Digital Unix box running SLiRP. Looks like it has a normal SLIP connection now, but there's another modern use for you.
Ummm....really don't know how many people from India read Slashdot but had a thought...
SLiRP could be used on a shell account in the USA (as far as I know Slirp does support telnet connections...though a bit fussy about it) in combination with a cheap shell account from VSNL (local ISP in India), a TCP/IP acc could be simulated. A bit slow but definitely worth the price ($10 for 500 hours..compared to a lot more for a TCP/IP )
Two things to note... A service called SenseNET used to provide something like this. Don't know if they used SLiRP/TiA or something else. Plus VSNL (and some other ISPs) do not provide clean 8 bit telnets (or I simply did not experiment enough with it). People might need to fiddle around with that.
It's simple.... Some of you are saying that use of this is dead. I can log onto a computer right now that probably has 30-40 slirp sessions running on it. College students are poor, or arn't allowed to get a cable/dsl modem in the doors/apartments they live in. And with some universities allowing free dialup servers like the one I goto, it is a valid solution. Granted its not gonna smoke but for the casual user that can always walk to a computer lab to do anything real, it works fine.
Is it a valid solution for most people no, mainly because we want to do more than look at a couple of simple web pages and reply to e-mails. I know now that I have a cable modem I couldn't ever go back to dialup. But for those that don't have the option slirp is a valid solution.
Why not just set up a simple proxy application to do the same thing? Then set netscape to point to your proxy port on that remote machine and browse their internal intranet. :-)
I use something like this already except my ISP calls it
a dynamic-shell account. I dial in and connect like any
other user but then I'm able to telnet to the server.
I find it extremely useful. I can check news and e-mail
before downloading it and trash any unwanted messages.
In addition, I can set up procmail filters if I ever
really need to. I can also edit my html on the server
rather than having to ftp any changes. All this and
no additional charge per month.
On the downside of this is that you now have another
account that can be cracked. Though this isn't too
bad because my ISP knows what its doing when it comes
to security.
I definitely have to say that I'm glad I have my
account.
Sol
OK how does one tell if kimchi IS spoiled?
--
When she told me I was average, she was just being mean.
TIA was pay software, with several license models. My ISP actually paid $$$ for a TIA site license before SLiRP came out, right about the time that the TIA license cracker was becoming popular :-) One of my friends from IIT (Hey Mike, you out there?) was one of the main tech support guys for TIA out in California. It was a good product, killed by a free product. Dave (formerly of Ripco, Chicago's least ethical ISP.)
Back when PPP accounts were expensive GA Tech signed some ridiculous contract with a service provider (MCI, I think) such that PPP would be provided to students for a small fee + per minute charges over some fixed amount of time.
That doesn't sound so bad until you get to 1999 where the price of an unlimited access PPP account is lower than the base fee with that ISP. The problem is that you can't just get by with any old ISP's account since there are a lot of servers and databases here which lock out users based on IP address.(Lexis/Nexis in particular).
SLiRP to the rescue! Although the contract prevents GA Tech from setting up a competing PPP dialin service, it's perfectly fine for them to provide a free TTY dialin line, which they've done. Now, thanks to the magic of SLiRP, I not only have unlimited PPP access from within the gatech.edu domain, but I don't even have to pay the slimy ISP's per minute fees.
--Ben
In 5 years, I never noticed any problems with SLiRP. Many thanks to the creator(s).
Bravery, Kindness, Clarity, Honesty, Compassion, Generosity
...Nothing interesting here. Just move along...
SLiRP works over X.25 packet nets (eg Tymnet), which are still in wide use. Does PPP? (I dunno).
I've routinely used this to access the 'net -- local dialup to Tymnet or equivalent, X.25 connection to my "ISP" (not its primary role, but it offers a SLiRP connection) across the country, and then IP from there.
Still some life in the old software yet, I think.
-- Alastair
Some of you might be surprised to learn that "the first public dialup Internet Service Provider" (Software Tool & Die of Brookline, Massachusetts: world.std.com) was *still* asking its customers to use SLiRP for IP access, apparently as recently as June of 1999! So there are probably hundreds of SLiRP users (at least) in the Greater Boston area. As of June 2, 1999 they're now apparently (finally!) supporting direct PPP access (in addition to their traditional dial-up accounts, presumeably).
Way to go, ST&D! --except that this has taken so long I'm now about to order a cable modem. From _another_ ISP... Oh well.
US West is a *fine* ISP, and the connection I see at my friend's place in Minneapolis is great, but the $18 is only good if you're willing to buy a $15/mo. phone package to get a few bucks knocked off the price of their ISP service. If you sign up from their website, they don't explain that you can get Internet access from an ISP other than USWEST.NET.
* The Minneapolis/St. Paul area has a simplex cable system, so uploads must be done via modem if you have cable, which gives DSL a (regional) advantage.
* DSL gives you several more choices. You can use the local Bell or at least one certified CLEC such as Covad. There are tons of ISP's also waiting for independent thinkers to use their services.
* It may not (always) be as fast or cheap to use 256k DSL, you can get some added value, like a static IP, or a subnet of 8 IP's at a reasonable rate (not $10/ea., more like $20 for eight.). The package that seems most interesting is $25/mo. with a static IP, 20 hours of dialup when I'm away from home, and two email addresses. The rates for addon packages are much more reasonable.
* The "snoop" policies that the @Home network was going to implement/did implement are just plain uncool -- it's not ISP's business to see what websites I'm visiting, especially if I can't opt out. If you don't have @Home cable, then you're probably using RoadRunner (Time Warner) or MediaOne(formerly US West), but where's your choice?
The ring/star topology arguments are bunk, of course... I've never seen bottlenecks related to anything other than the backbone of your ISP, even though peak hours slow down cable at two points instead of one.
If you can get cable, and they offer the kinds of features you want, go ahead and get it -- if you need a better set of features, you'll find them on DSL.
--
E2 IN2 IE?
Twas a few weeks ago at work, whence I was determining how to solve a raft of remote access problems. Nothing was working, deadlines were coming...and then I remembered SLiRP. Oh my.
SLiRP is alot more valuable than you might think. For one thing, it provides a user-level NAT'd IP connection over any terminal link. Note, not just a modem link, but *anything*. Combined with SSH, SLiRP makes for an insanely slick VPN routable link that just *works*.
Even for dialup lines, SLiRP rocks. *Absolutely* no administrative headache getting an IP range in which to run PPP. No headaches at all.
I think you need to try to get ASPPP to work on Solaris to truly understand how painful PPP can be. Even pppd isn't too nice on Solaris. But slirp? Thunk. Work. First try.
I'm not just blowing smoke. At my work, there's a semi-decent chance we'll be deploying SLiRP *all over the place*, at *huge* companies, very soon, for precisely these reasons. It's fast, it's free, and it's astoundingly functional.
My shock at seeing my recently rediscovered PPP app of old up on Slashdot again is quite unnerving, but I can't complain. SLiRP has done me well.
One thing I'd request, if anybody's working on adding features--could somebody port in the MS-DNS code? I'm eventually going to be doing *alot* of GPL work involving SLiRP, but my stuff will end up much more high level.
Yours Truly,
Dan Kaminsky
DoxPara Research
http://www.doxpara.com
Once you pull the pin, Mr. Grenade is no longer your friend.
I have a couple of guest shell accounts at the university where, as a college student, I worked at the computer center and CS dept. This university has a terrific library with some online databases that my present institution doesn't have. Access to these databases is via HTTP and restricted to IP addresses within the university.
So, what do I do?
Using ssh, I slirp up a secure ppp connection to my guest shell account. In fact I have my gateway machine (cable modem/masquerade/10-100 bridge) at home establish and maintain this connection (over my cable modem) automatically. Sort of like a poor man's vpn. It's all seamless. Packets destined for the library and a few other machines at that university always get routed over the slirp connection, which is reestablished if it's down. (This isn't surreptitious, btw.; the folks who let me have my guest account know and don't have a problem with it, so the connection is up almost always anyway -- no pesky delay when I connect to those cuspy online databases...)
I use the same trick to access resources at my graduate institution and even at my current (postdoctoral) institution (which of course doesn't recognize my cable modem address). But I don't need slirp in those cases, since I have root access to linux boxes at both places; I simply set up masquerading for my host. Same principle, though.
slirp works for me, in the limited application I have for it....
Which is a bit less.
I remember my 110/300 baud modem. And how I envied those spoiled college kids with their 1200 baud modems.
Will in Seattle
I remember the frigid winter in Seoul, Korea 1995. I had two bottles of soju, a 14.4k modem, lynx, a broken heater, a bowl of rice, some spoiled kimchi, then by some miracle link I discovered Slirp. It saved my life back then. Nobody was around to call for help. I was drinking heavily. None of the ISP staff spoke English and they barely knew how to run their HP machine. It is magical when your connection hangs by a thread.
Gosh, those were the days. Slirp, Navigator 2.0, Windows 3.1, my 486DX-66, and a 14.4k modem. Oh baby. Slirp was an awesome tool in the pre-ppp days, but is there even an isp out there now that doesn't offer PPP? slirp was a tool created just for getting around shell accounts. I can't think of any use for it now. It is a cool hack, so a copy should certainly be preserved, but I see no reason to keep it up to date.
There's no mystical energy field that controls my destiny. It's all a lot of simple tricks and nonsense.
those were equally great days for me. i was in high school, using slirp to turn my (free, of course) unix shell account into a full-fledged slip account, staying up until 4am (ah, that magic hour!) hacking away on LPMOO inheritance code or whatever it was i was doing at the time. that, my friend, was the proverbial day.
I have a lot of history with Slirp. I remember just having a lowly Unix account at the local university, and building Slirp so I could finally use that Netscape thingy. It was the first program I ever compiled.
Yeah those were the days.
---------------
---------------
Do not discount the fact that you have free will.
Is there any way to encapsulate SLiRP(and PPPD) within a 7 bit channel? I tried something along the lines of uudecode | slirp | uuencode, but it (obviously) didn't function as desired.
Suggestions? I have a feeling a standard 7 bit stdin/stdout wrapper might be useful all over the place.
Yours Truly,
Dan Kaminsky
DoxPara Research
http://www.doxpara.com
Once you pull the pin, Mr. Grenade is no longer your friend.
Back when my alma mater started charging $10 a month for PPP service, and simultaneously changed the shell to a 7-bit service. They quietly avoided the subject when asked if they changed it to break SLiRP.
J.
damned vulpine http://sb.drtwister.com/
http://www.phoneboy.com/slirp/, which is useful for those who are trying to run SLiRP with a Mac. Granted, I haven't added anything to this page in quite a while, but I keep it up there for people that need it. I still get an email or two about it every so often and, at least in the past month, the page got ~900 hits.
I was going to write a page for Win9x a while ago, but it's one of those things that seemed to use relevance once PPP accounts were plentiful and shell accounts were few. It's really nice to see that people are still using it.
-- PhoneBoy
The views expressed herein are not necessarily those of anyone, including the poster.
Can you give me more info on how you set this up? I'm in a similar situation: my university does IP checking for it's news server and I need to access university newsgroups. Ever since I got DSL, I've had to use my shell on a university account. This sounds like it's just what i need!
If you can, can you email me too? jyc2@uclink4.berkeley.edu
I would have thought it was preserved there.
Besides, a few years back, I looked into it...and heard that every ISP person I knew of would defenestrate you if you used it, since it apparently *ate* system cycles and resources.
I did find something I thought was better...and won an award from PC Mag in 95 or 96 - SLIPKnot,
which was a WinDoze-based graphical interface to lynx, that used that, and zmodem, to work the same as any other graphical web browser, from a shell account.
mark
I used SLiRP to get a SLIP connection to home back in 1992-93 or something. (Dialled up to a shell with my 2400bps modem..) I can still remember the feeling of using all TCP/IP software home without the hassles of first downloading files to my account and then downloading them home with Ymodem etc..
Nowadays I have a cable modem at home and I hook up my old computers as terminals to the serial ports of my NetBSD box. It's still the easiest way of networking old boxes with only a parallel or serial cable.
230Kbps is still fast enough for most 'surfing' if some friends visit and wants to be on-line the same time as I am.
I think SLiRP is quite useful for many others too who want to utilize their old boxes without spending more time (and money) on hubs, cables and ethernet cards and configuring interfaces than the old boxes are worth.
Con:
For modem dial-up, it's pretty simple to use RFC1918 addresses and IP Masquerade. Last time I used it, it didn't support a lot of things (ICMP, typical reverse-connection stuff like DCC send). You lose some performance running over 7-bit ascii transports.
Pro:
There's some pretty good NAT code out there now. It outght to be possible to borrow some of that to fix some protocols that don't work. It's nice sometimes nice to pic up you connection from a machine you're not directly dialed into. As mentioned in other replies, one can combine this with SSH to make a handy VPN. It appears to be less platform specific, so is easier to port.
wow... :) Those were the days... hacking 'till 4am to get the load-balancing code to work (I only had one modem and my tester, whom I talked to on IRC (hey Ducati916!) lived in Salt Lake City), getting tons of email every day (got up to around 80-100 per day at one stage), job offers, etc. etc. Some great memories. Gosh I'm a nerd. :)
:)
It's good to see it still being used... please do email me if you have any questions on the code or anything... I wish I had the time to keep maintaining it.
Let me just clear one thing up: I see "isn't interested in maintaining it..." everywhere, which is false... I did have a 1.1 release scheduled as the "final" release with some bugfixes and some cool new functions, but I lost them in a HD crash. Then I entered the RealWorld. etc. etc.
Ahh, memories... Thanks for brightening up my (really shitty up to now) day...
Danny Gasparovski
dgs@ficsgrp.com
Just a small note (it's been awhile) - but as I recall, you could set up a mask so that SLiRP would work properly over a connection that was not 8-bit clean. I don't remember the parameter off the top of my head but it isn't difficult.
SEAL
---
Spammed? Click here for free slack on how to fight it!
--
# Canmephians for a better Linux Kernel
$Stalag99{"URL"}="http://stalag99.net";
I nearly pulled off a hack once, but could never get it to work fully. Had/have a freenet acct w/ no shell. However, it has lynx, and thus, I used lynx to telnet/rlogin into my remote shell, and run slirp from there. Wrote a script in Commo (speaking of old software!) to automate it all.
I managed to get it to work, partially -- I could access things via IP, but not DNS, and still couldn't get it to work after rtfm.
Incidentally, unless I missed it, I don't think I've heard anyone mention the fact that you could do load-balancing with SLiRP, if you ran it across two modems. I always thought that was damn cool, even if I never had the chance to test it out.