From: Sam M. <pa...@gm...> - 2005-06-28 13:44:53
|
I have something like that set up, except its not the wider internet, just my company LAN. Basically I set mine up in bridged mode (Windows XP Pro) so that it became a part of my local network, as if it was directly connected. This method makes port forwarding much easier. If you have NAT'd it, you would be best off (IMHO) using port forwarding on your Windows box to get it from there. The best option (again IMHO) is to set it up with a bridged mode connection, as it makes it look like its directly connected to your network segment like a normal physical server. Sam On 6/28/05, Jeff Wigal <je...@wi...> wrote: > Hi-- >=20 > I am trying to configure coLinux so that, when it is running, it is > accessible to others from the Internet. My host PC is connected to a > LinkSys wireless router via ethernet cable. >=20 > I have successfully set up the NAT-method of networking coLinux, so when = I > run coLinux, coLinux has access to my local network and to the Internet. > However, I'd like to run a web server or a MySQL server that is accessibl= e > outside of the host PC. >=20 > Here's how I have this set up: >=20 > * Wireless router 192.168.1.1 > * Host PC address: 192.168.1.51 > * Connection "TAP_Connection" 192.168.0.1 > * "Local Area Connection" (192.168.1.51 fixed IP address, my Ethernet car= d > on host PC) is setup to share it's internet connection with TAP_Connectio= n. >=20 >=20 > ----------------------- > /etc/network/interfaces > ----------------------- >=20 > auto lo eth0 > iface eth0 inet static > address 192.168.1.52 > gateway 192.168.0.1 > netmask 255.255.255.0 >=20 > iface lo inet loopback >=20 > --------------------------------- > /etc/profile (lines added at top) > --------------------------------- >=20 > ifconfig eth0 192.168.1.52 && route add default gw 192.168.0.1 > pump -i eth0 >=20 > ---------------- > /etc/resolv.conf > ---------------- >=20 > search mshome.net > nameserver 192.168.0.1 >=20 > I would like to set up coLinux so that, when it runs, it appears on the > network as 192.168.1.52. I am assuming that, once I have this, I can set= up > my router so that it forwards certain port requests to 192.168.1.52, to > coLinux. >=20 > If I have to set it up another way to accomplish the same end (e.g. be ab= le > to set my router to forward certain ports to colinux) that's fine with me= . >=20 > Thanks in advance-- >=20 > -Jeff Wigal >=20 >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic= k > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |