I thought I had just copied a set of statements from an earlier post.
I have no idea why/what these are really doing. [Most of this is
'black-art' to me, but I understand that the DHCP is needed for the
active NIC and that is the reason for the exercise.]
Unfortunately, I am now away from the Wireless AP, but I will try to
have the change [replace mptstart with dhcpstrt] tested by someone who
is there and see what happens.
Thanks for the response.
Carl
On Fri, 31 Oct 2003 22:37:29 -0500, Lewis G Rosenthal wrote:
>I tend to agree with Frank's point about calling mptstart.cmd. You
>should only have to call dhcpstrt, as you have commented, unless there's
>something in the NETBIOS setup which is eluding me (I don't do any of
>the peer networking stuff, so I don't use NETBIOS; I'm at a bit of a
>loss to test this for you).
>
>On 10/31/2003 02:38 am, Carl Gehr thus wrote :
>
>>On Thu, 30 Oct 2003 23:26:13 -0500, Lewis G Rosenthal wrote:
>>
>>
>>
>>>Sam, as I recall, you were using static IP for the Wi-Fi connection,
>>>correct? In this case, you shouldn't need Neil's script, as that simply
>>>swaps the DHCP interface from LAN0 to LAN1. In your case, one or both of
>>>your interfaces are set to static IP, so you should be good to go with
>>>both interfaces configured (just not with the same address, as that is
>>>usually used for fault tolerant configurations).
>>>
>>>
>>
>>Lewis,
>>
>>Since you brought up the Cmd files to switch the DHCP between
>>interfaces, I'd like to revisit the subject. I just returned from a
>>trip where I had easy access to both a wired and wireless connection.
>>All attempts to use commands distributed here a while back to switch
>>the interface failed.
>>
>>Just so we're all starting from the same place, here are the specifics
>>of my configuration and the command files:
>>
>>=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
>> Configuration Information
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>LAN-0: Wired DriverName = E100B$
>> TCP/IP
>> NetBIOS for OS/2
>> DHCP active.
>>
>>LAN-1: 802.11b DriverName = PRISMP$
>> TCP/IP
>> NetBIOS for OS/2
>>
>>=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
>> The Commands
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>Switch Wired to Wireless
>>========================
>>/* CmdName: ActENet.Cmd */
>>/* Turn the Radio ON
>> * This command activates the 802.11b interface
>> *
>> * The wireless NIC should be inserted in the PC Card slot
>> */
>>say "Turn the Wireless Radio ON "
>>say "Activating the Wireless Network Card"
>>'@ ifconfig lan0 down'
>>'@ ifconfig lan0 delete'
>>'@ dhcpmon -t'
>>'@ route -fh'
>>'@ arp -f'
>> /* '@ dhcpstrt -i lan1 -d 0' */
>>'@ Call c:\mptn\bin\mptstart.cmd -i lan1 -d 5'
>>say "Wireless Networking Enabled"
>>return
>>
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>Switch Wireless to Wired
>>========================
>>/* CmdName: ActENet.Cmd */
>>/* Turn the radio OFF
>> * This command activates the 802.11b interface
>> */
>>say "Turn the Wireless Radio OFF"
>>say "Activating the Ethernet Network Card"
>>'@ ifconfig lan1 down'
>>'@ ifconfig lan1 delete'
>>'@ dhcpmon -t'
>>'@ route -fh'
>>'@ arp -f'
>> /* '@ dhcpstrt -i lan0 -d 0' */
>>'@ Call c:\mptn\bin\mptstart.cmd -i lan0 -d 5'
>>say "Ethernet Networking Enabled"
>>return
>>
>>=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
>>
>>So, what am I doing wrong?
>>
>>Thanks,
>>Carl
>>
>>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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).