Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Connect the internet to your Linux machine and use tinyproxy to serve over the network for Internet access in Windows. That way at least your Linux machine can act as a firewall and your Windows machine will be more secure than it is if connected directly to the net.
Last edited by vharishankar; 12-04-2006 at 08:38 AM.
This will NOT be easy without adding hardware. The easiest way is to add a NAT box with a built-in switch (informally often referred to as a "router" although this is technically incorrect). I'm not sure how much they cost in India, but they can be had for ~15-50 USD online.
The next best option is to use Windows Internet connection sharing and add a second NIC to the Windows Box. The NIC would likely cost almost as much as a cheap NAT box/switch.
Barring that, I suppose there is a method to do it using serial,usb,LPT, or firewire, but then you are still having to buy a cable.
OOPS! You already seem to have a switch. Windows ICS should do it all for you. There are a zillion howtos on the web for this, including some very comprehensive instructions buried on the MS website somewhere. Basically Windows ICS will turn the XP box into a NAT box/DHCP server.
I think he already has a working network connection between Windows and Linux... in that case he needn't buy additional hardware (assuming there are 2 nics on the machine connected to the net -- no big deal with modern motherboards which already come with 1 or 2 ethernet ports onboard).
The other thing is that I recommend connecting the internet to Linux and using a proxy server to access the net from Windows.
Last edited by vharishankar; 12-04-2006 at 08:48 AM.
yes harishankar is correct i am having two nics in my amd semperon and so u say it will be safe to do the thing vice-versa that is make my windows xp machine share internet connection through my kubuntu linux box .
but there will be no compromise on speed and performance on doing this thing .
finally i want to know all the possible ways for doing internet sharing from windows xp to kubuntu linux box . i have enabled windows xp to share a lan card for ics through windows xp to kubuntu
yes there are lots of howto for linux-to-windows xp and cannot find a great tutorial for windowsxp-to linux ics
men thanks a lot for the info u provided to me ,it was very useful to me
If you have configured ICS and your firewall in windows then you should be set to go. By default windows will automatically assign its LAN adapter to 192.168.0.1 (The IP address can not be channged) and start a DHCP server. Configure your kubuntu box for DHCP.
You do not have to use DHCP in your linux PC but you might have to change it settings.
Assign your kubuntu PC any address in the 192.168.0.x range where x is not 1, 0, or 255 and netmask 255.255.255.0. 192.168.0.1 will be the IP address of the XP PC and it can not be changed. The gateway IP address will also be 192.168.0.1. If not already accomplished add the DNS information to your /etc/resolv file as assigned to your XP box. The information can be recovered from XP using the
ipconfig /all command in a windows cmd box. You do not need to change any browser settings.
To configure Kubuntru go to "Control Center" and added IP, gateway and dns in "Network Settings" in Administrator mode
Distribution: Proud User Fedora FC5/ Fedora 7 /Ubunt 7.10
I had the same problem . And tried for months !! to get it going without success . I came to Linux Questions to post my solution and this thread was the first thing I saw .
I have 3 computers using Internet Connection Sharing . 1 with XP and others Win98 . Xp does not appear to give many details . Is DHCP being used - there is no indication . It maybe Peer to peer sharing. It would require a lot of investigation to try to duplicate what XP ICS was doing .
Here are my Linux settings - Eth0 connected to DSL modem - 192.168.1.1
Eth1 connected to Lan 192.168.0.1.
DSL modem gets IP from ISP .
I JUST DOWNLOADED FIRESTARTER
AND CLICKED ON INTERNET CONNECTION SHARING .
My internet connection is through a DSL modem which is shown as ppp0 . I selected that too.
It also has an option to start DHCP . And a very very neat and understandable equivalent of IPTABLES.
Just try it it takes much less time .
Yes and do read the PDF Manual .
Your situation is pretty different than gvsrinivasan's. It sounds like you are overdoing it. If the NIC that is connected to the DSL modem is using address 192.168.1.1, then the DSL modem probably has a NAT box in it already. What you are doing is using 2 NAT boxes; the one in your DSL modem and the PC you are using ICS on. If the DSL modem only has one LAN port, you can just uplink that port to a switch and connect your other PC's to the same switch (most NAT boxes also have switches these days, tho). The DSL modem's NAT probably also has a DHCP server built in (most do), so you can set all of the PC's to use DHCP for their addressing. Of course, you can usually disable the NAT box's DHCP server and make any other PC the DHCP server, but that only makes sense in a rare few situations.
Distribution: Proud User Fedora FC5/ Fedora 7 /Ubunt 7.10
If any of this holds for my DSL modem I will be very surprised .
Some instructions did say that I can access the modem . Through the Browser , but I was not able to do it.
I am serious, I did try to get this going for months . And Firestarter did it with one click ...
I think the computer connected to the Internet is configured as a router - does NAT just mean that ?
Basically connects two networks together and allows you to explicitly control the traffic between them. In most cases this means connecting your local network to the internet. Most people (including the marketing flunkies at the companies who make them) mistakenly call NAT boxes "routers". This is technically incorrect, although they do a similar job. If you are supposed to be able to access the DSL modem via a web browser, you most certainly (well, probably) have a NAT box built into it. If you were unsuccessful in doing that, you don't know the correct gateway address to access it.
Firestarter apparently automated the process by detecting the gateway address, assuming this was a WAN (internet) gateway, and used that for the ICS.