Quote:
Originally Posted by deed02392
After 'upgrading' to the superhub, not only am I lacking the ability to use my internal LAN DNS server (at least as issued by the hubs DHCP),
|
Yep - essetially I believe its because VM want you to use their DNS, they removed the ability to specify a dns server from the router. You now have to set it "per device" which sucks, but isn't hard.
Quote:
|
I've noticed that SSH connections appear to be dropping whilst left inactive.
|
Yep, about every 120 seconds by my own testing.
Quote:
|
This caused quite a mess when I was dist-upgrading last night and it disconnected half way through.
|
You should't really be dist-upgrading over a ssh connection unless you are 100% sure of its stability, as an unexpected disconnect can cause problems.
Quote:
|
Does anyone know if this is a configurable option of the Superhub before I waste time fiddling through the terrible interface?
|
Is what a configurable option? The DNS servers? No. The timeout interval? No. There are workarounds though. Change the tcpkeepalive setting in sshd_config and ssh_config to sidestep the timeouts, and set your DNS servers manually on each connected device, or put the superhub into modem mode, and use your own router.
Quote:
|
PS: Does anyone know if I can get shell access to the Superhub or otherwise modify the routing table? The ability to route everything through another server before going back out to the internet would be great.
|
There was a bug in the firmware that left an active ssh port open on the superhub, but they fixed it. I guess they didn't want to risk anyone figuring out how to use this privileged access to change stuff that shouldnt be changed. Can't say I blame them.