3 ms·
OK, I know it's the worst to show a product and have the first thing out of the audience be a feature request. So I guess first: this looks awesome. Second: w
by gjem97 9y ago
OK, I know it's the worst to show a product and have the first thing out of the audience be a feature request. So I guess first: this looks awesome. Second: what I really want from a SOHO router is a decent remote administration workflow. Our network admin is remote/part-time, and frequently uses remote-desktop apps to be "present" on our network to administer our firewall.
Here's what I'm thinking. Build an OTP display into the router that is necessary as a second factor for remote administration. Then, instead of allowing the remote administrator to make changes immediately, require me (on the local network) to approve the changes.
Regardless of the actual implementation, it seems like remote administration is a neglected featureset of the SOHO networking world. In my experience, though, it is very common to need someone outside the network to make changes (remote employee, family member, IT consulting shop, etc).
- ogig 9y agoSOHO routers already have ways of remote administration. You just need to be brave enough to expose it's web panel or telnet cli to the internet.
- gjem97 9y agoRight, and so that was my point about an second factor built in to the device.
- chme 9y agoSo like a configuration in a git repository and the router only pulls the master branch, external person pushes changes to a feature branch and merges to master have to be done by you. Something like this is doable. See puppet, saltstack, ansible, etc. With openwrt you could put the /etc/config directory in a git repo and have a cron job regularly pulling it. Not sure why you need an OTP display.
- gjem97 9y agoYeah, I think I was implicitly including in my use case people unfamiliar with git/puppet/etc.