Wifi-TrayNet and Wifi-Scanner
This update deals with the annoying menu or extramenu changing everytime the connection is tested. Now which ever menu is selected it will remain until manually changed.
Added some commands to the bluetooth section.
Revisited ScannerM for a checkup.
Tested on FatDogs, BionicDog, Upupbb acheives same functionality on all.
Added some commands to the bluetooth section.
Revisited ScannerM for a checkup.
Tested on FatDogs, BionicDog, Upupbb acheives same functionality on all.
- Attachments
-
- Wifi-TrayNet-2019.sfs.gz
- fake gz extension
- (180 KiB) Downloaded 322 times
Wifi-HotSpot : My script made the assumption that create_ap resided in /usr/sbin but on examining the makefile I see it is /usr/bin so I changed the script accordingly. But also simplified some things, namely only one hotspot can run at a time from the script, cli allows 4 if your hardware can handle it.
Hotspot tray notification closes reliably. lists clients in a properly sized and positioned gui.
Hotspot tray notification closes reliably. lists clients in a properly sized and positioned gui.
- Attachments
-
- Wifi-TrayNet-2019.sfs.gz
- (180 KiB) Downloaded 318 times
What have I done
When editing some functions I simplified their names but forgot to reflect changes in menus and calls, so usb eth1 eth2 probably did not connect. Anyway i removed usb ethernet1 ethernet2 from extrasmenu and replaced with one option, wired. Which opens a gui and uses one function to connect whichever ethernet or usb is selected.
Added a menu entry for Wifi-ScannerM which gives an open gui on the desktop to compliment the tray menu.
I also found a typo for nameserver section.
sorry!
stemsee
When editing some functions I simplified their names but forgot to reflect changes in menus and calls, so usb eth1 eth2 probably did not connect. Anyway i removed usb ethernet1 ethernet2 from extrasmenu and replaced with one option, wired. Which opens a gui and uses one function to connect whichever ethernet or usb is selected.
Added a menu entry for Wifi-ScannerM which gives an open gui on the desktop to compliment the tray menu.
I also found a typo for nameserver section.
sorry!
stemsee
- Attachments
-
- xscreenshot-20190324T152503.png
- (5.55 KiB) Downloaded 528 times
-
- scrn.png
- (32.72 KiB) Downloaded 539 times
Last edited by stemsee on Sun 24 Mar 2019, 20:41, edited 1 time in total.
This update is the most polished. So many bugs had crippled much of the smooth functionality, but I didn't have the clarity to deal with them....until now.
A couple of typos corrected. Changes to the trap on Exit function.
A couple of typos corrected. Changes to the trap on Exit function.
- Attachments
-
- Wifi-TrayNet-0619.sfs.gz
- fake .gz . dated by month and year
- (180 KiB) Downloaded 252 times
Improvements.
I have changed the handling of ssid displayed in menu to allow all 32 characters if so named. Also ssid with '+' in the name can be handled correctly. Saving profiles by ssid with quotes.
Some work on the bluetooth section.
Quick connect is now in the mainmenu.
I have changed the handling of ssid displayed in menu to allow all 32 characters if so named. Also ssid with '+' in the name can be handled correctly. Saving profiles by ssid with quotes.
Some work on the bluetooth section.
Quick connect is now in the mainmenu.
- Attachments
-
- Wifi-TrayNet-ssid.sfs.gz
- (180 KiB) Downloaded 220 times
I found the problem that stopped TrayNet working as expected on 'Dogs'n'Pups' (FatDog was fine).
I have also implemented an initial roaming function, which connects to open networks or profiled networks.
I have also implemented an initial roaming function, which connects to open networks or profiled networks.
- Attachments
-
- Wifi-TrayNet-270619.sfs.gz
- (180 KiB) Downloaded 254 times
The way I want the roaming function to work is quite simple.
First all open networks found during the scan are listed, then all profiled networks are added to the same list then each is connected in sequence until the first one that connects to the internet (external ip) then new connections stop.
If the connection is lost then the external ip test loop re-initiates the roaming function, starting off from the last AP on the list, or even from a refreshed list.
But 'I' can't get it to do what I want!!! Therefore after much effort, I concede. I am giving up on the roaming function for the foreseeable future. At least for Wifi-TrayNet, maybe easier to implement on Wifi-ScannerM.
So this next update is really the final feature set. Features which may be re-implemented in new sequences, such as auto-random-mac on scan, connection, and during connection at random intervals etc
First all open networks found during the scan are listed, then all profiled networks are added to the same list then each is connected in sequence until the first one that connects to the internet (external ip) then new connections stop.
If the connection is lost then the external ip test loop re-initiates the roaming function, starting off from the last AP on the list, or even from a refreshed list.
But 'I' can't get it to do what I want!!! Therefore after much effort, I concede. I am giving up on the roaming function for the foreseeable future. At least for Wifi-TrayNet, maybe easier to implement on Wifi-ScannerM.
So this next update is really the final feature set. Features which may be re-implemented in new sequences, such as auto-random-mac on scan, connection, and during connection at random intervals etc
- Attachments
-
- Wifi-TrayNet-080719.sfs.gz
- (180 KiB) Downloaded 216 times
This update results from much tweaking, and a manual roaming function of sorts added, makes me feel this is the final of Wifi-TrayNet script.
Still work to be done on Wifi-ScannerM and Wifi-HotSpot scripts, but not much.
Still work to be done on Wifi-ScannerM and Wifi-HotSpot scripts, but not much.
- Attachments
-
- Wifi-TrayNet-290719.sfs.gz
- (180 KiB) Downloaded 205 times
Hi Stemsee - can you offer some advice please? What is the best way to use your scripts on a pristine (no savefile) version of either Slacko 5.6 or Bionic64 please?
(I always use pups as they come from the devs - without savefile mods).
Which of your scripts should I install in order to get my wifi running - is wifitraynet all i should need?
cheers!
ps - this is the sort of thing i see in Slacko 5.6:
(I always use pups as they come from the devs - without savefile mods).
Which of your scripts should I install in order to get my wifi running - is wifitraynet all i should need?
cheers!
ps - this is the sort of thing i see in Slacko 5.6:
Code: Select all
/usr/sbin/Wifi-Scanner: line 833: /tmp/Wifi-Scanner/interfaces: No such file or directory
bash: line 1: yad: command not found
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
/usr/sbin/Wifi-Scanner: line 930: yad: command not found
cat: /root/.wifi-connect/geometry/Wifi-Scanner-Multi-Wifi: No such file or directory
/usr/sbin/Wifi-Scanner: line 939: yad: command not found
cat: /tmp/Wifi-Scanner/net: No such file or directory
/usr/sbin/Wifi-Scanner: line 833: /tmp/Wifi-Scanner/interfaces: No such file or directory
bash: line 1: yad: command not found
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
/usr/sbin/Wifi-Scanner: line 930: yad: command not found
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
xwininfo: error: No window with name "Wifi-Scanner-Multi-Wifi" exists!
cat: /root/.wifi-connect/geometry/Wifi-Scanner-Multi-Wifi: No such file or directory
/usr/sbin/Wifi-Scanner: line 939: yad: command not found
Hi greengeek
Wifi-TrayNet is only a script, or collection of scripts.
The usual neworking packages, which are usually already installed as part of most distros, are; wpasupplicant, wireless-tools, dnsmasq, hostapd (for hotspot), tcp-dump (for wps), tail, tee, yad, awk, either udhcpc (busybox) or dhcpcd.
For hostpot you will also need the devx loaded on first use, or every use if no savefile or remaster is used.
The relevant executables needed are checked by the script.
Give it a test run and please give feedback.
cheers
stemsee
Wifi-TrayNet is only a script, or collection of scripts.
The usual neworking packages, which are usually already installed as part of most distros, are; wpasupplicant, wireless-tools, dnsmasq, hostapd (for hotspot), tcp-dump (for wps), tail, tee, yad, awk, either udhcpc (busybox) or dhcpcd.
For hostpot you will also need the devx loaded on first use, or every use if no savefile or remaster is used.
The relevant executables needed are checked by the script.
Give it a test run and please give feedback.
cheers
stemsee
as per Greengeek's post I have updated the dependency checking to use xmessage to show missing deps at app startup.
Also changed ip testing code.
Also changed ip testing code.
- Attachments
-
- Wifi-TrayNet-190819.sfs.gz
- fake .gz
- (180 KiB) Downloaded 203 times
-
- wifi-traynet-190819_7_amd64.deb.gz
- .deb fake .gz
- (172.62 KiB) Downloaded 212 times
I got around to learning how to properly configure network devices and connections using systemd-networkd. It's funny that my app works regardless of settings implemented by systemd-networkd. But I didn't realize that systemd-networkd (sydned going forward) has its own dhcp server builtin. I was wondering how peasywifi did it on BionicDog. So I will re-sculpt my scripts taking advantage of my new knowledge....before re-writing using wpa_cli instead of verbose statements...ha ha! It was fun though. Of course following the common path will be a massive security compromise as every snoop on the planet will know how your system is functioning. That is the advantage of my app, I suspect.
systemd also has miraclecast available which lets linux use wifidisplay and also allows other devices to cast their screens to a linux display. Control will be added to Wifi-TrayNet.
Another thing will be to include both bluetooth4 and bluetooth5 commands.
Bridging support should also be available as an option.
EDIT: bridgin is already implemented in the hotspot function... i forgot
systemd also has miraclecast available which lets linux use wifidisplay and also allows other devices to cast their screens to a linux display. Control will be added to Wifi-TrayNet.
Another thing will be to include both bluetooth4 and bluetooth5 commands.
Bridging support should also be available as an option.
EDIT: bridgin is already implemented in the hotspot function... i forgot
The next release has a few improvements.
one is choosing the correct Ap in the menu to highlight connection. Previously it wasnt getting the ap with strongest signal.
Another is to do with multiple mac addresses when changing ap using the password entry gui.
I will be updating the bluetooth sections.
Then finally, gettext (any volunteers?)
stemsee
one is choosing the correct Ap in the menu to highlight connection. Previously it wasnt getting the ap with strongest signal.
Another is to do with multiple mac addresses when changing ap using the password entry gui.
I will be updating the bluetooth sections.
Then finally, gettext (any volunteers?)
stemsee
Reworked wired (usb0 eth0 etc) function. Reworked hard airplanemode so that wlan and bluetooth can be down but eth0 usb0 can still be tested for internet.
autocon script for usb0 eth0 connection on X-start.
Scan function no longer invokes rfkill unblock all.
autocon script for usb0 eth0 connection on X-start.
Scan function no longer invokes rfkill unblock all.
- Attachments
-
- Wifi-TrayNet-211019.sfs.gz
- (180 KiB) Downloaded 189 times