From: Saxon F. <ts...@ya...> - 2004-12-22 11:46:58
|
Host NIC(Win2000 192.168.2.40 ICS enabled) HOST TAP(Win2000 192.168.0.1) Colinux eth0(192.168.0.41 gateway 192.168.0.1) It can ping and resolve external domain. I'm trying to make it talk to another PC(nic 192.168.2.30 tap 192.168.0.1 colinux 192.168.0.31). What do I need to make be able to join up the 2 network? thanks. __________________________________ Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com |
From: Holger K. <hol...@gm...> - 2004-12-22 12:25:58
|
> Host NIC(Win2000 192.168.2.40 ICS enabled) > HOST TAP(Win2000 192.168.0.1) > Colinux eth0(192.168.0.41 gateway 192.168.0.1) It can > ping and resolve external domain. > > I'm trying to make it talk to another PC(nic > 192.168.2.30 tap 192.168.0.1 colinux 192.168.0.31). > > What do I need to make be able to join up the 2 > network? Add the routing rules to the colinux and windows systems. But maybe it is easier to setup winpcap and give every colinux a ip-adress in the 192.168.2.x range. |
From: Saxon F. <ts...@ya...> - 2004-12-22 15:30:40
|
hi, --- Holger Krull <hol...@gm...> wrote: > > Host NIC(Win2000 192.168.2.40 ICS enabled) > > HOST TAP(Win2000 192.168.0.1) > > Colinux eth0(192.168.0.41 gateway 192.168.0.1) It > can > > ping and resolve external domain. > > > > I'm trying to make it talk to another PC(nic > > 192.168.2.30 tap 192.168.0.1 colinux > 192.168.0.31). > > > > What do I need to make be able to join up the 2 > > network? > > Add the routing rules to the colinux and windows > systems. > But maybe it is easier to setup winpcap and give > every colinux a ip-adress in the 192.168.2.x range. > installed winpcap 3.1 beta 4(win2000) and pump in colinux but can't get it to work. in default.colinux.xml, what is the "name" refering to? Try the "name" and "device name" in "Network and Dial-up Connections" but still not working. "Local Area Connection 2" is the real nic. "Local Area Connection 4" is the tap device. where did i go wrong? thanks. -------- /etc/network/interface auto lo eth0 eth1 iface eth0 inet static address 192.168.0.40 gateway 192.168.0.1 netmask 255.255.255.0 iface eth1 inet dhcp iface lo inet loopback ---------- default.colinux.xml <network index="0" type="bridged" name="Local Area Connection 4"/> <network index="1" type="bridged" name="Local Area Connection 2/> ---------- /etc/resolv.conf nameserver 192.168.0.1 ---------- __________________________________ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com |
From: Holger K. <hol...@gm...> - 2004-12-23 00:19:51
|
> in default.colinux.xml, what is the "name" refering > to? Try the "name" and "device name" in "Network and > Dial-up Connections" but still not working. > "Local Area Connection 2" is the real nic. > "Local Area Connection 4" is the tap device. My entry is <network index="0" type="bridged" name="LAN-Verbindung" mac="00:ff:39:29:51:50" /> so i believe yours should be <network index="0" type="bridged" name="Local Area Connection 2" /> i need the mac entry to because of my dhcp server. > iface eth0 inet static > address 192.168.0.40 > gateway 192.168.0.1 > netmask 255.255.255.0 > > iface eth1 inet dhcp > > iface lo inet loopback > > ---------- > default.colinux.xml > <network index="0" type="bridged" name="Local Area > Connection 4"/> Don't use the tap device. I have: # The loopback interface auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp # iface eth0 inet static # address 192.168.1.102 # netmask 255.255.255.0 |
From: Saxon F. <ts...@ya...> - 2004-12-23 04:51:16
|
Try adding my nic mac to default.colinux.xml but still not working. Is there any setting for winpcap? starting colinux "colinux-daemon.exe -t nt -c default.colinux.xml" --- Holger Krull <hol...@gm...> wrote: > > in default.colinux.xml, what is the "name" > refering > > to? Try the "name" and "device name" in "Network > and > > Dial-up Connections" but still not working. > > > "Local Area Connection 2" is the real nic. > > "Local Area Connection 4" is the tap device. > > My entry is > <network index="0" type="bridged" > name="LAN-Verbindung" mac="00:ff:39:29:51:50" /> > > so i believe yours should be > <network index="0" type="bridged" name="Local Area > Connection 2" /> > i need the mac entry to because of my dhcp server. > > > iface eth0 inet static > > address 192.168.0.40 > > gateway 192.168.0.1 > > netmask 255.255.255.0 > > > > iface eth1 inet dhcp > > > > iface lo inet loopback > > > > ---------- > > default.colinux.xml > > <network index="0" type="bridged" name="Local > Area > > Connection 4"/> > > Don't use the tap device. > > I have: > # The loopback interface > auto lo > iface lo inet loopback > > auto eth0 > iface eth0 inet dhcp > # iface eth0 inet static > # address 192.168.1.102 > # netmask 255.255.255.0 > __________________________________ Do you Yahoo!? Dress up your holiday email, Hollywood style. Learn more. http://celebrity.mail.yahoo.com |
From: Sarah T. <sar...@ya...> - 2004-12-28 17:12:29
|
Saxon FJELDSTED wrote: > Host NIC(Win2000 192.168.2.40 ICS enabled) > HOST TAP(Win2000 192.168.0.1) > Colinux eth0(192.168.0.41 gateway 192.168.0.1) It can > ping and resolve external domain. > > I'm trying to make it talk to another PC(nic > 192.168.2.30 tap 192.168.0.1 colinux 192.168.0.31). > > What do I need to make be able to join up the 2 > network? > > thanks. > > > > __________________________________ > Do you Yahoo!? > Send holiday email and support a worthy cause. Do good. > http://celebrity.mail.yahoo.com > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ You need administrator priviledge to run coLinux networking! Before 0.62, it does not need administrator priviledge. Perhaps the 'tap' programmers should take second look what has changed. |