Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Offline Hints #593

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Offline Hints #593

wants to merge 1 commit into from

Conversation

thormj
Copy link

@thormj thormj commented Oct 21, 2020

Instead of a FakeDNS server, these are instructions to add to your host file to do offline operation.
I also added the FASpath/FASport to the Readme.md as an example of the difference between OpenNDS and Nodogsplash.

@bluewavenet
Copy link
Contributor

@thormj
There is much more to openNDS than just FASpath/FASport and for people not familiar with it FASpath/FASport will be meaningless. For better clarity, perhaps it should say something like:

If you want a more sophisticated authentication system providing a dynamic web interface, you need openNDS with its Forwarding Authentication Service API (FAS), rather than NoDogSplash.

  • making sure the link on the word "openNDS" is maintained.

@bluewavenet
Copy link
Contributor

@thormj
Adding entries to the hosts file might seem to be a good idea at first sight, but you will find there are many, perhaps hundreds of CPD detection urls. Not only that, they have also been known to change with vendor updates as well as varying by model. Samsung is one of the worst for this. Chromebooks from various manufacturers as well.

I don't mean to discourage you, on the contrary, it is very refreshing to see someone going down the same rabbit hole I went down a few years ago :-D Someone else going through the same thought processes is very valuable.

Adding to the hosts file might be a good solution for edge cases, for example IoT management using a standardised "engineers" phone for example.

With regard to "Hints", in my opinion the correct place is in the documentation. A new section would be most useful.
By documentation, I mean in the docs folder of course.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants