Message-Id: <200310192050.NAA28830@raq2.projecta.com>
In-Reply-To: <200310191845.LAA23064@raq2.projecta.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date:  Sun, 19 Oct 2003 13:50:30 -0700 (PDT)
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  "Thomas Garson" <os2-wireless_users@2rosenthals.com>
To:  "os2-wireless_users@2rosenthals.com" <os2-wireless_users@2rosenthals.com>
Subject: [OS2Wireless] Virtual Switch from Innotek Virtual PC can't see out through Prism mini-pci WiFi of Thinkpad A31

On Sun, 19 Oct 2003 11:45:13 -0700 (PDT), Thomas Garson wrote:

>On Sun, 19 Oct 2003 08:10:59 -0700, Lewis G Rosenthal wrote:
>
>>A follow-up to my last reply. At Warpstock this morning, I'm sitting 
>>next to Oliver Stein from Innotek, and just asked him about this issue. 
>>Here's a more exact answer:
>>In order for Vswitch to work with Wi-Fi, two things need to happen: The 
>>driver for the card must support promiscuous mode (Jens' drivers do, 
>>others may not); and the access point must be able to work 
>>inefficiently, meaning, it must not discard packets signed with a 
>>different MAC address than the Wi-Fi NIC of the client; many AP's - for 
>>the sake of efficiency and security - simply discard such packets.
>>Which AP are you using?
>
>D-Link DI-614+
>
>>Thomas Garson wrote:
>>
>>>I have installed Innoteks Virtual PC 5.1 on that system. It is way cool:-) 
>>>I've got VPC networking like a champ via its Virtual Switch driver in all ways (local, host and external) when 
>>>connecting through the hardware ethernet interface (Intel) in the Thinkpad.
>>>I'm stonewalled trying to achieve the same connectivity using the Prism card. I can achieve TCP/IP networking 
>>>access using the Prism card from VPC by using its "Shared Networking (NAT)" mode. Unfortunately, that 
>>>mode, by design, does not support NETBIOS, so I can't access any SAMBA shares, which is absolutely 
>>>essential. If I select Virtual Switch mode, I get no external connectivity by TCP/IP or NETBIOS but local 
>>>connectivity (to the host), including NETBIOS, works. It seems (easy for me to say) that this is a Prism driver 
>>>issue, rather than a VPC issue.

Followup:

Now I'm REALLY confused. I decided to play around with Shared Networking (NAT) mode in VPC over the WiFi port, again. This, 
even though the VPC docs tell you it is limited in what you can do through it. WELL, since going through all of the gyrations to 
get full access to my LAN when using the Intel hardwire ethernet port (VPC running Win98SE), I have somehow achieved 
virtually the same level of function using Shared Networking (NAT) mode!

>From VPC, I am able to access shares on its host computer (Thinkpad), the other OS/2 workstation on the same subnet, and 
SAMBA shares my Linux server located on another subnet that is physically removed from this location. The server is linked 
over the internet by a pair of SmoothWall firewall/VPN boxes. All TCP/IP and SMB network connections originating from VPC 
work. I can't access the VPC from the network, presumably because of the translation going on in the host, but as of the 
moment, that is immaterial since I don't intend to use my Thinkpad as any sort of server. 

An  acceptable, for the moment at least, workaround has seemingly been achieved.


Thomas Garson
Aural Technology, Ashland, Or.
tgarson@auraltek.com

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=