|
From: C. R. O. <cr...@nc...> - 2004-06-16 17:37:30
|
Blake wrote: > The second way. =20 > <network index=3D"0" type=3D"tap" name=3D"tap"></network> Thanks. OK, I've confirmed that I can bridge my physical enet adapter and the coLinux adapter together and my coLinux install has a working network (at least on my work machine--haven't tried at home yet) and it doesn't seem to conflict with the SecuRemote VPN we have installed here. I have noticed that I can't seem to connect over the VPN from coLinux, but I can do without that. I did have to reboot before anything would work. I think that's because SecuRemote looks at all the network adapters and binds itself to the "right" ones at boot time. I'm guessing that since this is a Windows "native" solution that it will perform better than the coLinux bridge or NAT solution. The coLinux bridge did perform really well, though. --cro |