Menu
▾
▴
colinux-users
|
From: Lars G. <Lar...@re...> - 2010-08-03 13:56:48
|
Hello everybody, I use colinux 0.78 with the native windows network bridge, it runs fine if I start it from a console. My problem is it to get up the windows service with network support. I can install, start and attach a console to the service. But it is not possible for me, to start the bridged interface (eth2), ifup eth2 prints this: ----------------------------- SIOCSIFADDR: No such device eth2: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth2: ERROR while getting interface flags: No such device Failed to bring up eth2. ----------------------------- In the wiki, I've read something about service dependencies, but this sections seems to e outdated for 0.78 and also does not affect brigdeg network. However I have tried to add Bridge and some other to the service dependencies, without success. Service Dependicies: -------------------- CoLinuxDriver Bridge BridgeMP NPF tap0801co Can someone tell me what is going wrong? Thanks for your support Lars PS: Extract from the config file: ----------------------------- # Slirp for internet connection (outgoing) # Inside running coLinux configure eth0 with this static settings: # ipaddress 10.0.2.15 broadcast 10.0.2.255 netmask 255.255.255.0 # gateway 10.0.2.2 nameserver 10.0.2.3 #eth0=slirp # Tuntap as private network between guest and host on second linux device #eth1=tuntap # brigded networks eth2=ndis-bridge,"tap0" ----------------------------- |
|
From: Henry N. <hen...@ar...> - 2010-08-03 20:05:02
|
Hello Lars, On 03.08.2010 15:43, Lars Grundei wrote: > I use colinux 0.78 with the native windows network bridge, it runs fine if I start it from a console. > My problem is it to get up the windows service with network support. I can install, start and attach a console to the service. > But it is not possible for me, to start the bridged interface (eth2), ifup eth2 prints this: > ----------------------------- > SIOCSIFADDR: No such device > eth2: ERROR while getting interface flags: No such device > SIOCSIFNETMASK: No such device > eth2: ERROR while getting interface flags: No such device > Failed to bring up eth2. > ----------------------------- > > In the wiki, I've read something about service dependencies, but this sections seems to e outdated for 0.78 and also does not affect brigdeg network. However I have tried to add Bridge and some other to the service dependencies, without success. > > Service Dependicies: > -------------------- > CoLinuxDriver > Bridge > BridgeMP > NPF > tap0801co Dependicies tap0801co (TAP-Win32), NPF (PCAP-bridge) you not need, if you not use such network options. They will automatically set, by the colinux-daemon, if they would be configured in your config. Please don't set Bridge and BridgeMP. CoLinux says ndis-bridge, because it works as a bridge. But it's not using any bridge drivers from Windows. And last: "Service Dependicies" means only, that this driver must be started before coLinux can start. So it is more for delayed coLinux start on the Windows boot, not for the manually start. > PS: Extract from the config file: > ----------------------------- > # Slirp for internet connection (outgoing) > #eth0=slirp > > # Tuntap as private network between guest and host on second linux device > #eth1=tuntap > > # brigded networks > eth2=ndis-bridge,"tap0" > ----------------------------- I think, "tap0" is not right there. Or your real network is an openVPN tunnel? Running from command line and as service, will use different Windows user accounts. With different user accounts, you would have different "automatic"-MAC for the eth2. DIfferent MAC your udev inside Linux will rename eth2 to any other eth3, eth3 or what ever. To solve this, please set a unic MAC for the eth2 in the coLinux config. Please read answer #4 in Forum at http://sourceforge.net/projects/colinux/forums/forum/342354/topic/3768555 Or for udev renaming problem please read: http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2 -- Henry N. |
|
From: Lars G. <Lar...@re...> - 2010-08-05 08:38:54
|
Hi Henry, thanks for the support, my problem was depending on the MAC address (thanks again for the good explanation). For others in this situation: I had to deinstall the service (--remove-service) and install it again before it works (I guess this was probably my registry manipulation). Cheers Lars PS: Just for information, "tap0" is correct, I have renamed my network cards in windows: eth0=LAN, tap0=TAP-Win32 and bri0= Windows Bridge. -----Ursprüngliche Nachricht----- Von: Henry Nestler [mailto:hen...@ar...] Gesendet: Dienstag, 3. August 2010 22:05 An: Lars Grundei Cc: 'col...@li...' Betreff: Re: [coLinux-users] Problem with windows service and ndis-bridge Hello Lars, On 03.08.2010 15:43, Lars Grundei wrote: > I use colinux 0.78 with the native windows network bridge, it runs fine if I start it from a console. > My problem is it to get up the windows service with network support. I can install, start and attach a console to the service. > But it is not possible for me, to start the bridged interface (eth2), ifup eth2 prints this: > ----------------------------- > SIOCSIFADDR: No such device > eth2: ERROR while getting interface flags: No such device > SIOCSIFNETMASK: No such device > eth2: ERROR while getting interface flags: No such device > Failed to bring up eth2. > ----------------------------- > > In the wiki, I've read something about service dependencies, but this sections seems to e outdated for 0.78 and also does not affect brigdeg network. However I have tried to add Bridge and some other to the service dependencies, without success. > > Service Dependicies: > -------------------- > CoLinuxDriver > Bridge > BridgeMP > NPF > tap0801co Dependicies tap0801co (TAP-Win32), NPF (PCAP-bridge) you not need, if you not use such network options. They will automatically set, by the colinux-daemon, if they would be configured in your config. Please don't set Bridge and BridgeMP. CoLinux says ndis-bridge, because it works as a bridge. But it's not using any bridge drivers from Windows. And last: "Service Dependicies" means only, that this driver must be started before coLinux can start. So it is more for delayed coLinux start on the Windows boot, not for the manually start. > PS: Extract from the config file: > ----------------------------- > # Slirp for internet connection (outgoing) > #eth0=slirp > > # Tuntap as private network between guest and host on second linux device > #eth1=tuntap > > # brigded networks > eth2=ndis-bridge,"tap0" > ----------------------------- I think, "tap0" is not right there. Or your real network is an openVPN tunnel? Running from command line and as service, will use different Windows user accounts. With different user accounts, you would have different "automatic"-MAC for the eth2. DIfferent MAC your udev inside Linux will rename eth2 to any other eth3, eth3 or what ever. To solve this, please set a unic MAC for the eth2 in the coLinux config. Please read answer #4 in Forum at http://sourceforge.net/projects/colinux/forums/forum/342354/topic/3768555 Or for udev renaming problem please read: http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2 -- Henry N. |
|
From: Henry N. <hen...@ar...> - 2010-08-05 17:47:43
|
Hello Lars,
> eth2=ndis-bridge,"tap0"
I wonder, that you wand to bridge the tap0? The tap0 is the TAP-Win32
and direct connected to the coLinux. So, I would assume, you should use
in coLinux config:
# Bridging the real ethernet card:
eth2=ndis-bridge,"eth0"
or
# Bridging a Windows bridge (this is than a bride over a bridge):
eth2=ndis-bridge,"bri0"
--
Henry
On 05.08.2010 10:38, Lars Grundei wrote:
> Hi Henry,
>
> thanks for the support, my problem was depending on the MAC address (thanks again for the good explanation).
>
> For others in this situation: I had to deinstall the service (--remove-service) and install it again before it works (I guess this was probably my registry manipulation).
>
> Cheers
> Lars
> PS: Just for information, "tap0" is correct, I have renamed my network cards in windows: eth0=LAN, tap0=TAP-Win32 and bri0= Windows Bridge.
>
> -----Ursprüngliche Nachricht-----
> Von: Henry Nestler [mailto:hen...@ar...]
> Gesendet: Dienstag, 3. August 2010 22:05
> An: Lars Grundei
> Cc: 'col...@li...'
> Betreff: Re: [coLinux-users] Problem with windows service and ndis-bridge
>
> Hello Lars,
>
> On 03.08.2010 15:43, Lars Grundei wrote:
>> I use colinux 0.78 with the native windows network bridge, it runs fine if I start it from a console.
>> My problem is it to get up the windows service with network support. I can install, start and attach a console to the service.
>> But it is not possible for me, to start the bridged interface (eth2), ifup eth2 prints this:
>> -----------------------------
>> SIOCSIFADDR: No such device
>> eth2: ERROR while getting interface flags: No such device
>> SIOCSIFNETMASK: No such device
>> eth2: ERROR while getting interface flags: No such device
>> Failed to bring up eth2.
>> -----------------------------
>>
>> In the wiki, I've read something about service dependencies, but this sections seems to e outdated for 0.78 and also does not affect brigdeg network. However I have tried to add Bridge and some other to the service dependencies, without success.
>>
>> Service Dependicies:
>> --------------------
>> CoLinuxDriver
>> Bridge
>> BridgeMP
>> NPF
>> tap0801co
> Dependicies tap0801co (TAP-Win32), NPF (PCAP-bridge) you not need, if you not use such network options. They will automatically set, by the colinux-daemon, if they would be configured in your config.
>
> Please don't set Bridge and BridgeMP. CoLinux says ndis-bridge, because it works as a bridge. But it's not using any bridge drivers from Windows.
>
> And last: "Service Dependicies" means only, that this driver must be started before coLinux can start. So it is more for delayed coLinux start on the Windows boot, not for the manually start.
>
>
>> PS: Extract from the config file:
>> -----------------------------
>> # Slirp for internet connection (outgoing)
>> #eth0=slirp
>>
>> # Tuntap as private network between guest and host on second linux device
>> #eth1=tuntap
>>
>> # brigded networks
>> eth2=ndis-bridge,"tap0"
>> -----------------------------
> I think, "tap0" is not right there. Or your real network is an openVPN
> tunnel?
>
> Running from command line and as service, will use different Windows
> user accounts. With different user accounts, you would have different
> "automatic"-MAC for the eth2. DIfferent MAC your udev inside Linux will
> rename eth2 to any other eth3, eth3 or what ever.
>
> To solve this, please set a unic MAC for the eth2 in the coLinux config.
> Please read answer #4 in Forum at
> http://sourceforge.net/projects/colinux/forums/forum/342354/topic/3768555
>
> Or for udev renaming problem please read:
> http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2
|
|
From: Lars G. <Lar...@re...> - 2010-08-05 21:01:16
|
Hi Henry, ok now I am a bit confused. The colinux wiki (http://colinux.wikia.com/wiki/Network) tells me: "The NDIS driver is new in coLinux 0.7.4. It makes use of the NDIS programming API built into windows. It works in practice exactly like the WinPcap driver, just without third party network drivers. It follows the same syntax in the configuration file as the winpcap driver, just use ndis-bridge instead of pcap-bridge" And "The name and mac fields are optional. If you don't specify the name parameter coLinux will use the first TAP device it finds. If you don't specify the MAC address in mac, a random one will be generated (in the range 00:FF:xx:xx:xx:xx)." The 1st comment can be found in section NDIS (this was new to me). The 2nd comment can be found in section TAP, Installation (this is an old part of the wiki, I remember that from my first colinux contact, wich has been a couple of years ago). Two NICs are required to create a windows bridge, in my case it seems to be quite logical to use the eth0 and tap0 for this. According to my understanding this means, that you need specify the TAP device if you want to access colinux from the network. Could you clarify this? Thanks Lars -----Ursprüngliche Nachricht----- Von: Henry Nestler [mailto:hen...@ar...] Gesendet: Donnerstag, 5. August 2010 19:47 An: Lars Grundei Cc: 'col...@li...' Betreff: Re: [coLinux-users] Problem with windows service and ndis-bridge Hello Lars, > eth2=ndis-bridge,"tap0" I wonder, that you wand to bridge the tap0? The tap0 is the TAP-Win32 and direct connected to the coLinux. So, I would assume, you should use in coLinux config: # Bridging the real ethernet card: eth2=ndis-bridge,"eth0" or # Bridging a Windows bridge (this is than a bride over a bridge): eth2=ndis-bridge,"bri0" -- Henry On 05.08.2010 10:38, Lars Grundei wrote: > Hi Henry, > > thanks for the support, my problem was depending on the MAC address (thanks again for the good explanation). > > For others in this situation: I had to deinstall the service (--remove-service) and install it again before it works (I guess this was probably my registry manipulation). > > Cheers > Lars > PS: Just for information, "tap0" is correct, I have renamed my network cards in windows: eth0=LAN, tap0=TAP-Win32 and bri0= Windows Bridge. > > -----Ursprüngliche Nachricht----- > Von: Henry Nestler [mailto:hen...@ar...] > Gesendet: Dienstag, 3. August 2010 22:05 > An: Lars Grundei > Cc: 'col...@li...' > Betreff: Re: [coLinux-users] Problem with windows service and ndis-bridge > > Hello Lars, > > On 03.08.2010 15:43, Lars Grundei wrote: >> I use colinux 0.78 with the native windows network bridge, it runs fine if I start it from a console. >> My problem is it to get up the windows service with network support. I can install, start and attach a console to the service. >> But it is not possible for me, to start the bridged interface (eth2), ifup eth2 prints this: >> ----------------------------- >> SIOCSIFADDR: No such device >> eth2: ERROR while getting interface flags: No such device >> SIOCSIFNETMASK: No such device >> eth2: ERROR while getting interface flags: No such device >> Failed to bring up eth2. >> ----------------------------- >> >> In the wiki, I've read something about service dependencies, but this sections seems to e outdated for 0.78 and also does not affect brigdeg network. However I have tried to add Bridge and some other to the service dependencies, without success. >> >> Service Dependicies: >> -------------------- >> CoLinuxDriver >> Bridge >> BridgeMP >> NPF >> tap0801co > Dependicies tap0801co (TAP-Win32), NPF (PCAP-bridge) you not need, if you not use such network options. They will automatically set, by the colinux-daemon, if they would be configured in your config. > > Please don't set Bridge and BridgeMP. CoLinux says ndis-bridge, because it works as a bridge. But it's not using any bridge drivers from Windows. > > And last: "Service Dependicies" means only, that this driver must be started before coLinux can start. So it is more for delayed coLinux start on the Windows boot, not for the manually start. > > >> PS: Extract from the config file: >> ----------------------------- >> # Slirp for internet connection (outgoing) >> #eth0=slirp >> >> # Tuntap as private network between guest and host on second linux device >> #eth1=tuntap >> >> # brigded networks >> eth2=ndis-bridge,"tap0" >> ----------------------------- > I think, "tap0" is not right there. Or your real network is an openVPN > tunnel? > > Running from command line and as service, will use different Windows > user accounts. With different user accounts, you would have different > "automatic"-MAC for the eth2. DIfferent MAC your udev inside Linux will > rename eth2 to any other eth3, eth3 or what ever. > > To solve this, please set a unic MAC for the eth2 in the coLinux config. > Please read answer #4 in Forum at > http://sourceforge.net/projects/colinux/forums/forum/342354/topic/3768555 > > Or for udev renaming problem please read: > http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2 |
|
From: Henry N. <hen...@ar...> - 2010-08-05 23:17:17
|
Am 05.08.2010 23:01, schrieb Lars Grundei: > Hi Henry, > > ok now I am a bit confused. I'm too. - From your bridging the bridge ;-) > The colinux wiki (http://colinux.wikia.com/wiki/Network) tells me: > > "The NDIS driver is new in coLinux 0.7.4. It makes use of the NDIS programming API built into windows. It works in practice exactly like the WinPcap driver, just without third party network drivers. It follows the same syntax in the configuration file as the winpcap driver, just use ndis-bridge instead of pcap-bridge" > > And > > "The name and mac fields are optional. If you don't specify the name parameter coLinux will use the first TAP device it finds. If you don't specify the MAC address in mac, a random one will be generated (in the range 00:FF:xx:xx:xx:xx)." > > The 1st comment can be found in section NDIS (this was new to me). The 2nd comment can be found in section TAP, Installation (this is an old part of the wiki, I remember that from my first colinux contact, wich has been a couple of years ago). > > Two NICs are required to create a windows bridge, in my case it seems to be quite logical to use the eth0 and tap0 for this. According to my understanding this means, that you need specify the TAP device if you want to access colinux from the network. > > Could you clarify this? "Windows Bridge" and coLinux "ndis-bridge" are different types of networking. Of curse, they works similar. Some peoples use a "Windows Bridge" between WLAN card and Loopback adapter to break out the problem of multiple MAC address on the wireless channel. If you use "ndis-bridge" then it is working like a bridge between your real Ethernet card and the adapter on Linux side (eth2 in your case). You will add a second MAC on the same adapter and Linux than can send and receive packets over this. So, ndis-bridge give one adapter a second MAC adresses and a second IP-adresses (on the Linux side). The MAC and IP address are *added* to the normal work of Windows network stuff. In summary have two MACs and two IP adresses. But, every side (Windows and Linux) has only one MAC and one IP address. Compared with the "Windows Bridge": This will bind two adapters and adds an 3rd MAC for the bridge self. The original ipaddress of the both adapers are hidden (or removed), and the bridge self becomes a new IP address. TAP-Win32 is a separate network between Linux (guest) and Windows (Host). This network is normal not accessable from outside of your Windows. Now, if you have created a "Windows Bridge" between TAP-Win32 and your Ethernet card, than you have mixed the two networks to a big one. If you use ndis-bridge on this "Windows Bridge", then you will add the 4th MAC to this construct. And I don't understand why you don't use the real Ethernet adapter directly? Maybe it can work. Afraid not efficiently. And last you will not use the other end of TAP driver, so the Link is permanently down for TAP-Win32. I don't understand why you bridged the TAP? You have (as I assume): Windows LAN (MAC1) + Windows TAP-Win32 (MAC2) ==> Windows-Bridge (MAC3) Windows-Bridge (MAC3) ==> ndis-bridge ==> Linux eth2 (MAC4) Why not? Windows LAN ==> ndis-bridge ==> Linux eth2 Windows TAP-Win32 ==> tuntap ==> Linux eth1 Over the ndis-bridge you would have all the traffic between your Linux and the world outside of your Windows. This type of config you can also better configure for firewalls (inside Linux and/or Windows), and they are less of network driver layers. Windows Bridge is slower as ndis-bridge. With the additional TAP to eth1, all the traffic between Linux (guest) and Windows (host) you have a separate network with separate ip area (!) and will never seen on the local network. Now, if you use ndis-bridge you not need the TAP. You can also access your Linux from Windows and via versa over the ndis-bridge. Of curse the performance is not the best, because using more hardware stacks, and all the traffic from Linux to Windows would also seen on all the other networking devices in your local network. === The additional options now. For TAP-Win32 the "name" is optional. If you have only one TAP driver installed, then coLinux will find it. The TAP-Win32 driver has a specific ID, that coLinux knows and will locate for. ndis-bridge can use *all* adapters (inclusively TAP and loopback), and we need to know what interface is your connection to the world. If you have only ndis-bridge (no TAP-Win32), then it is really optional. If you have TAP-Win32 and ndis-bridge configured, then the ndis-bridge will some times wrong catch the TAP as your favorite network interface. It is rarely and depend on your CPU speed and number of cores. Single CPU cores often works slowly, so the TAP will be "link up" many seconds after the ndis-bridge has scanned all adapters, and all works perfect. On faster CPU and dual cores, the TAP-Win32 can be up before the ndis-bridge scans the network. In this case the name should written in config. The default sort order of network adapters is sorted by install date, and the last installed adapter is placed on top of the list. So you would have typically TAP-Win32, WLAN, on board Ethernet card, Loopback adapter. In my case, I have sorted my network adapters (some there in the menu "extras" in network overview) to let find coLinux my TAP all times as last adapter, after cable LAN and after WLAN (because WLAN dows not work with ndis-bridge). -- Henry N. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X