Inspiration
Default available network troubleshooters doesn't point you to the exact point of failure but rather just say you're not connected to the internet. Tired of checking all possibilities by yourself ? KNet comes to your rescue.
What it does
If you are not able to connect to the network there are many failure points but the default troubleshooter fails in pointing to the most probable point of failure. Some possible cases might be failure of DHCP or the default gateway is broken.
How I built it
I used C to execute commands like ping , ipconfig or any of the system commands that i've used. And I used ruby for pattern matching and extracting the data from the file. Some shell script in between to pipe the output to a file.
Challenges I ran into
Getting ip configuration is tedious. With variety of operating systems available there are different commands to get the ip address or any such information. Essentially system commands are OS specific.
Accomplishments that I'm proud of
Effectively use different system calls and transferring extracted data through different stages of execution.
What I learned
How I can use different system calls and how to deal with IPv4 and IPv6 addresses while pattern matching.
What's next for Network Troubleshooter
Add GUI features may be using Java applets where I create an event handler and run a system command when we click on a button.
Log in or sign up for Devpost to join the conversation.