From: "Al Heath" <os2-wireless_users@2rosenthals.com>
Received: from mxout2.mailhop.org ([63.208.196.166] verified)
  by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9)
  with ESMTP id 391022 for os2-wireless_users@2rosenthals.com; Wed, 27 Sep 2006 18:08:52 -0400
Received: from mxin2.mailhop.org ([63.208.196.176])
	by mxout2.mailhop.org with esmtp (Exim 4.51)
	id 1GSha9-0002zZ-IO
	for os2-wireless_users@2rosenthals.com; Wed, 27 Sep 2006 18:08:46 -0400
Received: from e33.co.us.ibm.com ([32.97.110.151])
	by mxin2.mailhop.org with esmtp (Exim 4.51)
	id 1GSha9-000Ly7-BB
	for os2-wireless_users@2rosenthals.com; Wed, 27 Sep 2006 18:08:45 -0400
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11])
	by e33.co.us.ibm.com (8.13.8/8.12.11) with ESMTP id k8RM8dWT001831
	for <os2-wireless_users@2rosenthals.com>; Wed, 27 Sep 2006 18:08:39 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167])
	by westrelay02.boulder.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id k8RM8dVt525814
	for <os2-wireless_users@2rosenthals.com>; Wed, 27 Sep 2006 16:08:39 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k8RM8dSJ003472
	for <os2-wireless_users@2rosenthals.com>; Wed, 27 Sep 2006 16:08:39 -0600
Received: from d03nm122.boulder.ibm.com (d03nm122.boulder.ibm.com [9.17.195.148])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k8RM8d75003466
	for <os2-wireless_users@2rosenthals.com>; Wed, 27 Sep 2006 16:08:39 -0600
Importance: Normal
Sensitivity: 
Subject: Re: [OS2Wireless]Re: Adding internal Wi-Fi to non-Wi-Fi-ready notebooks
To: "OS/2 Wireless Users Mailing List" <os2-wireless_users@2rosenthals.com>
Date: Wed, 27 Sep 2006 17:08:35 -0500
Message-ID: <OFC4E6CB83.C4D9204C-ON862571F6.007684AF@us.ibm.com>
X-MIMETrack: Serialize by Router on D03NM122/03/M/IBM(Release 7.0.1HF269 | June 22, 2006) at
 09/27/2006 16:08:39
MIME-Version: 1.0
Content-type: multipart/alternative; 
	Boundary="0__=09BBFB65DFE5023F8f9e8a93df938690918c09BBFB65DFE5023F"
Content-Disposition: inline
X-Mail-Handler: MailHop by DynDNS
X-Spam-Score: -1.7 (-)

--0__=09BBFB65DFE5023F8f9e8a93df938690918c09BBFB65DFE5023F
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable






Andy replied...
>Unfortunately, the NAT connection makes for a sorry Socks server
>connection (it almost works but is very slow and unreliable).  The way=

>I do it works well so that I can use the wireless, so long as you can
>add a static route (IOW doesn't work when traveling)....

Thanks Andy,
My problem is only when traveling and only when I don't have power for =
the
Netgear bridge (as that Netgear works without having to do any special
routing) When traveling I can't modify the other people's routers...hot=
els,
coffee shops, etc are fussy about that <g>.  When I'm with the T42, I c=
an
put the Dlink on the wired port connection and have only the VPC side u=
se
that one, and use the built wireless on the T42 for the OS/2 side only.=
..
and get two DHCP addresses as normal, etc...  Not optimal as all socks
traffic goes from OS/2 -> T42 built in wireless -> service router -> ba=
ck
thru DLink -> hardwired T42 port -> VPC session (tunnel) -> hard wired =
port
-> DLink -> service router -> and out. (No special routing required on =
the
service router as both addresses are on same subnet just like two real
machines would be as peers.)  When I'm on the T23 (or T42 and disable t=
he
built in wireless) and have 100V power available I can put the Netgear =
on
the wired port and it seems like the socks traffic goes from OS/2
internally on the virtual switch of the ethernet port to the VPC sessio=
n ->
(tunnel) -> ethernet port -> bridge -> service router -> ... and on dow=
n
the line.  Non socks traffic on the OS/2 side just goes out normally ..=
, on
the port -> bridge -> and out.  Substitute the DLink for the netgear br=
idge
and only side will work at a time.   I've also tried routing all traffi=
c
through the socks instead of just the 9.x traffic, and that will sort o=
f
work but then everything is getting socksified.  With the VPC virtual
switch in there, does the DLink see 2 mac addresses (and it is crippled=
 to
only support 1 at a time???) or how does the aliasing work?  The netgea=
r is
happy enough, but the DLink isn't.  I can cycle the power on the DLink =
and
one side or the other will send/receive traffic when it reconnects, but=

never both sides at the same time.  I guess I should just move totally =
to
the T42 and use the round-a-bout method, or stick with AC power and the=

bridge.  Naturally, totally hardwired isn't a problem at all.

Al H=

--0__=09BBFB65DFE5023F8f9e8a93df938690918c09BBFB65DFE5023F
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

<html><body>
<p><tt>Andy replied...<br>
&gt;Unfortunately, the NAT connection makes for a sorry Socks server<br=
>
&gt;connection (it almost works but is very slow and unreliable). &nbsp=
;The way<br>
&gt;I do it works well so that I can use the wireless, so long as you c=
an<br>
&gt;add a static route (IOW doesn't work when traveling)....</tt><br>
<br>
<tt>Thanks Andy, &nbsp;</tt><br>
<tt>My problem is only when traveling and only when I don't have power =
for the Netgear bridge (as that Netgear works without having to do any =
special routing) When traveling I can't modify the other people's route=
rs...hotels, coffee shops, etc are fussy about that &lt;g&gt;. &nbsp;Wh=
en I'm with the T42, I can put the Dlink on the wired port connection a=
nd have only the VPC side use that one, and use the built wireless on t=
he T42 for the OS/2 side only... and get two DHCP addresses as normal, =
etc... &nbsp;Not optimal as all socks traffic goes from OS/2 -&gt; T42 =
built in wireless -&gt; service router -&gt; back thru DLink -&gt; hard=
wired T42 port -&gt; VPC session (tunnel) -&gt; hard wired port -&gt; D=
Link -&gt; service router -&gt; and out. (No special routing required o=
n the service router as both addresses are on same subnet just like two=
 real machines would be as peers.) &nbsp;When I'm on the T23 (or T42 an=
d disable the built in wireless) and have 100V power available I can pu=
t the Netgear on the wired port and it seems like the socks traffic goe=
s from OS/2 internally on the virtual switch of the ethernet port to th=
e VPC session -&gt; (tunnel) -&gt; ethernet port -&gt; bridge -&gt; ser=
vice router -&gt; ... and on down the line. &nbsp;Non socks traffic on =
the OS/2 side just goes out normally .., on the port -&gt; bridge -&gt;=
 and out. &nbsp;Substitute the DLink for the netgear bridge and only si=
de will work at a time. &nbsp; I've also tried routing all traffic thro=
ugh the socks instead of just the 9.x traffic, and that will sort of wo=
rk but then everything is getting socksified. &nbsp;With the VPC virtua=
l switch in there, does the DLink see 2 mac addresses (and it is crippl=
ed to only support 1 at a time???) or how does the aliasing work? &nbsp=
;The netgear is happy enough, but the DLink isn't. &nbsp;I can cycle th=
e power on the DLink and one side or the other will send/receive traffi=
c when it reconnects, but never both sides at the same time. &nbsp;I gu=
ess I should just move totally to the T42 and use the round-a-bout meth=
od, or stick with AC power and the bridge. &nbsp;Naturally, totally har=
dwired isn't a problem at all.<br>
</tt><br>
Al H</body></html>=

--0__=09BBFB65DFE5023F8f9e8a93df938690918c09BBFB65DFE5023F--