From: David K. <da...@gi...> - 2006-02-16 20:08:42
|
Is it not possible to use slirp on eth0 and a bridged TAP connection on eth1 simultaneously? Whenever I try to configure this in my colinux.default.xml: <network index="0" type="slirp" /> <network index="1" type="tap" name="coLinux LAN TAP Interface" /> Windows reports the TAP interface as "unplugged" :-( I normally run colinux on my laptop with two TAP adapters, one windows-bridged to the wireless adapter, and one with a static IP so that I can access colinux (web, FTP, ssh and even dns!) via the static IP with or without a net connection, and colinux connects to the net using DHCP via eth0, when I get connected to the net at home or work. But I've been having a problem where my DHCP servers keep giving out the same IP to both windows and colinux, so I'd hoped to switch my colinux->eth0->net path to use slirp instead, to bypass this problem. thanks! -dave |
From: * * <ric...@gm...> - 2006-02-21 07:00:14
|
I've got all three network types working simultaneously with 0.7.x eth2=3Dpcap-bridge,Gigabit,40:00:00:00:10:00 eth0=3Dslirp,"",tcp:2222:22 et= h1=3Dtuntap Note use of a "reserved for local assignment" MAC address for the bridge, to get a different DHCP address. On 2/16/06, David Kaufman <da...@gi...> wrote: > Is it not possible to use slirp on eth0 and a bridged TAP connection on > eth1 simultaneously? > > Whenever I try to configure this in my colinux.default.xml: > > <network index=3D"0" type=3D"slirp" /> > <network index=3D"1" type=3D"tap" name=3D"coLinux LAN TAP Interface" = /> > > Windows reports the TAP interface as "unplugged" :-( > > I normally run colinux on my laptop with two TAP adapters, one > windows-bridged to the wireless adapter, and one with a static IP so > that I can access colinux (web, FTP, ssh and even dns!) via the static > IP with or without a net connection, and colinux connects to the net > using DHCP via eth0, when I get connected to the net at home or work. > > But I've been having a problem where my DHCP servers keep giving out the > same IP to both windows and colinux, so I'd hoped to switch my > colinux->eth0->net path to use slirp instead, to bypass this problem. > > thanks! > > -dave > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: David K. <da...@gi...> - 2006-02-22 18:49:27
|
Hi asterisk-space-asterisk :-) * * <ric...@gm...> wrote: > > David Kaufman <da...@gi...> wrote: >> Is it not possible to use slirp on eth0 and a bridged TAP connection >> on eth1 simultaneously? >> >> Whenever I try to configure this in my colinux.default.xml: >> >> <network index="0" type="slirp" /> >> <network index="1" type="tap" name="coLinux LAN TAP Interface" /> >> >> Windows reports the TAP interface as "unplugged" :-( > > > I've got all three network types working simultaneously with 0.7.x Thanks (to you and to George), I have finally managed to get sirp and TAP slirping and tapping in unison, now. My problem seems to have stemmed from a dreaded-evil Cisco VPN network client that installed a plethora of interfaces and drivers and networking services that was not cleanly uninstalled after I came to my senses and uninstalled it. > Note use of a "reserved for local assignment" MAC address for the > bridge, to get a different DHCP address. Hey, that's a neat trick! I'll definitely try that out (once I have time to undo all the work I did to get me to *this* point... :-) Do you have any pointers where magic MAC addresses such as this might be documented? Thanks again! -dave |
From: George P B. <geo...@gm...> - 2006-02-22 19:27:57
|
On 2/22/06, David Kaufman <da...@gi...> wrote: > Thanks (to you and to George), I have finally managed to get sirp and > TAP slirping and tapping in unison, now. My problem seems to have > stemmed from a dreaded-evil Cisco VPN network client that installed a > plethora of interfaces and drivers and networking services that was not > cleanly uninstalled after I came to my senses and uninstalled it. Yeah... I've had nasty run-ins with CISCO's VPN client before myself... Glad that you got it working. -- George |