colinux-devel

[coLinux-devel] WinPcap problems

[Ronald P. <pij...@ds...>]

Hi,

I've got the following network setup:

router:  192.168.15.1
windows: 192.168.15.172 (dhcp)
colinux: 192.168.15.4   (static)

with gateway 192.168.15.1 on both windows and colinux.

When I use the winpcap bridge, I am able to ping to windows from colinux,
but I can't seem to ping the router, which works fine from windows. As I
far as I understand the winpcap setup, this should go without any further
configuration, right?

Any ideas on how to tackle this problem?

Ronald.

Re: [coLinux-devel] WinPcap problems

[Alejandro R. S. <as...@MI...>]

Hi Ronald,

Can you post your complete network configuration information on both
machines and the coLinux config file?

'/sbin/ifconfig' on coLinux
'ipconfig /all' on windows
the '<network...' line from default.colinux.xml or equivalent.

Also, what version of WinPCap?

Thanks,

-Alejandro

On Sat, 2004-03-20 at 15:43, Ronald Pijnacker wrote:
> Hi,
> 
> I've got the following network setup:
> 
> router:  192.168.15.1
> windows: 192.168.15.172 (dhcp)
> colinux: 192.168.15.4   (static)
> 
> with gateway 192.168.15.1 on both windows and colinux.
> 
> When I use the winpcap bridge, I am able to ping to windows from colinux,
> but I can't seem to ping the router, which works fine from windows. As I
> far as I understand the winpcap setup, this should go without any further
> configuration, right?
> 
> Any ideas on how to tackle this problem?
> 
> Ronald.
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
> 

Re: [coLinux-devel] WinPcap problems

[Ronald P. <pij...@ds...>]

> Hi Ronald,
>
> Can you post your complete network configuration information on both
> machines and the coLinux config file?
>
> '/sbin/ifconfig' on coLinux
> 'ipconfig /all' on windows
> the '<network...' line from default.colinux.xml or equivalent.
>
> Also, what version of WinPCap?

Sure, here it is. Hopefully the Dutch windows installation isn't a proble=
m.

----------------------------------------------------------------------
colinux:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:43:4F:4E:45:30
          inet addr:192.168.15.4  Bcast:192.168.15.255  Mask:255.255.255.=
0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:173 errors:0 dropped:0 overruns:0 frame:0
          TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:27960 (27.3 KiB)  TX bytes:12892 (12.5 KiB)
          Interrupt:2

colinux:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use I=
face
192.168.15.0    *               255.255.255.0   U     0      0        0 e=
th0
default         192.168.15.1    0.0.0.0         UG    0      0        0 e=
th0

----------------------------------------------------------------------
D:\>ipconfig /all

Windows IP-configuratie

        Host-naam  . . . . . . . . . . . .: windows-box
        Primair DNS-achtervoegsel. . . . .:
        Knooppunttype: . . . . . . . . . .: onbekend
        IP-routering ingeschakeld. . . . .: ja
        WINS-proxy ingeschakeld . . . . . : nee

Ethernet-adapter Draadloze netwerkverbinding:

        Verbindingsspec. DNS-achtervoegsel: o15.ehv.nl
        Beschrijving . . . . . . . . . . .:
          SMC2835W 2.4GHz 54 Mbps Wireless Cardbus Adapter
        Fysiek adres. . . . . . . . . . . : 00-04-E2-80-A5-2C
        DHCP ingeshakeld. . . . . . . . . : ja
        Autom. configuratie ingeschakeld. : ja
        IP-adres. . . . . . . . . . . . . : 192.168.15.172
        Subnetmasker. . . . . . . . . . . : 255.255.255.0
        Standaardgateway. . . . . . . . . : 192.168.15.1
        DHCP-server . . . . . . . . . . . : 192.168.15.1
        DNS-servers . . . . . . . . . . . : 192.168.15.1
        Lease verkregen . . . . . . . . . : zondag 21 maart 2004 18:50:58
        Lease verlopen . . . . . . . . .  : dinsdag 23 maart 2004 18:50:5=
8

----------------------------------------------------------------------
default.colinux.xml:

    <network index=3D"0" name=3D"SMC2835W 2.4GHz 54 Mbps Wireless Cardbus
Adapter" type=3D"bridged"></network>
----------------------------------------------------------------------

WinPCap version is 3.0.


Thanks,

Ronald.

Re: [coLinux-devel] WinPcap problems

[Alejandro R. S. <as...@MI...>]

Ok, yeah, this one is easy. IEEE 802.11 specs require that wireless
cards only transmit packets with a source MAC that is their own. You can
ping your own machine because it's clever enough to deal with the packet
internally, but you can't ping the router because the packet never
leaves the card.

As of right now, the bridged net daemon does not support any wireless
cards. When I get some free time (I just got a job...) I'll be working
on a workaround that will allow the two machines two share the host MAC
and let the filtering happen at an IP level. This won't be perfect (dhcp
will break for one of the two machines if you're trying to use it for
both) but it'll be better than nothing.

-Alejandro

On Sun, 2004-03-21 at 14:17, Ronald Pijnacker wrote:
> > Hi Ronald,
> >
> > Can you post your complete network configuration information on both
> > machines and the coLinux config file?
> >
> > '/sbin/ifconfig' on coLinux
> > 'ipconfig /all' on windows
> > the '<network...' line from default.colinux.xml or equivalent.
> >
> > Also, what version of WinPCap?
> 
> Sure, here it is. Hopefully the Dutch windows installation isn't a problem.
> 
> ----------------------------------------------------------------------
> colinux:~# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:43:4F:4E:45:30
>           inet addr:192.168.15.4  Bcast:192.168.15.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:173 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:27960 (27.3 KiB)  TX bytes:12892 (12.5 KiB)
>           Interrupt:2
> 
> colinux:~# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 192.168.15.0    *               255.255.255.0   U     0      0        0 eth0
> default         192.168.15.1    0.0.0.0         UG    0      0        0 eth0
> 
> ----------------------------------------------------------------------
> D:\>ipconfig /all
> 
> Windows IP-configuratie
> 
>         Host-naam  . . . . . . . . . . . .: windows-box
>         Primair DNS-achtervoegsel. . . . .:
>         Knooppunttype: . . . . . . . . . .: onbekend
>         IP-routering ingeschakeld. . . . .: ja
>         WINS-proxy ingeschakeld . . . . . : nee
> 
> Ethernet-adapter Draadloze netwerkverbinding:
> 
>         Verbindingsspec. DNS-achtervoegsel: o15.ehv.nl
>         Beschrijving . . . . . . . . . . .:
>           SMC2835W 2.4GHz 54 Mbps Wireless Cardbus Adapter
>         Fysiek adres. . . . . . . . . . . : 00-04-E2-80-A5-2C
>         DHCP ingeshakeld. . . . . . . . . : ja
>         Autom. configuratie ingeschakeld. : ja
>         IP-adres. . . . . . . . . . . . . : 192.168.15.172
>         Subnetmasker. . . . . . . . . . . : 255.255.255.0
>         Standaardgateway. . . . . . . . . : 192.168.15.1
>         DHCP-server . . . . . . . . . . . : 192.168.15.1
>         DNS-servers . . . . . . . . . . . : 192.168.15.1
>         Lease verkregen . . . . . . . . . : zondag 21 maart 2004 18:50:58
>         Lease verlopen . . . . . . . . .  : dinsdag 23 maart 2004 18:50:58
> 
> ----------------------------------------------------------------------
> default.colinux.xml:
> 
>     <network index="0" name="SMC2835W 2.4GHz 54 Mbps Wireless Cardbus
> Adapter" type="bridged"></network>
> ----------------------------------------------------------------------
> 
> WinPCap version is 3.0.
> 
> 
> Thanks,
> 
> Ronald.
> 
> 

Re: [coLinux-devel] WinPcap problems

[Ronald P. <pij...@ds...>]

> Ok, yeah, this one is easy. IEEE 802.11 specs require that wireless
> cards only transmit packets with a source MAC that is their own. You ca=
n
> ping your own machine because it's clever enough to deal with the packe=
t
> internally, but you can't ping the router because the packet never
> leaves the card.

Hmm... that explains the problem. I'll try with a cable... I do see the
light on the wireless card blinking, though...

> As of right now, the bridged net daemon does not support any wireless
> cards. When I get some free time (I just got a job...) I'll be working
> on a workaround that will allow the two machines two share the host MAC
> and let the filtering happen at an IP level. This won't be perfect (dhc=
p
> will break for one of the two machines if you're trying to use it for
> both) but it'll be better than nothing.

OK. For now NAT is good enough, I'm not able to boot my Gentoo system yet=
.
When that happens the problem becomes a bit bigger...

Thanks,

Ronald.

Re: [coLinux-devel] WinPcap problems

[Ronald P. <pij...@ds...>]

Ronald Pijnacker wrote:
>>Ok, yeah, this one is easy. IEEE 802.11 specs require that wireless
>>cards only transmit packets with a source MAC that is their own. You can
>>ping your own machine because it's clever enough to deal with the packet
>>internally, but you can't ping the router because the packet never
>>leaves the card.
> 
> 
> Hmm... that explains the problem. I'll try with a cable... I do see the
> light on the wireless card blinking, though...

Just to let you know that indeed it works when using a cable. Thanks for 
  saving me days of useless debugging effort.

Ronald.

Re: [coLinux-devel] WinPcap problems

[<ch...@to...>]

Ok I could be totally off base with this but wouldn't putting the card in
master mode bypass the mac address requirement?

Here is an article that talks about building an AP that acts like a bridge
on linux
http://www-106.ibm.com/developerworks/library/l-wap.html?ca=dnt-429

iwconfig can tell the card to go to master mode. I do not know if this is
suposed to be possible with all cards or not.
Of course in this situation this would have to be set in windows. And the
configuration software might not allow this.
But maby it could be set with regedit.

How does the ctrl click 2 interfaces rt click select "bridge these
interfaces" work with wireless in XP ? My best guess is that it would have
to set the card to master mode or it would not work at all or it does not
create a true layer2 bridge.

Just throwing some ideas out there.

chris


> Ronald Pijnacker wrote:
>>>Ok, yeah, this one is easy. IEEE 802.11 specs require that wireless
>>>cards only transmit packets with a source MAC that is their own. You can
>>>ping your own machine because it's clever enough to deal with the packet
>>>internally, but you can't ping the router because the packet never
>>>leaves the card.
>>
>>
>> Hmm... that explains the problem. I'll try with a cable... I do see the
>> light on the wireless card blinking, though...
>
> Just to let you know that indeed it works when using a cable. Thanks for
>   saving me days of useless debugging effort.
>
> Ronald.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>