Re: Does MBRIDGE work with 802.11b and 802.3 ?
From: K. S. Huang (ks_huang_at_AlphaNetworks.com_remove.this)
Date: 08/13/04
- Next message: Bruce Eitman \(eMVP\): "Re: Why don't DLL create?"
- Previous message: Nitin: "Network Driver registry Settings"
- In reply to: Holger: "Re: Does MBRIDGE work with 802.11b and 802.3 ?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 13 Aug 2004 19:02:26 +0800
I think that might be hard to let a Station Mode Driver enable the
Promiscuos,
especially the driver is a legacy NDIS driver.
Although, there are some WLAN card on Desktop Windows can enable the
Promiscuos mode,
but it will pass all of the RAW packet to its upper edge (like the Atheros
WLAN used with AiroPeek).
So I think that only AP mode WLAN driver can be used with the MBridge.
"Holger" <froelich@fs-net.de> 撰寫於郵件新聞
:uRBnEJSgEHA.3948@TK2MSFTNGP11.phx.gbl...
> Here are some news:
> After checking the SMSC driver i have seen that the bit to enable
> promiscious mode is not set correctly. After changing this, i'm able to
ping
> to the ip address given to mbridge.
> But, i have still no access to my WLAN interface.
> I also checked the CISCO driver and found that they have commented out the
> function to enable the promiscious mode. I have changed this, but without
> success.
> Any idea ?
> Thank you
> Holger
>
>
> "K. S. Huang" <ks_huang@AlphaNetworks.com_remove.this> schrieb im
> Newsbeitrag news:OgvV7vOgEHA.704@TK2MSFTNGP09.phx.gbl...
> > Well, I am not using the CISCO WLAN card, but I am using intersil PCI
bus
> > WLAN card in our device.
> > And my Intersil WLAN card is working in AP mode.
> >
> > the following is the result of NDISCONFIG.exe
> >
> > **********
> > Protocols: NDISUIO TCPIP PPP PPPOE MBRIDGE NATIVEWIFI
> > Adapters: PCI\INDIGO1 IXP4XXETHNPE2 IXP4XXETHNPE1 PPPOE1 MBRIDGE1
> > Adapter Bindings
> > ------- --------
> > PCI\INDIGO1 MBRIDGE
> > IXP4XXETHNPE2 NDISUIO TCPIP
> > IXP4XXETHNPE1 MBRIDGE
> > PPPOE1 PPP
> > MBRIDGE1 NDISUIO TCPIP
> > **********
> >
> > the MBridge1 in my device is bind to NDISUIO and TCPIP
> >
> > what is the ARP entry for the 10.0.0.195 on your PC??
> > Normally, the MBridge will use the first binding interface and modified
> the
> > first by into 0x02.
> > for example, the MAC addr. of IXP4XXETHNPE1 is 00-70-00-22-22-22
> > and the MBridge will use 02-70-00-22-22-22 as its MAC address.
> >
> > I think you could try to only bind the SMSC11XFD1 into MBridge and try
to
> > see if it could work find or not.
> >
> > Also note that most of the Station Mode WLAN card driver may NOT support
> the
> > PROMISCUOUS mode that will receive all of the packet.
> > If not the MBridge may NOT be functional.
> >
> > "Holger" <froelich@fs-net.de> 撰寫於郵件新聞
> > :uj4ev#HgEHA.636@TK2MSFTNGP12.phx.gbl...
> > > Thank you for your answer.
> > >
> > > I have changed the order of the two entrys under Bind.
> > > The problem is, that a ping to 10.0.0.192 does not work.
> > > ipconfig:
> > > Ethernet adapter [MBRIDGE1]:
> > > IP Address .....: 10.0.0.192
> > > Subnet mask ...: 255.0.0.0
> > > Default Gateway..: 10.0.0.5
> > > DNS Servers ......: 10.0.0.5
> > >
> > > If i ping from my CE device to 10.0.0.192 (loopback) works fine.
> > >
> > > If i type ndisconfig i see that CISCO1 and SMSC11XFD1 are bind to
> > MBRIDGE1.
> > > But MBRIDGE1 has no bindings. Is this correct ?
> > >
> > > As already told, a ping from my PC to 10.0.0.192 doesn't work. But if
i
> > type
> > > arp -a i see an entry for 10.0.0.192.
> > >
> > > Do you have an idea whats wrong ?
> > > Do you also use WinCE 4.2 CISCO driver ?
> > >
> > > Many thanks
> > > Holger
> > >
> > >
> > >
> > > "K. S. Huang" <ks_huang@alphanetworks.com.remove.this> schrieb im
> > > Newsbeitrag news:uDEmTzHgEHA.1656@TK2MSFTNGP09.phx.gbl...
> > > > The MBridge can work fine with a WLAN card,
> > > > but actually the MBridge can only work with 802.3 packet!!
> > > > But most of the WLAN will translate the 802.11 packet into a 802.3
> > packet
> > > > internally, so it is still like a regular 802.3 NIC for the upper
> layer
> > > > driver.
> > > >
> > > > Even for the Native-WiFi driver (a kind of NDIS driver that will
> > > > tranmist/receive packet in 802.11 to its upper layer), there will be
> > > > NativeWiFi Intermediate driver for translating the packet to/from
> 802.3
> > > > packet.
> > > >
> > > > Do you try to let the SMSC11XFD1 be your first param of Bind??
> > > > "Bind"=multi_sz:"SMSC11XFD1", "CISCO1"
> > > >
> > > > the WLAN card might be in disconnected state before it connect to an
> AP,
> > > so
> > > > let a regular LAN port be MBridge's first interface might be better.
> > > >
> > > >
> > > > "Holger" <froelich@fs-net.de> 撰寫於郵件新聞
> > > > :#NgbPWHgEHA.636@TK2MSFTNGP12.phx.gbl...
> > > > > Hello,
> > > > >
> > > > > i'm trying to use mbridge from WCE 4.2 to bridge between a PCMCIA
> WLAN
> > > > card
> > > > > and my onboard SMSC ethernet port. I have no success.
> > > > > It seems like i have configured all correctly but I'm not sure if
> > > mbridge
> > > > > can work with 802.11.
> > > > >
> > > > > If anyone has a idea what's wrong or can tell me that it must work
> or
> > > not
> > > > > work, please tell me.
> > > > >
> > > > > Regards
> > > > > Holger
> > > > >
> > > > > I have the following registry settings:
> > > > >
> > > > >
> > > > > [HKEY_LOCAL_MACHINE\Comm\MBridge]
> > > > > "DisplayName"="Microsoft Mac Bridge Miniport"
> > > > > "Group"="NDIS"
> > > > > "ImagePath"="MBridge.dll"
> > > > > "Bind"=multi_sz:"CISCO1","SMSC11XFD1"
> > > > >
> > > > > [HKEY_LOCAL_MACHINE\Comm\MBridge\Linkage]
> > > > > "Route"=multi_sz:"MBRIDGE1"
> > > > >
> > > > > [HKEY_LOCAL_MACHINE\Comm\MBridge1]
> > > > > "DisplayName"="Microsoft Mac Bridge Adapter"
> > > > > "Group"="NDIS"
> > > > >
> > > > > [HKEY_LOCAL_MACHINE\Comm\MBridge1\Parms]
> > > > > "BusNumber"=dword:0
> > > > > "BusType"=dword:0
> > > > >
> > > > > [HKEY_LOCAL_MACHINE\Comm\MBridge1\Parms\TcpIp]
> > > > > "EnableDHCP"=dword:0
> > > > > "DefaultGateway"=""
> > > > > "UseZeroBroadcast"=dword:0
> > > > > "IpAddress"="10.0.0.192"
> > > > > "Subnetmask"="255.0.0.0"
> > > > >
> > > > > [HKEY_LOCAL_MACHINE\Comm\CISCO1\Parms]
> > > > > "ProtocolsToBindTo"=multi_sz:"MBRIDGE"
> > > > >
> > > > > [HKEY_LOCAL_MACHINE\Comm\SMSC11XFD1\Parms]
> > > > > "ProtocolsToBindTo"=multi_sz:"MBRIDGE"
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Bruce Eitman \(eMVP\): "Re: Why don't DLL create?"
- Previous message: Nitin: "Network Driver registry Settings"
- In reply to: Holger: "Re: Does MBRIDGE work with 802.11b and 802.3 ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
