... what he said...
Sorry my description was so confusing to follow. L3mce got it correct but let me see if I can clarify it even further.USB Modem
plugs into the USB port of:Cradle Point
The only other connection on this device is ethernet out which goes to my core on eth0
Settings: It is DHCP, for its own network that consists of wireless clients and the Core.
It gave the Core an IP of 192.168.0.7
I made this static so that port forwarding rules would stick even after a power loss or disconnection
Non-lmce devices connect to this wireless network which is named Orphan's Cradle D-Link IP Cam
sits on this network as well @ 192.168.0.162
My Core/Hybrid can see this network, however devices connected to eth1 of my core can not, obviously
Out from the Core/Hybrid which has a default IP address of 192.168.80.1
and is a DHCP for its own internal network: Netgear Router
Settings: This router is functioning as a switch, it has nothing on its WAN port and DHCP has been disabled
This device was given a static IP by me from the Core of 192.168.80.254
(this was done so I can always get into the interface and add new MAC addresses to allow wireless access
Wifi1 connection is WebDT (192.168.80.135)
Wifi2 connection is iPhone4 (192.168.80.137)
LAN1 is connected to eth1 of the Core
LAN2-4 are connected to internal components (I cant recall which is on what atm)
HD HomeRun (192.168.80.3)
VOIP Adapter (192.168.80.4)
Ubuntu 10.04 PC (192.168.80.136)
It looks worse in person if I was to take a photo of that wiring closet believe me. Overall though, my Core gets its IP from an external network. My lmce devices all connect to the internal network. Sorry for the confusion my cradlepoint (and description of it) caused. The only thing non-typical of an external router connected to eth0 would be my IP cam. I had some issues with it dropping out after a while and after reading I found a work-around of adding it to an external network. The core still considers it a lease even though it doesn't have the ability to give it a static IP on that network. It shows up in DHCP leases of the web-admin as 192.168.0.162
. I have not had any dropping out issues since putting it out there.
And now that all of the admins know my external IP and all of my device IPs... If my myth starts recording adult films mysteriously I know who to blame!