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.

Sign up for GitHub

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

Jump to bottom

You're doing the diagnostic part all wrong. Write a diagnose_network ( host, transport, port, protocol) function #33

Open
jeffsilverm opened this issue Jan 31, 2019 · 1 comment
Open

You're doing the diagnostic part all wrong. Write a diagnose_network ( host, transport, port, protocol) function #33

jeffsilverm opened this issue Jan 31, 2019 · 1 comment
Assignees
@jeffsilverm

Comments

@jeffsilverm
Copy link
Owner

No description provided.

@jeffsilverm jeffsilverm self-assigned this Jan 31, 2019
@jeffsilverm
Copy link
Owner Author

The NBMDT is working at the wrong level of abstraction. There is nothing wrong with monitoring a network - lots of programs do it and the NBMDT, as it currently stands, is just another network monitoring tool. That's not what's needed.

What's needed is a function that an application program can call that explains to the caller why the socket call just failed. Did DNS fail because no name server was available? Did DNS fail because the name server couldn't find an IP address by that name? (Bonus points if that name has an A record but not AAAA record or vice versa) Did ARP fail because there is no carrier (the cable is not plugged in)? The Wifi is not working? Is the NIC visible to the operating system?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeffsilverm jeffsilverm

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeffsilverm