Puppy Linux Discussion Forum

@rerwin :

I find the easiest way around that 'Default' issue is simply to re-run the internet Connection Wizard from the Menu.....which then gives the list of choices to select from again.

With regard to that last item you mentioned, I've had it happen to me a number of times. You get 169.254.xxx.xxx; you appear to have an internet connection, but you are NOT, in fact, connected. It's not a proper sub-net address.

These days, I always use Dougal's Network Wizard, forgo the "delights" of DHCP.....and set-up 'statics'. Works for me.

-------------------------------------------------------

BTW; not enough people say it, so I will now..... Thanks for everything you do, Richard.....especially this networking stuff. It IS very much appreciated. As I've noted on a number of occasions, browsers are the "glue" that hold our on-line communities together. And without the ability to get the things connected, on-line, even they are useless.

Mike.

How does Frisbee connect hidden WiFi?

debianfan wrote: ↑Mon Jun 06, 2022 11:19 pm

How does Frisbee connect hidden WiFi?

For me, Frisbee does not connect to hidden networks, because there is no way to tell it the network name (SSID) since it is hidden when Frisbee scans for available networks. But supporting hidden networks seems reasonable, to allow users to hide their own networks.

If you (or anyone) prefer(s) to not use SNS or network wizard for hidden networks, I can add the capability to Frisbee. I think it just needs to detect that a network is hidden and prompt for the SSID when it asks for the password. It should also indicate "hidden" instead of showing the SSID as "\x00...". My next project.

Note, however, if there are multiple hidden networks, the user will need to guess which is the desired network, probably by trial and error. Once a hidden network is connected, Frisbee should retain the SSID for automatic startup.

Richard

rerwin wrote: ↑Wed Jun 08, 2022 7:42 pm

debianfan wrote: ↑Mon Jun 06, 2022 11:19 pm

How does Frisbee connect hidden WiFi?

For me, Frisbee does not connect to hidden networks, because there is no way to tell it the network name (SSID) since it is hidden when Frisbee scans for available networks. But supporting hidden networks seems reasonable, to allow users to hide their own networks.

If you (or anyone) prefer(s) to not use SNS or network wizard for hidden networks, I can add the capability to Frisbee. I think it just needs to detect that a network is hidden and prompt for the SSID when it asks for the password. It should also indicate "hidden" instead of showing the SSID as "\x00...". My next project.

Note, however, if there are multiple hidden networks, the user will need to guess which is the desired network, probably by trial and error. Once a hidden network is connected, Frisbee should retain the SSID for automatic startup.

Richard

I love Frisbee and look forward to your updates! thank you!

rerwin wrote: ↑Wed Jun 08, 2022 7:42 pm

debianfan wrote: ↑Mon Jun 06, 2022 11:19 pm

How does Frisbee connect hidden WiFi?

For me, Frisbee does not connect to hidden networks, because there is no way to tell it the network name (SSID) since it is hidden when Frisbee scans for available networks. But supporting hidden networks seems reasonable, to allow users to hide their own networks.

If you (or anyone) prefer(s) to not use SNS or network wizard for hidden networks, I can add the capability to Frisbee. I think it just needs to detect that a network is hidden and prompt for the SSID when it asks for the password. It should also indicate "hidden" instead of showing the SSID as "\x00...". My next project.

Note, however, if there are multiple hidden networks, the user will need to guess which is the desired network, probably by trial and error. Once a hidden network is connected, Frisbee should retain the SSID for automatic startup.

Richard

Can Frisbee modify dns alone? Just don't modify the ip address, but use a fixed dns, I hope this function can be added

linuxunix wrote: ↑Thu Jun 09, 2022 7:20 am

Can Frisbee modify dns alone? Just don't modify the ip address, but use a fixed dns, I hope this function can be added

@linuxunix
I think the choice is either automatic or all static IP address & DNS.

But maybe you can achieve what you need by first using DHCP ("automatic") to obtain an IP address, then using that address to set up the static address/dns.

From where do you get the IP address with DHCP? A router, your ISP or somewhere else. Please tell me more about your setup.

Richard

Can Frisbee modify dns alone?

AFAIK, you can do exactly that by configuring your preferred DNS address or addresses in file /etc/resolv.conf.head for example:

#CloudFlare
nameserver 1.1.1.1
nameserver 1.0.0.1
#IBM Quad9
nameserver 9.9.9.9
#end head

For each url (web page name) this will try each dns nameserver in the list until it finds one that works. dhpc will put a different dns nameserver in /etc/resolv.conf, but the nameservers in /etc/resolv.conf.head will be tried and used first.

debianfan wrote: ↑Thu Jun 09, 2022 1:42 am

I love Frisbee and look forward to your updates! thank you!

@debianfan
Attached is my candidate for a fix to hidden networks. My routers show my hidden networks as:
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00

Frisbee was not looking for that. Now it does.

If your hidden networks appear as something else (other than blank) please tell me so that I can add that.

I am waiting for @linuxunix to reply in case there is something I can add to handle his/her need to override the DNS addresses. I hope williams2's solution is sufficient.

If not, I will need linuxunix's assistance to test whatever I might come up with. But I don't plan on starting until I am assured of testing support, as I cannot test such a fix, myself.

Richard

williams2 wrote: ↑Sat Jun 18, 2022 9:03 pm

Can Frisbee modify dns alone?

AFAIK, you can do exactly that by configuring your preferred DNS address or addresses in file /etc/resolv.conf.head for example:

Code: Select all

#CloudFlare
nameserver 1.1.1.1
nameserver 1.0.0.1
#IBM Quad9
nameserver 9.9.9.9
#end head

For each url (web page name) this will try each dns nameserver in the list until it finds one that works. dhpc will put a different dns nameserver in /etc/resolv.conf, but the nameservers in /etc/resolv.conf.head will be tried and used first.

The content modified in /etc/resolv.conf will be overwritten by frisbee's automatic update, that is, manual modification is effective, but it will automatically jump back to the default dns address within a few minutes (after a period of time).

You can Google/DuckDuckGo for resolv.conf for more information.

It should be dhcpcd that creates and modifies /etc/resolv.conf.

In the documentation, if resolv.conf is a symlink, then dhcpcd will not overwrite resolv.conf.

AFAIK, every time your network connects and each time it reconnects, dhcpcd modifies resolv.conf. It copies /etc/resolv.conf.head to /etc/resolv.conf, then it puts the nameserver it gets from your isp in resolv.conf
then it copies /etc/resolv.conf.end to resolv.conf

When an app resolves a URL, the nameserver address at the top of resolv.conf is tried first. If that fails, then the next one is tried, until there are none left.

AFAIK, frisbee does not modify /etc/resolv.conf.head.

Your Puppy should use the dns nameserver address at the top of /etc/resolv.conf.head.
{So you put the static dns nameserver address that you want to use at the top of /etc/resolv.conf.head.)
If the file /etc/resolv.conf.head does not exist, then create it.

I am connected using frisbee using the dns nameservers in /etc/resolv.conf.
Which works, or I could not be writing this post.
(except I'm using dnsmasq, which is slightly different.)

The content modified in /etc/resolv.conf will be overwritten by frisbee's automatic update

Yes, that is what dhcpcd is supposed to do.
You put the dns address that you want to use at the top of resolv.conf.head.
Not in resolv.conf.
In resolv.conf.head

williams2 wrote: ↑Wed Jun 22, 2022 3:57 am

You can Google/DuckDuckGo for resolv.conf for more information.

It should be dhcpcd that creates and modifies /etc/resolv.conf.

In the documentation, if resolv.conf is a symlink, then dhcpcd will not overwrite resolv.conf.

AFAIK, every time your network connects and each time it reconnects, dhcpcd modifies resolv.conf. It copies /etc/resolv.conf.head to /etc/resolv.conf, then it puts the nameserver it gets from your isp in resolv.conf
then it copies /etc/resolv.conf.end to resolv.conf

When an app resolves a URL, the nameserver address at the top of resolv.conf is tried first. If that fails, then the next one is tried, until there are none left.

AFAIK, frisbee does not modify /etc/resolv.conf.head.

Your Puppy should use the dns nameserver address at the top of /etc/resolv.conf.head.
{So you put the static dns nameserver address that you want to use at the top of /etc/resolv.conf.head.)
If the file /etc/resolv.conf.head does not exist, then create it.

I am connected using frisbee using the dns nameservers in /etc/resolv.conf.
Which works, or I could not be writing this post.
(except I'm using dnsmasq, which is slightly different.)

The content modified in /etc/resolv.conf will be overwritten by frisbee's automatic update

Yes, that is what dhcpcd is supposed to do.
You put the dns address that you want to use at the top of resolv.conf.head.
Not in resolv.conf.
In resolv.conf.head

There is no resolv.conf.head file, I created it manually, with what you gave above:
#CloudFlare
nameserver 1.1.1.1
nameserver 1.0.0.1
#IBMQuad9
nameserver 9.9.9.9
#end head

But it doesn't work, just create this file manually, but it doesn't work.
The dns written in the resolv.conf.head file has no effect, even after a few minutes.
But writing it in resolv.conf has immediate effect.

The dns written in the resolv.conf.head file has no effect, even after a few minutes.
But writing it in resolv.conf has immediate effect.

I think a new resolv.conf is created every time dhcpcd changes state.
For example, when your network goes down then comes up again.
For my wifi, like this:
rfkill block wlan
rfkill unblock wlan

Or just reboot.

You can check your dns server address at certain web sites.
Google for whats my ip or whats my dns, something like that.

Or you can use nslookup.

Your isp might have external dns addresses blocked, to force you to use their dns server.

Do you have systemd? systemd is a little different.

For Firefox, you can use their encrypted dns.
see: https://support.mozilla.org/en-US/kb/fi ... over-https
That should work, because it uses https, just like this forum web page you are looking at.
This bypasses resolv.conf completely, I think.
But it only works for Firefox.

I have uploaded ".1" versions of simple_network_setup, frisbee and network wizard.

SNS waits a bit longer before before trying a connection, to increase the probability of avoiding the "169.254..." failure to obtain a valid IP address. It also handles better the absence of the 'iw' command.

Network Wizard waits similarly but also logs all dhcpcd operations for the session, instead of only the last use of dhcpcd.

Both Frisbee and Network Wizard now recognize hidden networks identified as hexadecimal zeroes.

In addition, the network_connect_update package default wired ethernet starter waits before connecting, to improve the probability of success.

The update packages are here: https://forum.puppylinux.com/viewtopic.php?p=2241#p2241

Richard

Richard, @rerwin ,
I'm testing sns 3.3.1, and getting a wifi reconnect failure, in /usr/local/simple_network_setup/rc.network

The log is ok up to a certain point:

 wlan1
 SUCCESS: ip link set wlan1 up
 EXECUTING SCAN: iw dev wlan1 scan | grep -E (detail labels)
 SCANRESULT=BSS bc:1a:e4:99:6c:4c(on wlan1)
	freq: 2462
	signal: -63.00 dBm
	SSID: HUAWEI Y9 Prime 2019
 EXECUTING: ip link set wlan1 down

It goes wrong here; see my inserted echo:

    for ONEWANT in $EBSSIDS_WANT; do #211215
        grep -wq "${ONEWANT}" <<< "${TRIED_WANTS}" && continue #211215
        IFS='|' read -r WANTSSID WANTBSS <<< "$ONEWANT" #211215
        while IFS='|' read -r CELL_ADDRESS CELL_FREQUENCY _ CELL_ESSID _; do
            echo "TEST6 CELL_ADDRESS='${CELL_ADDRESS}' CELL_ESSID='${CELL_ESSID}' WANTBSS=${WANTBSS} WANTSSID=${WANTSSID}"
            [ -z "$CELL_ESSID" ] && CELL_ESSID="$WANTSSID"
            if [ "$CELL_ADDRESS" = "$WANTBSS" ] \
              && [ "$CELL_ESSID" = "$WANTSSID" ]; then

which prints out:

TEST5 SRLINES='bc:1a:e4:99:6c:4c|2462|-63|HUAWEI Y9 Prime 2019|'
TEST6 CELL_ADDRESS='bc:1a:e4:99:6c:4c' CELL_ESSID='HUAWEI Y9 Prime 2019' WANTBSS= WANTSSID=HUAWEI
TEST6 CELL_ADDRESS='bc:1a:e4:99:6c:4c' CELL_ESSID='HUAWEI Y9 Prime 2019' WANTBSS= WANTSSID=Y9
TEST6 CELL_ADDRESS='bc:1a:e4:99:6c:4c' CELL_ESSID='HUAWEI Y9 Prime 2019' WANTBSS= WANTSSID=Prime
TEST6 CELL_ADDRESS='bc:1a:e4:99:6c:4c' CELL_ESSID='HUAWEI Y9 Prime 2019' WANTBSS=bc:1a:e4:99:6c:4c WANTSSID=2019
#

...looks like the spaces in the ssid have messed it up.

Richard,
One thing I noticed in rc.network, I commented-out some code, replaced with one line:

#Running?...
# shellcheck disable=SC2009
#ps --no-headers -fC rc.network | grep '/usr/local/simple_network_setup' | grep -qvw "$$" \
#  && sleep 5 \
#  && ps --no-headers -fC rc.network | grep '/usr/local/simple_network_setup' | grep -qvw "$$" \
#  && exit 1 #210209
pidof -o ${$} rc.network && exit 1

I presume that you want to test if the script is already running. I haven't tested my replacement, and perhaps it won't work if there is a different script running with the same name -- which would be unlikely.

Richard,
This fixes rc.network, see my changes "#BK":

    TRIED_WANTS=''  #211215
    echo "TEST5 SRLINES='${SRLINES}'"
    #for ONEWANT in $EBSSIDS_WANT; do #211215 #BK
    echo "$EBSSIDS_WANT" > /tmp/EBSSIDS_WANT #BK
    while read -r ONEWANT <&4 ; do #BK
        echo "TEST5b ONEWANT='${ONEWANT}'"
        grep -wq "${ONEWANT}" <<< "${TRIED_WANTS}" && continue #211215
        IFS='|' read -r WANTSSID WANTBSS <<< "$ONEWANT" #211215
        while IFS='|' read -r CELL_ADDRESS CELL_FREQUENCY _ CELL_ESSID _; do
            echo "TEST6 CELL_ADDRESS='${CELL_ADDRESS}' CELL_ESSID='${CELL_ESSID}' WANTBSS=${WANTBSS} WANTSSID=${WANTSSID}"
            [ -z "$CELL_ESSID" ] && CELL_ESSID="$WANTSSID"
            if [ "$CELL_ADDRESS" = "$WANTBSS" ] \
              && [ "$CELL_ESSID" = "$WANTSSID" ]; then
                find_connection_profile_and_extract_content || continue #210201
                echo "TEST7 SEC_MGMT='${SEC_MGMT}'"
                RUNWPASUPP='no'
                case "${SEC_MGMT:0:3}" in #210207...
                  WPA) RUNWPASUPP='yes' ;;
                  NON) [ -n "$SEC_KEY" ] && RUNWPASUPP='yes' ;; #WEP
                esac
                spoof_macaddress '   EXECUTING: ' >> /tmp/simple_network_setup/rc_network_wireless_connection_log #If using real MAC, spoof it #211215
                ip link set "$INTERFACE" up #210202
                local RC=$? #170301
                echo "     RESULT=$RC FOR: ip link set $INTERFACE up" >> /tmp/simple_network_setup/rc_network_wireless_connection_log #170301 210202
                if [ $RC -eq 0 ]; then #170301
                    sleep "${SECS}".1 #210205
                    local wCNT=0
                    if [ "$RUNWPASUPP" = "yes" ]; then
                        run_wpa_supplicant || continue 2 #210211
                    elif [ -z "$SEC_MGMT" ]; then
                        iw dev "$INTERFACE" connect "${CELL_ESSID}" "$CELL_FREQUENCY" "$CELL_ADDRESS" #210202
                    fi
                    start_wireless_connection #exits if connection successful
                    reset_macaddress >> /tmp/simple_network_setup/rc_network_wireless_connection_log #Unsuccessful, so undo spoofing #211215
                fi 
            fi 
        done <<< "$SRLINES"
        TRIED_WANTS="${TRIED_WANTS}${ONEWANT} " #211215
    done 4</tmp/EBSSIDS_WANT #BK
} #initiate_wireless_connection

Nested read loops require using different file descriptors.

In EasyOS, there is /etc/rc.d/rc.network_basic, which starts with this:

#echo "Setting up interface lo..."
ifconfig lo 127.0.0.1
route add -net 127.0.0.0 netmask 255.0.0.0 lo

I'm behind the times here, unfamiliar with the 'iw' utility.
Appreciate if someone could someone advise me how to replace that ifconfig with iw?

Also, I want to exit the script if "lo" is already up. can 'iw' be used to detect that?

@rerwin ,
I found a bug if the distro has busybox pgrep.

/usr/sbin/connectwizard is ok, it has a comment to avoid "-d" because busybox pgrep doesn't support it.

However, connectwizard_exec has "pgrep -fd ..." and pgrep fails.

Just noting this. I have fixed it in EasyOS by changing to the full pgrep in the procps package.

I have posted to my blog about the pleasant experience using SNS:

https://bkhome.org/news/202309/the-retu ... nager.html

Richard,
The udev rule in SNS doesn't work; build_udevmodulelist never gets called.

I have removed both files, and modified /usr/local/simple_network_setup/rc.network (renamed to rc.snsnetwork) to not require them.

Easy has an enhanced pup_event that supports delaying any of the scripts in /etc/init.d until a particular event has occurred. /etc/init.d/rc.network is called with "start" after X has started (rc.network then calls default_network_connect), giving the kernel network drivers plenty of time to load, so don't think there is any need to wait for them.

@BarryK,

Thank you for telling me of the SSID bug and your solution, as well as the other suggestions and fixes.

I now have an update to work on.

Regarding my avoidance of 'pidof', I found that it did not always work for me. The situation I addressed was where a user right-clicks the tray icon to disconnect, then clicks again to reconnect. Sometimes the old SNS instance was detected. I was also concerned that while a user changes managers from Network Wizard to SNS, pidof might see the NW rc.network but report that SNS was already running, which your renaming to rc.snsnetwork resolves.

And thank you for adopting the Puppy SNS (with mods) for EasyOS. The code rework was my Covid-lockdown project.

Richard

i have fossapup64-9.5.
i installed sns-3.3.1.pet by changing users to 777
, as i have lost my changed spot password.
no network or interfaces displayed, tho they exist.
dell optilux 3060 4GB, 256GB
Ralink Technology, Corp. MT7601U Wireless Adapter - working.

, as i have lost my changed spot password.

You can change a user password as root.
Just open a terminal and type

passwd spot

boof,

You may have to install the sns package as /root. That is is only way I have done it.

If you installed under spot, I'd be curious what running sns from a console would show as to messages.

Richard

Uploaded SNS version 3.4 in the first message of this thread.

It contains compatibility changes for EasyOS, and other small changes. Details in the third message of the thread.

Tested in XenialPup, FossaPup, FossaPupCE, BookWormPup, S15Pup, JammyPup32, VoidPup, EasyOS-5.5.4.

Tested with Broadcom b43, ath9k, e1000e, forcedeth driver modules. Uses new udev rule for module detection -- Please tell me of any drivers that are not detected.

The minor operational differences are that "Puppy" and "Barry's" are absent from message text, and that for wifi setup the passphrase can be omitted if it is already in a connection profile.

As usual, please report here any regression issues.

Richard

See ozsouth's post here, https://www.forum.puppylinux.com/viewto ... 07#p114607

@rerwin

Thank you once again for the updates/solutions to internet connectivity

In regards to 'pop-up / dialogue' boxes

viewtopic.php?p=118142#p118142

I have installed and working perfectly on JammyPup (JRB) the combo of (Conman dropped in favour of PeasyWifi) :

peasywifi_4.9

network_connect_update-20240425

Upon boot up there are two small dialogue boxes which 'pop-up' to display 'connecting and wifi connected (?)'

Once the connection is made both close automatically with no intervention.

On a second PC (Fossapup64-95) the combination is:

frisbee-2.0.4

network_connect_update-20240425

This shows Dunst desktop notifications informing me of acquiring/acquired connections or 'dropped'.

rerwin wrote: ↑Mon Aug 10, 2020 5:16 pm

Newest packages: , Network_connect_update 20240602 (6/2/24), NetWiz 3.0.2 (5/30/24), SNS 3.5.1 (4/25/24), Frisbee 2.0.4 (4/21/24)

......

You might want to make an adjustment to the link. Instead of this:

https://archive.org/download/Puppy_Linux_Rerwin_Repository/simple_network_setup-3.5.1.pet

I get this link in my FF browser, which doesn't work:

https://archive.org/download/Puppy_Linux_Rerwin_Repository/simple_network_setup-3.5.1.pet%5Burl%5D%5B/list%5D%0A%5Blist%5DSimple_network_setup-3.5:%20%20%5Burl%5Dhttps://archive.org/download/Puppy_Linux_Rerwin_Repository/simple_network_setup-3.5.pet

Would it work better without the forum markup tags?
Thanks.

Governor wrote: ↑Sun Jun 09, 2024 1:59 pm

rerwin wrote: ↑Mon Aug 10, 2020 5:16 pm

Newest packages: , Network_connect_update 20240602 (6/2/24), NetWiz 3.0.2 (5/30/24), SNS 3.5.1 (4/25/24), Frisbee 2.0.4 (4/21/24)

......

You might want to make an adjustment to the link. Instead of this:
https://archive.org/download/Puppy_Linu ... -3.5.1.pet

I get this link in my FF browser, which doesn't work:
https://archive.org/download/Puppy_Linu ... up-3.5.pet

Would it work better without the forum markup tags?
Thanks.

This url works for SNS v3.5.1: https://archive.org/download/Puppy_Linu ... -3.5.1.pet
edit: indeed the link on top of first post does not.

thank you, @rerwin , for these updates.