On Sun, 02 Aug 2009 23:22:38 -0500, M.L. <me@privacy.invalid> wrote:
>Ok, I set the SMCWTVG mode as a Wireless Client. Here is what the
>manual states about that mode:
>
><quote>
>The configuration of wireless settings is available in Gateway Mode
>and Access Point Mode only.
>...
>To access a wireless network in Wireless Client mode, connect your PC
>to the LAN port and then set your PC’s network connection to DHCP.
No big deal. Take whatever IP address it offers for now.
>In
>Wireless Client mode, the Personal Mobile Gateway acts as a DHCP
>server to assign IP address settings to one client connected on the
>LAN port.
OK, that makes sense. Without NAT, you can only bridge one IP address
in the SMC, which is acting like a transparent wireless ethernet
client bridge (whew!).
>Use the default IP address, 192.168.2.1, to access the web
>management interface. Using the Setup Wizard or from the Mode Config
>page, you can then set up a connection to a nearby access point.
></quote>
Ok. It really doesn't matter what IP address you use for management.
However, you really want the Netgear to assign the IP address or you
don't get to talk to the Netgear. With the SMC operating in the
client mode, you apparently now have two DHCP servers operating. One
in the Netgear and one in the SMC. That can be fixed. Read on.
>So I changed the SMCWTVG's gateway IP to 192.168.2.1, and it connects
>to my LAN connection using DHCP. However, it knocks out my wireless
>laptop connection to the Netgear.
Well yes. Your Netgear is at 192.168.0.1. It's not going to see
anything on the 192.168.2.xxx network. So, please make the following
changes:
1. Plug your computah into one of the LAN ports of the SMC travel
router. Disable the wireless on your computer if so equiped to keep
from accidentally connecting to the Netgear.
2. Change the DHCP assigned IP address range of the Netgear from the
default 192.168.0.2 -> 192.168.0.254 to something more sane like:
192.168.0.100 -> 192.168.0.199
3. Set the IP address of the SMC to 192.168.0.2. This should be
static and not DHCP assigned.
4. Turn OFF the DHCP server in the SMC. This may cause some initial
headaches until you establish a wireless connection with the Netgear.
5. Reboot everything and pray. If everything works as expected, you
should get an IP address from the Netgear on your computer. If you
get something like 169.254.xxx.xxx, it didn't work. If that happens,
try:
ipconfig /release
wait about 5 seconds
ipconfig /renew
If that still doesn't work, set your computer for a static IP address
for 192.168.0.99 (or whatever). Any gateway and blank DNS servers.
Now, you should be able to connect to the SMC at 192.168.0.2 and fix
the configuration. Yes, I know turning off the DHCP server in the SMC
is a pain at the laptop level, but you only have to do it once. Reboot
again or do the above ipconfig trick. You should eventually get a
DHCP assigned IP address of 192.168.0.100 with a gateway IP of
192.168.0.1. The DNS server could be 192.168.0.1 or the real DNS
servers depending on how the Netgear is configured.
6. Try browsing the internet, it should work.
>I get my wireless Internet
>connection back only if I disable the LAN connection. Does that make
>sense?
What LAN connection? You should *NOT* have both a CAT5 cable and a
wireless connection running simultaneously between the Netgear and the
SMC. In the client mode, you are using the travel router as a
wireless client. The only things that gets connected to the LAN ports
on the SMC is the management computah.
>>Other random suggestions:
>>1. If you're eventually going to have two wireless access points
>>operating, choose different non-overlapping channels (such as 1,6,11)
>>for each.
>>2. Consider using different SSID's for each access point.
>
>I can't do any of those things in Wireless Client mode since the
>wireless settings are not available in that mode. I also notice that
>the wireless indicator light is unlit in Wireless Client mode.
The SMC description you quote is self-contradictory. The first line
says that the wireless settings are not available in client mode. Then
3rd sentence explains how to connect to the web management pages.
What I guess(tm) they meant is that you cannot change the wireless
channel in client mode. That's normal because the system access point
controls what channel is used. The client scans all channels looking
for a matching SSID. I think when you get everything on the same
Class C IP address block, and disarm the extra DHCP server, things
will start to work correctly.
What a PITA.
--
Jeff Liebermann
jeffl@cruzio.com
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
Re: Wireless Router Can't See Wireless Device 
Linear Mode
