From: <Mic...@un...> - 2005-01-20 21:18:44
|
Dear Ian, Thanks! It sound pretty much like its what I need (though port listening would be nice) It pretty much serves my purpose as I was going to make an OpenVPN tunnel anyway... Cheers, Michael > -----Original Message----- > From: Ian Bonnycastle [mailto:ib...@gm...] > Sent: 20. januar 2005 15:12 > To: Sam Moffatt > Cc: Michael Grønager; col...@li... > Subject: Re: [coLinux-devel] Network forwarding... > > > Actually, come to think of it, the SLiRP setup does ALMOST what you > want. Its an outgoing (AFAIK) connection only, and it requires no > installed software (PCAP/TAP). I THINK it allows for incoming > connections via port forwarding, but again, you'll have to set up a > piece of software to open those ports automatically. I know what > you're saying, though... you want the application on Linux to act like > its an application on the Windows box, where it just listens for > ports, and thats it. You'd probably have more success (as of right > now) running the application out of Cygwin than out of a coLinux box > to do what you want to do. I'm not advocating Cygwin as a solution to > coLinux, but I'm saying in this particular situation, it would do what > you specially want to do better, most likely. > > Ian > > On Thu, 20 Jan 2005 21:00:17 +1000, Sam Moffatt <pa...@gm...> wrote: > > from memory, this sort of idea has been discussed, its just the > > implementation that is a bit tricky. afaik previously it was suggested > > that colinux might try to interface directly with the hardware (add a > > hook somewhere), but this gets complicated. > > > > one option you might want to look at is running a socks server on the > > windows box and hooking up dante with colinux. dante > > (http://www.inet.no/dante/) uses dynamically loadable modules to hook > > into the network functions and make them run through a socks server. > > this means that any network application become socks capable. can't > > remember the details, but that may also be a solution for your problem > > as it uses the host system of the socks server to control the ports > > > > On Thu, 20 Jan 2005 10:03:07 +0100, Michael Grønager > > <Mic...@un...> wrote: > > > Hi Sam and Jok, > > > > > > Thanks for your replies - I do agree that it has to be done with a new > > > driver, > > > however, it would add a very nice default networking option > > > just parasiting on the windows box as an application. Super > easy to setup, > > > no need for extra installs (TAP/PCAP) and probably enough for most > > > installs(?). The question is more where to begin? > > > Some of the drawbacks with NAT and Bridged is that you have > to set it up, > > > and I am looking for something more self configurating. > Though, I can see > > > that I would get the same functionality with NAT and port > forwarding - I'll > > > checkout webcat. > > > > > > Cheers, > > > > > > Michael > > > > > > > -----Original Message----- > > > > From: Sam Moffatt [mailto:pa...@gm...] > > > > Sent: 20. januar 2005 05:56 > > > > To: Michael Grønager > > > > Cc: col...@li... > > > > Subject: Re: [coLinux-devel] Network forwarding... > > > > > > > > > > > > A network bridge does exactly this, connects it to the same > segment so > > > > that it appears to be just another computer on the network. not the > > > > same ip as the windows box, but it 'appears' to be on the same > > > > network. just tell colinux the ip and netmask it needs, set up a > > > > bridge between the two lan connections under windows and > the rest will > > > > work for itself > > > > > > > > the routing and remote access service does a similar thing in a more > > > > complicated way, but thats 2k3 only (or perhaps 2k, but i haven't > > > > needed to it on there) > > > > > > > > of course port forwarding will also work > > > > > > > > hope this helps, > > > > > > > > Sam > > > > > > > > On Wed, 19 Jan 2005 22:57:01 +0100 (CET), Michael Grønager > > > > <mic...@un...> wrote: > > > > > Hi, > > > > > > > > > > I am currently using coLinux as a means to provide Linux > > > > compute ressources > > > > > to NorduGRID (one of the biggest production GRIDs). > > > > > > > > > > My current setup uses the bridged network interface and > > > > WinPCAP, however, > > > > > a much better solution (and probably also simpler to make > and support), > > > > > would be for coLinux to use the same network address as the > > > > windows box it > > > > > is sitting on and behave as an ordinary application - > i.e. just grap the > > > > > ports it needs - this means of course that we cannot have > a sshd running > > > > > on windows and linux at the same time (at least not on > the same port). > > > > > However, I guess that this would rarely be a problem (unless > > > > you are using > > > > > several VMs on the same windows box.). > > > > > I browsed through the coLinux code quickly, but I have > not been able to > > > > > pinpoint where and how I could add this new network device - > > > > hints anyone,or anyone that is doing this already? > > > > > > > > > > Cheers > > > > > > > > > > PS: I cannot just use TAP/NAT as I need the coLinux VM to > be visible on > > > > > the same net as the windows machine is on... > > > > > Michael Gronager > > > > > > > > > > -- > > > > > Michael Gronager, PhD > > > > > Research and Developement, VR-C > > > > > UNI-C > > > > > DTU Build. 304 > > > > > 2800 Lyngby > > > > > DENMARK > > > > > > > > > > Phone: +45 35878889 > > > > > Fax: +45 35878990 > > > > > Direct: +45 35878966 > > > > > Mobile: +45 24248207 > > > > > Email: mp...@un... > > > > > > > > > > ------------------------------------------------------- > > > > > This SF.Net email is sponsored by: IntelliVIEW -- > Interactive Reporting > > > > > Tool for open source databases. Create drag-&-drop > reports. Save time > > > > > by over 75%! Publish reports on the web. Export to DOC, > XLS, RTF, etc. > > > > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > > > > > _______________________________________________ > > > > > coLinux-devel mailing list > > > > > coL...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > -- > > > > No virus found in this incoming message. > > > > Checked by AVG Anti-Virus. > > > > Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: > 19-01-2005 > > > > > > > -- > > > No virus found in this outgoing message. > > > Checked by AVG Anti-Virus. > > > Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19-01-2005 > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive > Reporting > > > Tool for open source databases. Create drag-&-drop reports. Save time > > > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > > Tool for open source databases. Create drag-&-drop reports. Save time > > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19-01-2005 > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19-01-2005 |