12 Apr
2000
12 Apr
'00
6:38 p.m.
Sorry for the partially off-topic question, but I'm stumped.
I'd like to set up more of my systems in a home network environment, but I
don't really properly understand routing and am looking for some help.
My internet access is through a cable modem that acts as a DHCP server,
allocating up to three IP addresses to specifically-named systems. For
instance systems "foo1", "foo2" and "foo3" will get IP
addresses from the
modem, while "foo4", "foo5" and "foo6" will not.
I thought about snagging a small PC with a couple of NICs and running
ShareTheNet or WinGate, but I recently picked up a used Alpha running NT
with a pair of NICs that I'd like to try out as a router. Right now, the
Alpha has one of the magic system names (foo1), so one of the network
adapters gets a DHCP-served IP address. I have the other adapter's IP
address defined as 192.168.0.101, with the mask as 255.255.255.0 and no
gateway defined.
I want to set the following systems up with static IP addresses:
192.168.0.105 SGI Indy
192.168.0.106 Symbolics Lisp Machine
192.168.0.107 NeXT Cube
192.168.0.108 Pentium II Laptop
192.168.0.109 Pentium Desktop
192.168.0.110 DEC Shark
192.168.0.111 iOpener
I'd like to set up these machines to use 192.168.0.102 as their gateway.
Seems to me that if I have the Alpha set up properly, I shouldn't need to do
any special route definitions on the other systems, right?
So, any suggestions on how I should set up the two NICs on the Alpha under
NT 4.0?
-- Tony
12 Apr
12 Apr
7:20 p.m.
Well you have to tell the other systems how to route somehow. For addresses
that don't go the local subnet they need a routing entry. The simplest one
is a "default" route that points to your internet gateway, the next
simplest is to run routed on the gateway and it will broadcast a route to
the internet every 30 seconds or so.
--Chuck
At 10:38 PM 4/12/00 -0500, you wrote:
Sorry for the partially off-topic question, but I'm
stumped.
I'd like to set up more of my systems in a home network environment, but I
don't really properly understand routing and am looking for some help.
My internet access is through a cable modem that acts as a DHCP server,
allocating up to three IP addresses to specifically-named systems. For
instance systems "foo1", "foo2" and "foo3" will get IP
addresses from the
modem, while "foo4", "foo5" and "foo6" will not.
I thought about snagging a small PC with a couple of NICs and running
ShareTheNet or WinGate, but I recently picked up a used Alpha running NT
with a pair of NICs that I'd like to try out as a router. Right now, the
Alpha has one of the magic system names (foo1), so one of the network
adapters gets a DHCP-served IP address. I have the other adapter's IP
address defined as 192.168.0.101, with the mask as 255.255.255.0 and no
gateway defined.
I want to set the following systems up with static IP addresses:
192.168.0.105 SGI Indy
192.168.0.106 Symbolics Lisp Machine
192.168.0.107 NeXT Cube
192.168.0.108 Pentium II Laptop
192.168.0.109 Pentium Desktop
192.168.0.110 DEC Shark
192.168.0.111 iOpener
I'd like to set up these machines to use 192.168.0.102 as their gateway.
Seems to me that if I have the Alpha set up properly, I shouldn't need to do
any special route definitions on the other systems, right?
So, any suggestions on how I should set up the two NICs on the Alpha under
NT 4.0?
-- Tony
7:58 p.m.
It was thus said that the Great Chuck McManis once stated:
Well you have to tell the other systems how to route somehow. For addresses
that don't go the local subnet they need a routing entry. The simplest one
is a "default" route that points to your internet gateway, the next
simplest is to run routed on the gateway and it will broadcast a route to
the internet every 30 seconds or so.
But 192.168.0.0 is defined as a private network and won't be routed on the
Internet. The machines that are in the 192.168.0.0 network will have their
gateway set to the machine with two NICs. Then he'll have to run software
to NAT (Network Address Translation) his internal private addresses to one
of the public addresses. I know it's possible under Linux or FreeBSD but I
don't know about NT.
-spc (And for such a simple network there is no need to run routed unless
he wants to learn how to use routed)
8:36 p.m.
Fair point but I'm guessing if someone had already started using
192.168.x.x addresses then they already know about private addresses. Yes,
you had better NAT those puppies, yes you can do it with Linux, or NetBSD,
or FreeBSD. It would be cooler if you set up a VMS system to do it but hey
there is fun and then there is "fun."
In any event network drivers (even on wimpy DOS boxen) make a choice when
they have a packet to send:
1) Drop it on to the wire (which they do if it is contained in the
subnet
that is defined to be attached to the interface)
2) Drop on the wire encapsulated to a router that claims to know
how to get it off
the subnet and closer to its destination.
The simplest way to do #2 is with a default static route.
--Chuck
At 12:58 AM 4/13/00 -0400, spc wrote:
It was thus said that the Great Chuck McManis once
stated:
Well you have to tell the other systems how to route somehow. For
addresses
that don't go the local subnet they need a
routing entry. The simplest one
is a "default" route that points to your internet gateway, the next
simplest is to run routed on the gateway and it will broadcast a route to
the internet every 30 seconds or so.
But 192.168.0.0 is defined as a private network and won't be routed on the
Internet. The machines that are in the 192.168.0.0 network will have their
gateway set to the machine with two NICs. Then he'll have to run software
to NAT (Network Address Translation) his internal private addresses to one
of the public addresses. I know it's possible under Linux or FreeBSD but I
don't know about NT.
-spc (And for such a simple network there is no need to run routed unless
he wants to learn how to use routed)
13 Apr
13 Apr
9:49 a.m.
gateway set to the machine with two NICs. Then
he'll have to run software
to NAT (Network Address Translation) his internal private addresses to one
of the public addresses. I know it's possible under Linux or FreeBSD but I
don't know about NT.
-spc (And for such a simple network there is no need to run routed unless
he wants to learn how to use routed)
If you want a firewall and to do NAT you should take a look at OpenBSD.
It's not quite as easy to setup NAT on OpenBSD as it is to setup IPmasq on
Linux. However, OpenBSD's main focus is security. It's also possible to
setup NAT on OpenBSD to redirect certain ports to machines inside your
firewall so they can provide certain services.
I've been running OpenBSD on an AlphaStation 200 4/233 for about a year and
a half. Acting just as a Firewall, NAT, Web, and FTP servert the RAM
requirements are nice and light. When I set it up, I'd planned on using
Linux, but found OpenBSD meshed with the hardware I had on hand better and
was more secure.
Still my ideal solution would be to have that AS200 running VMS, but there
seems to be a serious lack of Firewall and NAT software for VMS :^(
Zane
| Zane H. Healy | UNIX Systems Adminstrator |
| healyzh(a)aracnet.com (primary) | Linux Enthusiast |
| healyzh(a)holonet.net (alternate) | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| and Zane's Computer Museum. |
| http://www.aracnet.com/~healyzh/ |
12 Apr
12 Apr
7:54 p.m.
On Wed, Apr 12, 2000 at 10:38:12PM -0500, Eros, Anthony wrote:
I'd like to set up more of my systems in a home
network environment, but I
don't really properly understand routing and am looking for some help.
My internet access is through a cable modem that acts as a DHCP server,
allocating up to three IP addresses to specifically-named systems. For
instance systems "foo1", "foo2" and "foo3" will get IP
addresses from the
modem, while "foo4", "foo5" and "foo6" will not.
I thought about snagging a small PC with a couple of NICs and running
ShareTheNet or WinGate, but I recently picked up a used Alpha running NT
with a pair of NICs that I'd like to try out as a router. Right now, the
Alpha has one of the magic system names (foo1), so one of the network
adapters gets a DHCP-served IP address. I have the other adapter's IP
address defined as 192.168.0.101, with the mask as 255.255.255.0 and no
gateway defined.
I want to set the following systems up with static IP addresses:
192.168.0.105 SGI Indy
192.168.0.106 Symbolics Lisp Machine
192.168.0.107 NeXT Cube
192.168.0.108 Pentium II Laptop
192.168.0.109 Pentium Desktop
192.168.0.110 DEC Shark
192.168.0.111 iOpener
I'd like to set up these machines to use 192.168.0.102 as their gateway.
Seems to me that if I have the Alpha set up properly, I shouldn't need to do
any special route definitions on the other systems, right?
So, any suggestions on how I should set up the two NICs on the Alpha under
NT 4.0?
May be possible with NT but this is screaming for Linux... what you need
is IP masquerading, which will let all the machines hide behind one IP
address, that of the gateway machine. It will let all the machines on the
whole LAN access the Internet, but they won't have real Internet IP
addresses. You could also use the two remaining IP addresses on two
other machines, to expose them directly to the Internet, in case you want
to run services on them. I've been doing this for 4 or 5 years, it
works great. And it's just one excuse among many to get into Linux if
you haven't already... with a NeXT and an Indy evidently you aren't Unix-
phobic, so should have no trouble... There are a couple of good howto's
on the 'net about routing and masquerading respectively. You can install
Linux on the alpha machine or just get another 386 or 486 for that purpose.
--
_______ http://www.bigfoot.com/~ecloud
(_ | |_) ecloud(a)bigfoot.com finger rutledge(a)cx47646-a.phnx1.az.home.com
__) | | \__________________________________________________________________
Get money for spare CPU cycles at http://www.ProcessTree.com/?sponsor=5903
13 Apr
13 Apr
1:21 a.m.
Trivial. I use a Windows 98 box which comes with internet sharing. This was
the old
NAT95 product they acquired from Nevod. It acts as a simple firewall and
DHCP server.
I found an old 266MHz system with a small disk and 64MB of memory,
installed Win98
and enabled the internet sharing. It nicely serves up my six machines and
two network
printers through my cable modem.
I had an NT 4 machine running MS Proxy Server, but that was a very heavy-handed
approach to the problem. At one time, I also tried WinGate but it didn't
work well,
I was always having problems accessing odd port numbers. The Win98 solution
is fast and easy to install. I've never rebooted the server. FWIW.
At 10:38 PM 4/12/2000 -0500, you wrote:
Sorry for the partially off-topic question, but I'm
stumped.
I'd like to set up more of my systems in a home network environment, but I
don't really properly understand routing and am looking for some help.
My internet access is through a cable modem that acts as a DHCP server,
allocating up to three IP addresses to specifically-named systems. For
instance systems "foo1", "foo2" and "foo3" will get IP
addresses from the
modem, while "foo4", "foo5" and "foo6" will not.
I thought about snagging a small PC with a couple of NICs and running
ShareTheNet or WinGate, but I recently picked up a used Alpha running NT
with a pair of NICs that I'd like to try out as a router. Right now, the
Alpha has one of the magic system names (foo1), so one of the network
adapters gets a DHCP-served IP address. I have the other adapter's IP
address defined as 192.168.0.101, with the mask as 255.255.255.0 and no
gateway defined.
I want to set the following systems up with static IP addresses:
192.168.0.105 SGI Indy
192.168.0.106 Symbolics Lisp Machine
192.168.0.107 NeXT Cube
192.168.0.108 Pentium II Laptop
192.168.0.109 Pentium Desktop
192.168.0.110 DEC Shark
192.168.0.111 iOpener
I'd like to set up these machines to use 192.168.0.102 as their gateway.
Seems to me that if I have the Alpha set up properly, I shouldn't need to do
any special route definitions on the other systems, right?
So, any suggestions on how I should set up the two NICs on the Alpha under
NT 4.0?
-- Tony
4:01 a.m.
New subject: OT: Home network routing setup
At 10:38 PM 4/12/00 -0500, you wrote:
I thought about snagging a small PC with a couple of
NICs and running
ShareTheNet or WinGate, but I recently picked up a used Alpha running NT
Speaking of obsolete, obscure and potentially classic WinNT systems,
I've got a rare prototype (circa 1994) Acer MIPS machine on eBay now
at http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=306521190
and the bid is at $10.50. It's got WinNT Server 3.5 and MS VC/MIPS
on the hard drive.
- John
7:04 a.m.
You might want to look into simply upgrading to Win98's Second Edition. I
recall reading that it comes with a gateway program that would allow you to
skip the Wingate or whatever. Check it out for yourself, though, as I'm not
well informed about this detail. If you use Windows, that's an easy
solution. If not, I'd say it involves too much pain.
Dick
----- Original Message -----
From: Eros, Anthony <Anthony.Eros(a)compaq.com>
To: <classiccmp(a)classiccmp.org>
Sent: Wednesday, April 12, 2000 9:38 PM
Subject: Home network routing setup
Sorry for the partially off-topic question, but
I'm stumped.
I'd like to set up more of my systems in a home network environment, but I
don't really properly understand routing and am looking for some help.
My internet access is through a cable modem that acts as a DHCP server,
allocating up to three IP addresses to specifically-named systems. For
instance systems "foo1", "foo2" and "foo3" will get IP
addresses from the
modem, while "foo4", "foo5" and "foo6" will not.
I thought about snagging a small PC with a couple of NICs and running
ShareTheNet or WinGate, but I recently picked up a used Alpha running NT
with a pair of NICs that I'd like to try out as a router. Right now, the
Alpha has one of the magic system names (foo1), so one of the network
adapters gets a DHCP-served IP address. I have the other adapter's IP
address defined as 192.168.0.101, with the mask as 255.255.255.0 and no
gateway defined.
I want to set the following systems up with static IP addresses:
192.168.0.105 SGI Indy
192.168.0.106 Symbolics Lisp Machine
192.168.0.107 NeXT Cube
192.168.0.108 Pentium II Laptop
192.168.0.109 Pentium Desktop
192.168.0.110 DEC Shark
192.168.0.111 iOpener
I'd like to set up these machines to use 192.168.0.102 as their gateway.
Seems to me that if I have the Alpha set up properly, I shouldn't need to
do
any special route definitions on the other systems,
right?
So, any suggestions on how I should set up the two NICs on the Alpha under
NT 4.0?
-- Tony
8:44 a.m.
I use an old 486 with small HD and LINUX to do the dirty routing work
Install Slackware (not to bloated) with ppp, ipchains, maquerading,
wvdial or pppd (if dailup is needed) and the PMfirewall software.
I still have the option to use part of the HD for FTP or SAMBA.
I may even be possible to use a HD-less 486 system. (take the fan out in
the PSU to reduce the noise and without a HD I don't think youll miss it)
see: The linux Router Project
http://www.linuxrouter.org/
or: PicoBSD
http://www.freebsd.org/~picobsd/picobsd.html
Maybe you wan't to use the Alpha for more demanding work
I've heard that lots of companies in the US and Europe have a
surplus of "obsolete" Pentium I and 486 equipment, so it
should be easy to get a few........
----- Original Message -----
From: Eros, Anthony <Anthony.Eros(a)compaq.com>
To: <classiccmp(a)classiccmp.org>
Sent: Thursday, April 13, 2000 5:38 AM
Subject: Home network routing setup
Sorry for the partially off-topic question, but
I'm stumped.
I'd like to set up more of my systems in a home network environment, but I
don't really properly understand routing and am looking for some help.
My internet access is through a cable modem that acts as a DHCP server,
allocating up to three IP addresses to specifically-named systems. For
instance systems "foo1", "foo2" and "foo3" will get IP
addresses from the
modem, while "foo4", "foo5" and "foo6" will not.
I thought about snagging a small PC with a couple of NICs and running
ShareTheNet or WinGate, but I recently picked up a used Alpha running NT
with a pair of NICs that I'd like to try out as a router. Right now, the
Alpha has one of the magic system names (foo1), so one of the network
adapters gets a DHCP-served IP address. I have the other adapter's IP
address defined as 192.168.0.101, with the mask as 255.255.255.0 and no
gateway defined.
I want to set the following systems up with static IP addresses:
192.168.0.105 SGI Indy
192.168.0.106 Symbolics Lisp Machine
192.168.0.107 NeXT Cube
192.168.0.108 Pentium II Laptop
192.168.0.109 Pentium Desktop
192.168.0.110 DEC Shark
192.168.0.111 iOpener
I'd like to set up these machines to use 192.168.0.102 as their gateway.
Seems to me that if I have the Alpha set up properly, I shouldn't need to do
any special route definitions on the other systems, right?
So, any suggestions on how I should set up the two NICs on the Alpha under
NT 4.0?
-- Tony
8900
days inactive
8901
days old
9 comments
9 participants
participants (9)
-
Anthony.Eros＠compaq.com -
cmcmanis＠mcmanis.com -
edick＠idcomm.com -
healyzh＠aracnet.com -
jfoust＠threedee.com -
rutledge＠cx47646-a.phnx1.az.home.com -
sipke＠wxs.nl -
spc＠armigeron.com -
stevemas＠persys.com