If you've got an old PC laying around, you could build yourself a freesco router. I'm using an old P133 with 32 MB RAM, which is overkill. All you really need is a 486 and 8 to 16 MB RAM. I'm using just the motherboard, 2 NICs and a floppy. It can handle port forwarding, which is what you want. You can forward any external port to any port on any machine on your LAN. It connects to my Cable modem without a problem. How well it connects to ADSL, I don't know. You can check out at http://www.freesco.org. HTH, Tim
Previously, Tom Wilson chose to write: > On Friday 25 January 2002 11 23:55 pm, Bruce Marshall's voice rose above > the ones in my head and declared: > > I assume by 'private ip' you really mean a static IP. (it's always the > > same) > > I have a DHCP assigned address although it has been the same one since I > got my DSL a year ago. My assigned IP is a private class A. > 10.xxx.xxx.xxx > > > Sounds like you want the same situation that I have here (static IP, but > > I use a dial-up line) I host a web server and wouldn't *dare* put up > > an ftp server. You'll be over-run with door knockers... > > I was thinking of hosting my own web server and ftp. My IPS provides me > with 10 MB of webspace but I want the experience of setting up my own. And > I have some friends that swap a lot of MP3's of Phish and Grateful Dead > concerts and they mostly do it via ftp. I was gonna put up a non-anonymous > ftp using something other than wu-ftp. > > > In any event all I think you need is masquerading of your internal > > network. All your machines would have local addresses of 192.168.0.xx > > or such and your ADSL connected machine becomes the gateway to the Inet. > > I am going to set up my internal network (192.168.0.xx range) to masq > through my firewall that has my external interface point to the > 10.xxx.xxx.xxx that I have from my ISP. Problem is how do I get incoming > connections routed to a 10.xxx.xxx,xxx private address. > > > Now I have my web server on my inet connected machine. Placing it on > > some other machine in your LAN that isn't directly connected can take > > some work as you will have to forward incoming connections to that > > machine. > > Yes it is. But I am willing to put in the work and have had some previous > help in IP forwarding. It may take awhile but I am willing to give it my > best. > > > But dyndns is the way to go if you can't get your ISP to host your > > domain. > > They will host the domain for me but it all cost more money above and > beyond my current ISP and DSL provide costs. And that is what I want to > avoid is paying more money for stuf I am really just doing for fun right > now. > > Thanks a bunch -- Caldera eWorkstation 3.1, kernel 2.4.9, KDE 2.2.1, Xfree86 4.1.0 _______________________________________________ Linux-users mailing list - http://linux.nf/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
