Sorry, poor wording on my part, you are correct, Wally. My 'testing' was on the 'public' wifi at work ( what we were to use for personal equipment, (personal cellphones, personal laptops & tablets, etc)) not the 'corporate' network. Today, the 'corporate' network has certificate authentication, and cannot be accessed by anything but 'authorized' equipment, controlled by certificates installed by IT, on controlled VLANs, and so many other layers of security it isn't funny...
Even if those layers of protection aren't there at work, you should always find out what the policies are, and follow them.
I also don't count on those layers in public wifi (I pretend they aren't there) and now use VPN when possible, or never have 'personal data' on any device I connect to a public wifi. My cellphone and table both are VPN'd to my home first, before going anywhere else... The tablet is used for 'casual surfing' and does not have any personal info, accounts or passwords on it and it gets wiped (factory reset) regularly.

Kevin -- KD9EFV

开云体育

Before you do anything on a business network, you better have permission or you maybe flagged as a bad actor trying to break into to the network. Better be safe than sorry!

? Thank you Kevin? this helps....? Not sure to be honost,? yrs back we hired a IT company to handle everything....? There is very lil we can do other than get to the internet...and run the programs we normally use.? We do use team viewer to let outside techs get into our pc's and equipment...? ? Unless I can get hotspot to work for me then I'm probably out of luck and not worth rocking the boat on this topic.... .? ?
Thanks? ?Dave? 73??

Issues with work wifi in a corporate environment: They may have peer-to-peer turned off or disabled, which means one device on the wifi may not be able to talk to another device on the wifi, even though they can get out to the internet. If so, you wouldn't be able to VNC to the Pi. Can your work PC ping the Pi connection? Can you temporarily hook a keyboard and monitor to it just to see what's going on? I have a script on my Pis that emails me the IP address every hour to my gmail account This helps confirm that it connects to the wifi, and that it has internet. When in my corporate network it still works, but a laptop connected to the same wifi can't talk or ping the Pi. I _CAN_ use something like TeamViewer, or the paid version of RealVNC to connect, though because the Pi connects to the Internet server for the TeamViewer or RealVNC, and my laptop can connect to the server, too, and it connects me to the Pi... A few coffee shops and fast food restaurants have this kind of security, too, which helps prevent local attacks and packet sniffing...

Kevin -- KD9EFV

? ?God morning all....? Well once I got the monitor set up properly all work fine both the 4b and the 3b......

On a different note when I did the build a on Saturday..? ?I had the "app hamclock."...? I also remember seeing it in the KM4ACK github page........
once I redid the build a pi Sunday I did not see it?? ?Did I miss something or was It removed for some reason.? ???
Thanks? Dave KF0EXO? ? 73

I also brought the pi to work to show off...lol....? ?However I was not able to connect via VNC.....? ?Can someone point me in a direction to look....? I am sure its a IP issue tho not exactly sure how to go about this???? My work does have wifi and I am pretty sure I have the IP address..............? ? ? Even if hotspot was configured I dont think it would work due to there is wifi present???
Any advice will be greatly appreciated.......
Thanks again to all who put so much effort into this project!!
73

Yes flrig is running . ? Might just try a new install of BAP ??

Jason- does he have FLrig running?

Great question & I assume so. He said FLRIG was running correctly.

--

Jason- does he have FLrig running?

Good morning all...? ?Well i decided to redo the whole build a pi install being more attentive to country code and after the install all went great... wifi work right away and vnc connected right away...ok so I get to the end of what I planned to install I followed thru with moving all the data to the SSD drive.... I put the case all together and went to bed... next day I go to boot uo the pi and got turned on the VNC? .... I got the display of? "cannot show desktop at this time"...? Not sure what happen or if I missed a step???? I also used the same SD card to boot up the other PI 3b I have..... I got the same response from the PI3b....???? any ideas where I went wrong??? I will dig into this more when I get home by asctually attaching a HDMI monitor to both...???
? Maybe just the VNC was having issues???? ? ?

I was running the monitor off grid seeing it was the only way to power it and my battery box needed a full recharge....? ? hence I didnt try it...
Thanks to all !!! 73? ? ?Dave KF0EXO

As long as the radio is on USB-D, you should be good. If you have a second radio, monitor the frequency and you should hear the digital data burst being sent by your Pi. You may find this video helpful when trying to make your first Winlink connections https://youtu.be/8iaDidw2Jgg
--

BTW, I've used both ethernet and wifi during testing, and no ethernet, and it doesn't matter in my testing... Most of my Pis are headless ( too expensive to have 15-20 monitors, or even KVM switched <grin> ). Most of my regular use Pis are set with static IPs from the router/dhcp server on both the Ethernet and WiFi macs, so I don't need to use things like AngryIP Scanner. They are all on their own subnet, on their own VLAN for the most part, but that is beyond the skill set of most users...

Kevin -- KD9EFV

I just tested again, Both 32 bit Buster and 32 bit Bullseye dated Jan 2022 from RaspberryPi.com
I added ssh.txt and wpa_supplicant.conf to the boot partition prior to putting in my RPi4-8GB (with Argone One V2 case)
It booted up normally in both cases. I then did the sudo apt update && sudo apt upgrade -y in both Buster and Bullseye setups (in case either replace the existing /boot/config.txt during updates)
I modified /boot/config.txt, adding dtoverlay=disable-wifi as the last line, in both situations, and rebooted multiple times.
The WLAN0 is not listed in any reboot.
I then inserted the Wifi dongle. It shows up as WLAN0, shows in command lsusb
I then rebooted and tested again, multiple times, and only WLAN0 (the dongle) shows up. This was tested on both the Buster and Bullseye, multiple times. I also tested with a Pi3B+, same setups, same modified /boot/config.txt, same results. It's weird that yours brings back the
on board WiFi, as I cannot reproduce it.

Kevin -- KD9EFV

Hi

I am attempting a new build of both Buster and Bullseye with a date

of 1-28-22 I think, at least in Jan of 2022. On buster it loads and works good, but

when attempting to use BAP it has notices of not being updated any further and I

think in my case at least it failed to much.

With Bullseye I believe 32 Bit I am getting a failure in the beginning of GTK, and I

did save the error message and put it in a file on a disk then copied over it. I can

get the error message but has anyone else seen this occurrence? The git of BAP then

is hung up.

Marty kd8bj

Hi Kevin

I tried out, as you described with a fresh install. I added?dtoverlay=disable-wifi as last line to config and rebooted. After reboot I typed ip a and wlan0 was still present. So I shut down the raspi and started new. Now pi a showed no wlan interface. I connected the dongle. ip a now showed again wlan0, I rebooted again, the raspi connected to my network, I typed again ip a and the list showed wlan0 and wlan1 again. So actually I do not know, which adapter is used

klaus, DC2JR?

开云体育

The original purpose of the RPi was as a low-cost computer to introduce school age children to what many refer to as 'hands-on computing", with additional hardware to make the boards appeal to industrial designers to incorporate the RPi into their products, thus increasing demand, and enabling economy of scale savings to kick in, lowering the cost of the boards, allowing more children to get their hands on them.

Should that be on the radio usb-d ??
The radio will ptt on usb data but I can’t make any connection with any station to send a email ,or should the Pat set up be configured to usb-d ??

If you use a wpa_supplicant.conf file, it must have a country= line in it.
If you set up WiFi in raspi-config, be SURE to enable Localization, WLAN-Country,
If you don't do either, there is a programthat will run, called rfkill, that looks for theountry setting, and disables wifi if it doesn't find it.
This is to prevent the system from using inappropriate wifi channels/frequencies depending on which wifi chipset you have, and what country you are in.

Everything appears to be configured correctly with maybe one exception. After pressing "connect" in the Pat Inbox, what mode is your radio in (USB or USB-D?) It should probably be in USB-D. Educated guess as I don't have a 991 to test with.

--