Quote:
Originally Posted by ferretuk
- DDNS updating may well not work as the router given the task of running the update will have a private IP address on its WAN port, not the VM public address.
|
It'll work just fine. Before people had DDNS clients in their routers they were running on PCs with private IP addresses. The update server sees the public IP as the source of the connection whenever the client tries to update anyway.
Quote:
Originally Posted by ferretuk
Machine IP addresses will change as you move between segments.
|
Not necessarily. I don't see why they would. You would only have one subnet and one IP range.
Quote:
Originally Posted by ferretuk
Far easier, IMHO, to simply use the downstream routers as access points...
|
Easier, if you don't need to magic up an extra 4 ports and additional cable out of thin air...
Quote:
Originally Posted by ferretuk
Looking at a Cisco document, their implementation of 'bridge' mode completely disables all router functionality, including DHCP, and turns the unit into an access point anyway...
|
That's basically what an AP is... a bridge.
Quote:
Originally Posted by ferretuk
Accessing the printers and the NAS that are connected to the SH from the LAN side of the downstream router will be problematic and speed limited!
|
I don't see why it would. It should go at full switch speed, i.e. gigabit.
Quote:
Originally Posted by ferretuk
'Discovery' software won't work for printer installation (if required).
|
Should work just fine. When set up correctly you will still only have one subnet and one ethernet domain.
Quote:
Originally Posted by ferretuk
Static IPs will need to be configured on the SH connected devices (not necessarily a bad thing of course!) and this isn't mentioned by GM...
|
Should work just fine without. The second router dishing out DHCP addresses will dish out DHCP addresses.
Quote:
Originally Posted by ferretuk
"Not ideal" is a bit of understatement! It's a dog's dinner  |
Again, the majority of corporate LANs and the internet at large works on this sort of setup, it's not ideal only in it's hard to set up properly.
Quote:
Originally Posted by ferretuk
The routers under discussion are, by default, NAT devices.
|
Unless you turn NAT off. NAT is an optional feature and present on just about any router.
Quote:
Originally Posted by ferretuk
Makes management of them a bit more awkward if they're not? No reason not to be on the same subnet so why make life difficult?
|
I don't get your point. My proposal *is* to put them all on the same subnet.
Quote:
Originally Posted by ferretuk
The WAN address of the second router will be the private address allocated by the SH so that's likely to be the address used for DDNS update.
|
Or, it'll use the public address like it should do.
Quote:
Originally Posted by ferretuk
PC clients are 'NAT aware' and will identify the public address when behind a NAT router but do router clients work in the same way?
|
Yes.
Quote:
Originally Posted by ferretuk
I haven't tested this (have you?)
|
Yes.
Quote:
Originally Posted by ferretuk
but it would seem unlikely...
|
Works just fine. On Openwrt especially, you can set it to use any IP and fetch it via any mechanism. Either the server can use the IP it sees the connection coming from, or the router can go to
www.whatismyip.com and submit the IP it gets from there.
---------- Post added at 17:14 ---------- Previous post was at 17:13 ----------
Quote:
Originally Posted by General Maximus
Yes it will. The only booboo i made suggesting you put the shub in modem mode and then use it as a switch. I'll correct myself: as we dont want to use the shub as either a router or wireless ap ditch it all together and get a gigabit switch
|
The problem would be, obviously, you would need an extra switch and an extra cable running across the house. Which can be avoided with some clever setup.
---------- Post added at 17:17 ---------- Previous post was at 17:14 ----------
Quote:
Originally Posted by ferretuk
Correction to my own post - Accessing the printers and NAS won't work...
|
Should work just fine. You will still have one continuous ethernet broadcast domain.
Quote:
Originally Posted by ferretuk
To the OP:
If using the SH ethernet ports is important then you'll have to use it as a router and my advice in post 12 stands. |
Probably the easiest option tbh.
Quote:
Originally Posted by ferretuk
Back to the iPhone issue - If you want to be able to access machines (plural) on your LAN you're into the realms of setting up a VPN server in your LAN (and client on the iPhone) rather than port forwarding...
|
Not sure why you would need a VPN. Port forwarding works in all circumstances and most mobile clients use it as their primary/default access mechanism.