Frisbee Network Manager 1.4.9

Configuration wizards, scanners, remote desktop, etc.
Message
Author
User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#41 Post by rerwin »

I discovered this posting in the "Frisbee Network Manager - Beta 2" thread:
libomer wrote:My network needs a username and password to access it
( recognized by frisbee as EAP encryption ).

After version 1.4.7, it is not possible.

So, I guess, there is a bug, nobody noticed,
because that type of encryption is rare.
If anyone wants to work with me to investigate and test this, please post here, so that we can get started.
Richard

User avatar
WB7ODYFred
Posts: 169
Joined: Sun 14 Dec 2008, 02:15
Location: Oregon & Washington

Modifying Frisbee Network Manager 1.4.9 for another Linux

#42 Post by WB7ODYFred »

Testing modified Frisbee on Manjaro Linux (an Arch based Linux)
https://manjaro.org
https://ghostbsd.org

Hello Rerwin, Wb7ody Fred Finster here, inidicating my interest in modifying Frisbee to work on other Linux Distributions and eventually on FreeBSD 12.0 Stable based GhostBSD version 19.09.

Basic changes in Frisbee files in directory /usr/local/frisbee
Change ifconfig to ip command. Most of the shell scripts already had use of ip commands and wpa_cli and wpa_supplicant.

Code: Select all

cd /usr/local/frisbee
grep -n ifconfig *
grep -n iwconfig *
grep -n busybox *
change ifconfig command to ip command
comment out iwconfig command
delete busybox command "usually busybox pidof" to just pidof
Almost working out of the box on Manjaro Linux. Work In Progress (WIP) the shell SED code for ifconfig command, to get the working name of the network interfaces like eth0 or wlan0 or for Manjaro Linux enp25s0 or wlp3s0

manually edit or set /etc/frisbee/interface to wlp3s0 the wireless interface here on my Manjaro Linux box.


Richard, Looking for any changes or suggestions or Debian Dog code you can share via URL link or email wb7odyfred@yahoo.com

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#43 Post by rerwin »

Hi Fred,

I just now noticed your posting. I am willing to work with you to the extent I can be of use.

I would like to know the issues regarding ifconfig, iwconfig, busybox pidof.

I assume the 'ip' command is newer and more comprehensive than ifconfig (& iwconfig?) -- are those now deprecated?

Regarding pidof, I have been replacing it with the full 'ps' command with arguments (wherever I am already modifying code), on the assumption that is better. I have seen cases where pidof did not produce what I expected -- either extra processes or missing some (I forget which).

I am open to adapting the woofCE frisbee so that it can work in other distributions. But I am not knowledgeable about distros other than Puppy and a little bit about the Dogs, so would depend on you for that expertise and guidance.
Richard

williams2
Posts: 337
Joined: Fri 14 Dec 2018, 22:18

#44 Post by williams2 »

For anybody who might not realize,
I read somewhere that iwconfig is for WEP connections.

If you run iwconfig and it says
iwconfig
[snip]
Encryption key:off
Power Management:off
Link Quality=51/70 Signal level=-59 dBm

this does not mean encryption is disabled.
It means there is no WEP encryption
because you are using wpa2
which is good.

wpa_cli status
[snip]
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED

CCMP is AES, which is good.

PSK is the password.
I usually use wpa_passphrase to encrypt the psk password
to put in wpa_supplicant.conf
instead of the unencrypted password.

Post Reply