![]() |
![]() |
![]() |
||||
Welcome to the GoFuckYourself.com - Adult Webmaster Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact us. |
![]() ![]() |
|
Discuss what's fucking going on, and which programs are best and worst. One-time "program" announcements from "established" webmasters are allowed. |
|
Thread Tools |
![]() |
#1 |
So Fucking Banned
Join Date: Jul 2002
Posts: 193
|
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 |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#2 |
Confirmed User
Join Date: Sep 2002
Posts: 117
|
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. |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#3 | |
Master of Gfy.com
Industry Role:
Join Date: Feb 2002
Posts: 14,887
|
Quote:
Wow thats the most help I've ever seen someone give on GFY, good job Travis ![]() |
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#4 |
Confirmed User
Join Date: May 2002
Location: New York City
Posts: 403
|
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. |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#5 |
Confirmed User
Join Date: Jul 2002
Location: In a house now. Under an overpass if I don't start making money.
Posts: 123
|
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.
__________________
"If it floats, flies or fucks... rent it" <a href="http://www.goodpussygonebad.com" target="_blank"> <img border="0" src="http://www.goodpussygonebad.com/images/site/GPGBLogo_sm.jpg" width="73" height="74"> |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#6 |
Confirmed User
Join Date: Oct 2002
Location: Germany
Posts: 768
|
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.
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#7 |
Confirmed User
Join Date: Sep 2002
Posts: 117
|
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. |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#8 | |
Confirmed User
Join Date: May 2002
Location: New York City
Posts: 403
|
Quote:
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). |
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#9 | |
Confirmed User
Join Date: Feb 2001
Location: The bushes behind your house
Posts: 2,303
|
Quote:
![]() |
|
![]() |
![]() ![]() ![]() ![]() ![]() |