CLInet 0.8
Posted: Fri 08 Jan 2010, 00:27
Greetings everybody!
I've been working on the issue with connecting a PC to the internet on the commandline for quite some time, and now I've got a working prototype: CLInet.
What it does:
It is a dialog-based tool chain (total size of all files is approx 30 KB) that allows you to set up a connection with a cable connection, wireless LAN connection, and dial-up with a modem. The tools create an executable script running the dial-up tools with generated configs so you can even start a dial-up without the need for CLInet itself. Later versions are supposed to be able to edit the config files of the router scripts (and wxdial).
Since I have only very limited possibilities here when it comes to testing everything, any help would be VERY appreciated, especially with the modem part.
Please remember that this thing is VERY brittle right now and still is cramped with bugs. I'll try to fix'em as good as I can, but bash scripting is totally new for me (I usually program GUIs in tcl/tk), so I'd welcome any helping hand.
Update:
I forgot to mention what I've tested so far *note to myself: don't throw stuff out to the crowd at 1:30 in the morning *
The system proved to work with:
- LAN connection
- WLAN and WEP encryption
- WLAN and WPA encryption
- WLAN and WPA2 encryption
It should work with:
WLAN and no encryption (I managed to get a connection to a public AP but I didn't have the necessary login data at hand to actually dial into the net)
It probably works with (but hasn't been tested yet):
- Modem connection
I'd appreciate any feedback about wether the connection types mentioned above do work with others or not, so I can fix these things first (if necessary) before going for the editor part.
That said ... fire it up!
UPDATES!!!
v 0.2: I moved the generated scripts and temporary config files to a temp folder in the user's home directory to avoid conflicts (and security issues) in a multi-user environment. Also fixed a few bugs with the connect2modem script so you can actually abort the whole process if necessary.
v 0.3: now runs under the GUI as well. Thanks for the idea with XDialog, aragon.
v 0.4: Fixed some bugs that came up with Puppy 4.31. Also changes the layout of the dialogs a bit so they are more compatible with both dialog and xdialog
v 0.5: Edited the start script according to aragon's proposal (I seriously totally forgot about that one xD). But I used -z $DISPLAY instead for checking out if X is running or not. Also re-enabled Xdialog for all scripts again after fixing some layout problems and fixed a serious flaw in the design; I added t message box that warns the user if there's no access point available (the former versions tried to run the script anyway).
v 0.6: CLInet now always opens in dialog mode only (on X, it opens in rxvt) because XDialog tended to catch error messages and put them into the temporary variables, screwing up the entire process.
Added the promised edit functions for router connections. You may set the connection to ad-hoc (directly between two computers) or Standard (connection over a router), as well as the driver mode for normal and hidden router SSIDs.
v 0.7: Added cross-reference links to the pppoe wizardtools. CLInet may now be used to configure DLS connections over modems as well. Also changed the layout from the main dialog box to make it fit the new features properly.
v.0.8: Added a rescan function for the case that there were no access points in range. Also replaced the echo message with a dialog messagebox to tell if the system successfully established a connection or not.
I've been working on the issue with connecting a PC to the internet on the commandline for quite some time, and now I've got a working prototype: CLInet.
What it does:
It is a dialog-based tool chain (total size of all files is approx 30 KB) that allows you to set up a connection with a cable connection, wireless LAN connection, and dial-up with a modem. The tools create an executable script running the dial-up tools with generated configs so you can even start a dial-up without the need for CLInet itself. Later versions are supposed to be able to edit the config files of the router scripts (and wxdial).
Since I have only very limited possibilities here when it comes to testing everything, any help would be VERY appreciated, especially with the modem part.
Please remember that this thing is VERY brittle right now and still is cramped with bugs. I'll try to fix'em as good as I can, but bash scripting is totally new for me (I usually program GUIs in tcl/tk), so I'd welcome any helping hand.
Update:
I forgot to mention what I've tested so far *note to myself: don't throw stuff out to the crowd at 1:30 in the morning *
The system proved to work with:
- LAN connection
- WLAN and WEP encryption
- WLAN and WPA encryption
- WLAN and WPA2 encryption
It should work with:
WLAN and no encryption (I managed to get a connection to a public AP but I didn't have the necessary login data at hand to actually dial into the net)
It probably works with (but hasn't been tested yet):
- Modem connection
I'd appreciate any feedback about wether the connection types mentioned above do work with others or not, so I can fix these things first (if necessary) before going for the editor part.
That said ... fire it up!
UPDATES!!!
v 0.2: I moved the generated scripts and temporary config files to a temp folder in the user's home directory to avoid conflicts (and security issues) in a multi-user environment. Also fixed a few bugs with the connect2modem script so you can actually abort the whole process if necessary.
v 0.3: now runs under the GUI as well. Thanks for the idea with XDialog, aragon.
v 0.4: Fixed some bugs that came up with Puppy 4.31. Also changes the layout of the dialogs a bit so they are more compatible with both dialog and xdialog
v 0.5: Edited the start script according to aragon's proposal (I seriously totally forgot about that one xD). But I used -z $DISPLAY instead for checking out if X is running or not. Also re-enabled Xdialog for all scripts again after fixing some layout problems and fixed a serious flaw in the design; I added t message box that warns the user if there's no access point available (the former versions tried to run the script anyway).
v 0.6: CLInet now always opens in dialog mode only (on X, it opens in rxvt) because XDialog tended to catch error messages and put them into the temporary variables, screwing up the entire process.
Added the promised edit functions for router connections. You may set the connection to ad-hoc (directly between two computers) or Standard (connection over a router), as well as the driver mode for normal and hidden router SSIDs.
v 0.7: Added cross-reference links to the pppoe wizardtools. CLInet may now be used to configure DLS connections over modems as well. Also changed the layout from the main dialog box to make it fit the new features properly.
v.0.8: Added a rescan function for the case that there were no access points in range. Also replaced the echo message with a dialog messagebox to tell if the system successfully established a connection or not.