From: alessandro-email.it <wi...@em...> - 2006-04-23 10:17:45
|
>wiki.colinux.org/cgi-bin/Network?highlight=%28slirp%29#head-45b3ecf09a831ae18ab8d4e7b153bc6f212d6ed4 i'm looking bridged network and now i see a interesting thing .... "The problems with this aproach is that it requires an existing network connection and may not work when you connect directly to your ISP, as they may refuse multiple IPs in the same /line/ ." mmm it could be this my problem... but i don't understand a thing ! in this way i obtain a network between my colinux and may winXP but colinux can't go in internet... so .. "This can be solved by installing the Microsoft Loopback Driver and using it, but then it would be the same as the TAP driver" perfect... but ... what's Microsoft Loopback Driver ??? (is for local traffic ?? ) how i can istall this driver ? :-) thanks thanks thanks alessandro |
From: Matthias D. <md...@zi...> - 2006-04-23 10:36:22
|
Am Sonntag 23 April 2006 12:17 schrieb alessandro-email.it: > but i don't understand a thing ! in this way i obtain a network between > my colinux and may winXP but colinux can't go in internet... > so .. It's quite easy. If your Windows box is _directly_ connected to an ISP, use NAT. Otherwise your ISP may be confused when you try to use more than one IP address in order to connect to the Internet. If your box is within a LAN, use a bridged network. It's way more flexible. -- Matthias Dressler |
From: alessandro-email.it <wi...@em...> - 2006-04-23 13:38:50
|
Matthias Dressler ha scritto: >Am Sonntag 23 April 2006 12:17 schrieb alessandro-email.it: > > > >>but i don't understand a thing ! in this way i obtain a network between >>my colinux and may winXP but colinux can't go in internet... >>so .. >> >> > >It's quite easy. If your Windows box is _directly_ connected to an ISP, use >NAT. Otherwise your ISP may be confused when you try to use more than one IP >address in order to connect to the Internet. >If your box is within a LAN, use a bridged network. It's way more flexible. > > > you're emphasized DIRECTLY... i have a DSL 4 MB connection with a italian provider this is a directly connection ? mmm... ------------ so who use bridge ? when is necessary use bridge ? and SLIRP ? slirp : "As there is no NAT support, you can't connect from outside of CoLinux <http://wiki.colinux.org/cgi-bin/CoLinux>, but you can use colinux to connect outside It is much slower than the other ways, because everything happens in "user mode", but can be sufficient for most uses, and it has the benefit of being easy to deploy (no driver to install and the colinux instance can be configured as a DHCP client)." so now i think that NAT is the only real way for a good network. (i want use some server on colinux like apache postgress and so on) now i try nat.. i hope well alessandro |
From: Matthias D. <md...@zi...> - 2006-04-23 14:53:54
|
Am Sonntag 23 April 2006 15:38 schrieb alessandro-email.it: > i have a DSL 4 MB connection with a italian provider Speed does not matter :) Use NAT. That will work definitely. Some report bridging also does work when directly connected but I doubt this will work flawlessly, though I have not tried that yet. -- Matthias Dressler |
From: Eric S. J. <es...@ha...> - 2006-04-23 15:58:47
|
Matthias Dressler wrote: > Am Sonntag 23 April 2006 15:38 schrieb alessandro-email.it: > >> i have a DSL 4 MB connection with a italian provider > > Speed does not matter :) nor does the size of your pipe... > Use NAT. That will work definitely. Some report bridging also does work when > directly connected but I doubt this will work flawlessly, though I have not > tried that yet. bridging works very well on the LAN and is my preferred method of connecting my colinux instance to a network. But no matter what you have for an Internet connection, independent of any size or speed, never run a machine naked on the net. Always use some form of hardware protection that sits between your machine and the Internet. It's cheap, it's easy, and is one of the simple steps of safe computing. ---eric |
From: George P B. <geo...@gm...> - 2006-04-27 03:03:54
|
On 4/23/06, alessandro-email.it <wi...@em...> wrote: > so who use bridge ? when is necessary use bridge ? > and SLIRP ? > slirp : "As there is no NAT support, you can't connect from outside of > CoLinux <http://wiki.colinux.org/cgi-bin/CoLinux>, but you can use > colinux to connect outside > It is much slower than the other ways, because everything happens in > "user mode", but can be sufficient for most uses, and it has the benefit > of being easy to deploy (no driver to install and the colinux instance > can be configured as a DHCP client)." This is a bit dated... Probably at the time this was written SLiRP in the stable or devel didn't support connections comming in. Current stable and devel version of SLiRP allow port-redirection which allows you to have ports on the host 'redirected' to coLinux, so running SSH in coLinux, but accepting SSH connection from anyways is possible with SLiRP (contrived example, obviously) As for the comment above about speed... It's getting better, it's still probably not as good as some of the others, but it's getting better. -- George |
From: Jason A. <ja...@co...> - 2006-04-23 17:06:16
|
The problem, if I understand right, is you have a single windows box connected directly to the internet. I hope you have a good firewall ;) In this scenario, you need to make Windows be your router for your coLinux boot. I's not ideal but what I did (with XP) when having only a single system and no router to work with was use Internet Connection Sharing. I say it's not ideal, but it's probably the best you'll manage without a dedicated router. There are some gotchas with ICS. First and foremost you must use DHCP from the virtual (guest) OS. ICS supports nothing else. Secondly, you have to set up DHCP in your Linux boot to NOT send a hostname with the DHCP request. At least, when I was using it for a brief spat, Windows DHCP would never reply with an IP if the DHCP client went along the hostname. I also can't guarantee how it will behave/work with whatever firewall you are using to protect windows. Jason On Sun, 23 Apr 2006, alessandro-email.it wrote: > > >> wiki.colinux.org/cgi-bin/Network?highlight=%28slirp%29#head-45b3ecf09a831ae18ab8d4e7b153bc6f212d6ed4 > > i'm looking bridged network and now i see a interesting thing .... > > "The problems with this aproach is that it requires an existing network > connection and may not work when you connect directly to your ISP, as they > may refuse multiple IPs in the same /line/ ." > > mmm it could be this my problem... > but i don't understand a thing ! in this way i obtain a network between my > colinux and may winXP but colinux can't go in internet... > so .. > > "This can be solved by installing the Microsoft Loopback Driver and using it, > but then it would be the same as the TAP driver" > > perfect... but ... > what's Microsoft Loopback Driver ??? > (is for local traffic ?? ) > how i can istall this driver ? :-) > > > thanks thanks thanks > > alessandro > > > > > > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: alessandro-email.it <wi...@em...> - 2006-04-25 09:22:45
|
Jason Ahrens ha scritto: > The problem, if I understand right, is you have a single windows box > connected directly to the internet. I hope you have a good firewall ;) my scenario is... a netgear router modem firewall connect to internet a pc and one notebook connect to router (ethernet not wireless) :P |
From: Matthias D. <md...@zi...> - 2006-04-25 09:27:15
|
Am Dienstag 25 April 2006 11:22 schrieb alessandro-email.it: > Jason Ahrens ha scritto: > > The problem, if I understand right, is you have a single windows box > > connected directly to the internet. I hope you have a good firewall ;) > > my scenario is... > a netgear router modem firewall connect to internet > > a pc and one notebook connect to router (ethernet not wireless) This is NOT a direct connection. You probably have a hop between your win box and the ISP. Then use a bridged network :) -- Matthias Dressler |
From: alessandro-email.it <wi...@em...> - 2006-04-25 15:42:51
|
in the meantime i try NAT.. but .. http://wiki.colinux.org/cgi-bin/coLinuxNetworking#head-c455ffdd2de74f38bcb54ed7a5de0735c82e77c4 "Internet Connection Sharing will only work with 192.168.0.1 being the IP address of the Tap device! Make sure that you do not assign a Gateway in the TAP IP settings (As shown above)." asdasdasdasdasdadsa 192.196.0.1 is the address of my router .... and now ?? must return on bridging ?? LoL |
From: Sunil <fu...@ya...> - 2006-04-25 19:30:13
|
you can change that in the router settings thru web interface of the router (to something like 10.3.75.1). I wonder why use ICS if you have a router. "alessandro-email.it" <wi...@em...> wrote: in the meantime i try NAT.. but .. http://wiki.colinux.org/cgi-bin/coLinuxNetworking#head-c455ffdd2de74f38bcb54ed7a5de0735c82e77c4 "Internet Connection Sharing will only work with 192.168.0.1 being the IP address of the Tap device! Make sure that you do not assign a Gateway in the TAP IP settings (As shown above)." asdasdasdasdasdadsa 192.196.0.1 is the address of my router .... and now ?? must return on bridging ?? LoL ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users --------------------------------- Yahoo! Mail goes everywhere you do. Get it on your phone. |
From: alessandro-email.it <wi...@em...> - 2006-04-27 17:46:19
|
alessandro-email.it ha scritto: > Aaron Miller ha scritto: > >> Shouldn't your guest Linux default gateway be 192.168.40.1 ? >> > > ok ok i try with gateway 192.168.40.1 and 192.168.0.1 .... but don't > work :D > (with 602LAN suite) > >> If you can't ping 192.168.40.1 from Windows, something seriously >> weird is going on. If the TAP adapter is enabled and configured to >> that IP address, then you should be able to ping it no matter what. > > > in fact, is this the problem > i do a test... > i return without 602LAN suite > > my router is 192.168.0.1 > other pc is 192.168.0.2 > notebook 192.168.0.3 > tap (on notebook) 192.168.0.4 > > on colinux... (gentoo) i type > > ifconfig lo 192.168.0.4 broadcast 192.168.40.255 netmask 255.255.255.0 up > ifconfig eth0 192.168.0.4 broadcast 192.168.40.255 netmask > 255.255.255.0 up > > route add default gateway 192.168.0.1 > > a question : is correct use for tap and in ifconfig the same ip > 192.168.0.4 ?? > > so now i can ping... > > windoz don't ping 192.168.0.4 > > colinx ping 192.168.0.4 > colinx ping 192.168.0.1 > colinx ping 192.168.0.2... > colinx ping 192.168.0.3... > > but not ping www.google.it > ( yes i edit resolv.conf with my dns :D ) > > and don t ping the ip of google (216.239.37.99 ) > > mmmm > |