wilcal
08-06-2002, 12:18 PM
1ea Win98 box and 1ea Linux Mandrake 8.2 box
SBC ADSL 128/1500 Fixed IP service, VisionNet ADSL modem
NetGear RP614 DSL Router
First what I did is make sure that both boxes could talk
to the VisionNet ADSL modem directly.
The Win98 box was easy and set up quickly.
After unsuccessfully fooling around with Linuxconfg GUI
I used the following code to connect the Linux Box:
root# ifconfig eth0 65.xxx.xx.xx up netmask 255.255.255.0
root# route add default gw 65.xxx.xx.x dev eth0
Using VI, resolv.confg file set to nameserver assigned by SBC
The Linux box then ran fine talking directly to the VisionNet
modem. The Apache HTML server also worked fine and I could
use the FTP function. At this point my "router" was
to unplug the modem RJ45 cable from the Win98 box and plug
it into the Linux box and visa versa. This way I was
absolutely sure that both machines could talk to the
DSL connection via the VisionNet ADSL modem.
I then installed the RP614 router between the two boxes and
the VisionNet modem. Port 1 is the Linux box, port 2 is the
Win98 box. The VisionNet modem was connected to the WAN I/O.
Afer a clean boot I become root and ran the following
command in /ect:
dhcpcd -d -R
-d tell me what you are doing
-R don't screw with my resolv.confg file
The Linux box then got its new IP LAN (192.168.0.2) info
and I was able to set up the router configuration using
Mozilla. That was pretty easy. Once I set up the Router
(about 2 minutes) using Mozilla, I was immediately able
to surf the Internet. Per NetGears adverts it took just
minutes to get this part working.
Back over to the Win98 box I made the appropriate changes
there (from fix'd IP to DHCP) and it was able to set that
up in just a couple of minutes. After a reboot it was
assigned LAN address 192.168.0.3 and I was able to surf
the Internet after a warm boot.
I then went back to the Linux box and changed the router
port that it was on (port 1) to be in the DMZ zone to make
absolutely sure that it was still able to be a web server.
I then went to a remote location and was able to access
the http server using the WAN address. It worked fine.
Note: You cannot access the WAN web server IP address
(65.xxx.xx.xx) from inside the router (LAN). So I had
to go to another location to make sure that it was all
working, and it was. You can access the Linux box web server
from inside the LAN all you want using the DHCP designated
LAN IP address (192.168.0.2), but not the WAN address.
A day later I turned off the DMZ thing and opened
Port 80 (html) & 21 (ftp) to the Linux box, port 1.
And that works fine too.
This process was WAY easier then I thought it was
going to be.
Side note: Running speed checks (up and down) on
both the Win98 and Linux box showed no degradation
of speed performance with the NetGear RP614 in there.
Its like its not there at all. Obviously, if you
try to do a speed check on both machines at the
same time that will have an effect.
SBC ADSL 128/1500 Fixed IP service, VisionNet ADSL modem
NetGear RP614 DSL Router
First what I did is make sure that both boxes could talk
to the VisionNet ADSL modem directly.
The Win98 box was easy and set up quickly.
After unsuccessfully fooling around with Linuxconfg GUI
I used the following code to connect the Linux Box:
root# ifconfig eth0 65.xxx.xx.xx up netmask 255.255.255.0
root# route add default gw 65.xxx.xx.x dev eth0
Using VI, resolv.confg file set to nameserver assigned by SBC
The Linux box then ran fine talking directly to the VisionNet
modem. The Apache HTML server also worked fine and I could
use the FTP function. At this point my "router" was
to unplug the modem RJ45 cable from the Win98 box and plug
it into the Linux box and visa versa. This way I was
absolutely sure that both machines could talk to the
DSL connection via the VisionNet ADSL modem.
I then installed the RP614 router between the two boxes and
the VisionNet modem. Port 1 is the Linux box, port 2 is the
Win98 box. The VisionNet modem was connected to the WAN I/O.
Afer a clean boot I become root and ran the following
command in /ect:
dhcpcd -d -R
-d tell me what you are doing
-R don't screw with my resolv.confg file
The Linux box then got its new IP LAN (192.168.0.2) info
and I was able to set up the router configuration using
Mozilla. That was pretty easy. Once I set up the Router
(about 2 minutes) using Mozilla, I was immediately able
to surf the Internet. Per NetGears adverts it took just
minutes to get this part working.
Back over to the Win98 box I made the appropriate changes
there (from fix'd IP to DHCP) and it was able to set that
up in just a couple of minutes. After a reboot it was
assigned LAN address 192.168.0.3 and I was able to surf
the Internet after a warm boot.
I then went back to the Linux box and changed the router
port that it was on (port 1) to be in the DMZ zone to make
absolutely sure that it was still able to be a web server.
I then went to a remote location and was able to access
the http server using the WAN address. It worked fine.
Note: You cannot access the WAN web server IP address
(65.xxx.xx.xx) from inside the router (LAN). So I had
to go to another location to make sure that it was all
working, and it was. You can access the Linux box web server
from inside the LAN all you want using the DHCP designated
LAN IP address (192.168.0.2), but not the WAN address.
A day later I turned off the DMZ thing and opened
Port 80 (html) & 21 (ftp) to the Linux box, port 1.
And that works fine too.
This process was WAY easier then I thought it was
going to be.
Side note: Running speed checks (up and down) on
both the Win98 and Linux box showed no degradation
of speed performance with the NetGear RP614 in there.
Its like its not there at all. Obviously, if you
try to do a speed check on both machines at the
same time that will have an effect.