GoFuckYourself.com - Adult Webmaster Forum

GoFuckYourself.com - Adult Webmaster Forum (https://gfy.com/index.php)
-   Fucking Around & Business Discussion (https://gfy.com/forumdisplay.php?f=26)
-   -   networking linux and windows (https://gfy.com/showthread.php?t=82500)

[MistaT] 10-13-2002 09:05 PM

networking linux and windows
 
is it possible to share a windows internet connection with mandrake linux?

please post a linux to a tutorial or explain

thanks

travis 10-13-2002 09:21 PM

yes, you do it the same way as an all windows network.

you need to create a proxy server on one of the machines, i would suggest doing this on the linux box but since you specifically requested the windows box you can do it there.

you're going to create an internal intranet with non-internet ip addresses for your network. for example 90.0.0.*

you'll make your linux box 90.0.0.2 and your windows machine 90.0.0.1.

on the linux box you're going to set the gateway ip address to 90.0.0.1 (the windows machine).

now, in order to do this you're going to have to either have two network cards on the windows machine or a network device for your internet that does not require a network card, such as a USB dsl modem.

if your DSL uses a NIC to connect to your computer, you'll need another card. one of them will be internet (90.0.0.1) and one will be external (your dsl ip).

XP has made it very easy to setup a windows proxy server for home network and can guide you though the process very easily. If you don't use XP let me know and i can give you the full details for whatever you currently run.

hope this helps. let me know if you have any questions.

Pipecrew 10-13-2002 09:51 PM

Quote:

Originally posted by travis
yes, you do it the same way as an all windows network.

you need to create a proxy server on one of the machines, i would suggest doing this on the linux box but since you specifically requested the windows box you can do it there.

you're going to create an internal intranet with non-internet ip addresses for your network. for example 90.0.0.*

you'll make your linux box 90.0.0.2 and your windows machine 90.0.0.1.

on the linux box you're going to set the gateway ip address to 90.0.0.1 (the windows machine).

now, in order to do this you're going to have to either have two network cards on the windows machine or a network device for your internet that does not require a network card, such as a USB dsl modem.

if your DSL uses a NIC to connect to your computer, you'll need another card. one of them will be internet (90.0.0.1) and one will be external (your dsl ip).

XP has made it very easy to setup a windows proxy server for home network and can guide you though the process very easily. If you don't use XP let me know and i can give you the full details for whatever you currently run.

hope this helps. let me know if you have any questions.


Wow thats the most help I've ever seen someone give on GFY, good job Travis :thumbsup

posh rat in hell 10-14-2002 01:18 AM

An add-on to what travis said...

First off, you should NOT use 90.0.0.x.
That IP Space isn't in use NOW, but that doesn't mean it won't be in the future, and if/when it is, you will have a problem reaching things on that block.

To read more about that issue, check out this url:
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1918.html

In any case, the space you should be using is in the following ranges:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)


Personally, I usually use 192.168.0.1 - 192.168.0.254 with a netmask of 255.255.255.0 - which will be efficient enough for you to have 254 computers on one network (probably much more than you will need), but if you will need more, you could use a netmask like: 255.255.254.0 (192.168.0.1 -> 192.168.1.254) or 255.255.252.0 (192.168.0.1 -> 192.168.3.254).

Also, I recommend using the linux box to share the connection instead of the windows box, as you will have more control with the linux firewall/nat than you will with windows "internet connection sharing", although either way should be robust enough for basic home use.

ReFresh 10-14-2002 01:35 AM

Why not just use a NAT? I mean, they're dirt cheap now, and a hardware firewall to boot. netgear makes one for a little more than you'd pay for the second NIC you'll have to use for the ICS.

Unless you just want to use the 'nix box's firewall, but you made it wound like you wanted to make the windoze box the gateway, whic is the opposite of what I'd do.

andi_germany 10-14-2002 02:30 AM

Routers are cheap nowadays. Just get one that connects to your kind of connection and you will be set. Configure it in Windows and Linux in 5 minutes and you are all set. Requires no networking skills.

travis 10-14-2002 05:51 AM

Yes, i would agree with the 90.0.0.* issue, but it can be use for now, and for a home network it would be fine.

Also, getting a home router is by far the best bet for a home network, i agree.

There's a lot of cheap ones out there, and some that use 10/100 and wireless which can be very cool to incorporate your laptop into your home network.

posh rat in hell 10-14-2002 02:25 PM

Quote:

Originally posted by travis
Yes, i would agree with the 90.0.0.* issue, but it can be use for now, and for a home network it would be fine.

Also, getting a home router is by far the best bet for a home network, i agree.

There's a lot of cheap ones out there, and some that use 10/100 and wireless which can be very cool to incorporate your laptop into your home network.

What is gained out of using 90.0.0.x instead of using the space specifically assigned for private networks?

All you are doing is intentionally setting up something wrong with no benefit at all to doing it the right way.

Also -- If you are going to use windows or a solid state nat router like a netgear, the nat box is probably better always. But there are plenty of things a linux box can do that a nat box would have problems with (like complicated port redirects).

Kat - Fast 10-14-2002 02:41 PM

Quote:

Originally posted by posh rat in hell
An add-on to what travis said...

First off, you should NOT use 90.0.0.x.
That IP Space isn't in use NOW, but that doesn't mean it won't be in the future, and if/when it is, you will have a problem reaching things on that block.

To read more about that issue, check out this url:
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1918.html

In any case, the space you should be using is in the following ranges:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)


Personally, I usually use 192.168.0.1 - 192.168.0.254 with a netmask of 255.255.255.0 - which will be efficient enough for you to have 254 computers on one network (probably much more than you will need), but if you will need more, you could use a netmask like: 255.255.254.0 (192.168.0.1 -> 192.168.1.254) or 255.255.252.0 (192.168.0.1 -> 192.168.3.254).

Also, I recommend using the linux box to share the connection instead of the windows box, as you will have more control with the linux firewall/nat than you will with windows "internet connection sharing", although either way should be robust enough for basic home use.

:thumbsup


All times are GMT -7. The time now is 04:12 AM.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123