On Sun, 02 Aug 2009 13:35:42 -0500, M.L. <email@example.com> wrote:
>Comcast Netgear Wireless Cable Modem Gateway CG814WG
>SMC Networks SMCWTVG Wireless Router/ATA
>I'd rather not debate WEP. I don't want to turn off WEP for testing. I
>use a HEX key.
Fine, but you're making your life difficult. I don't think hackers
will attack your system in the short time it takes to verify that you
can connect and get a DHCP assigned IP from the router.
Incidentally, if the CG814WG has MAC address filtering, or other
obstructive security measure enabled, I suggest you might want to
either include the MAC address of the wireless and wired interfaces
(they're different) of the SMCWTVG ATA. Better yet, just disable it
for testing. (General plan.... keep it simple).
>The SMCWTVG works in one of 3 easily selectable modes: As a Router, a
>Wireless Client, or an Access Point. I want to use it only as an
>Access Point for VOIP.
It won't work the way you want. In the router mode, the DHCP server
is enabled. You cannot have a DHCP server and client running on the
same interface (ethernet or wireless). It's one, or the other. Even
if you disable the DHCP server in the router mode, that doesn't
magically enable the DHCP client.
However, in the wireless client mode, the DHCP server will be disabled
and the DHCP client will probably be automagically enabled.
Note that I'm not calling it an AP (access point). In order for it
work as an AP, the NAT translation should not be functional. Reading
the data sheet at:
it's obviouly a router, not an AP. However, the data sheet uses both
terms interchanegably. Are there seperately selectable "AP mode" and
"router mode" in the SMC? If my guess(tm) is correct, "AP mode" would
allow only one wireless or ethernet connection because it can connect
to only one IP address without NAT. (For NAT/PAT to work, you need a
Incidentally, the SMCWTVG is generically known as a "travel router".
As you noted, it has various modes, each of which involve different
configuration of DHCP server, client, AP mode, client mode, and
probably whether the FXO connects to the WAN side or LAN side of the
If you insist on running it in the router mode, the wireless part of
the puzzle is NOT going to connect to another router. However, if the
travel router supported WDS (wireless distribution service), it would
be possible for the travel router to simultaneously act as an AP,
client, and repeater. However, looking at the data sheet, this is not
I tried to download the manual from the SMC web pile and failed. It
found the product, but no downloadable manual.
>The wireless Access Point mode automatically turns off such router
>features as firewall, NAT and DHCP, essentially leaving the SMCWTVG as
>a passthrough device for VOIP.
Please look again. I didn't see any AP mode. I saw a *ROUTER* mode
which is a very different animal.
>The Ethernet connection used for
>testing is supposed to get its IP from the Netgear router, not the
Ummm... what ethernet connection? If you mean the client computer,
that's wrong. In router mode, it get its DHCP assigned IP address
from the DHCP server in the SMCWTVG. That's what the
>However, since it's not getting an IP I'm forced to assign it
>a static one during testing.
I'm a bit confused as to what you're trying to accomplish. If
everything is working, except for obtaining a DHCP assigned IP
address, just assign a static IP and be done with it.
>I'm trying to find out why the Netgear
>isn't handing over an IP address to my LAN connection, and why the
>SMCWTVG isn't showing up on the Netgear's config web page as a
>connected wireless device.
Yep... it should. In AP mode (actually router mode) the WAN interface
should have a DHCP client running, exactly like on a commodity wired
router. However, the wireless port is probably connected to the
ethernet switch, which puts it on the LAN side of the router. You
cannot use the wireless to connect to the Netgear CG814WG because two
wireless AP's will not talk/connect to each other. It will connect in
client mode, but you didn't want to do that.
>Although the SMCWTVG has an IP
>(192.168.0.120) within the Netgear's IP range, it's acting as though
>it's not on Netgear's network. I hope this clarifies my OP.
That's correct. In AP (or more correctly router) mode, it's on the
LAN side of the SMC router, which will not connect to an AP. You use
that for other wireless clients to connect to the SMC.
Jeff Liebermann firstname.lastname@example.org
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558