Ubuntu ground station? #372
-
|
Hi, I installed WFB-NG as a ground station on a Debian-based OS (Ubuntu) and it seems my installation was successful. No errors, and I installed wfb-ng using the
For the "vehicle" side of this, I'm using the normal wfb image on a Pi4. I've used this successfully with a ground station that is running the same Pi image (configured for GS obviously). What I'd like to do is connect to that using this Ubuntu machine, but I'm not getting a connection. I assume that what I'm trying to do is actually possible, and would appreciate any insights into what I need to do to make that happen. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 17 replies
-
|
please run |
Beta Was this translation helpful? Give feedback.
-
|
run |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I think these look right except for ...GS side: |
Beta Was this translation helpful? Give feedback.
-
|
Try to run |
Beta Was this translation helpful? Give feedback.
-
|
I ran |
Beta Was this translation helpful? Give feedback.
-
|
See two things:
|
Beta Was this translation helpful? Give feedback.
-
|
I'm new to tcpdump, learning as fast as possible. :-)
I am seeing a lot of what I thought were remote packets, whose frequency
values correspond to the channel I'm using (165, 5825Mhz). But they appear
on the GS side whether or not the drone is even turned on. The majority of
the items in the output look like this:
```
23:37:50.204817 6.0 Mb/s 5825 MHz 11a -82dBm signal -89dBm noise 41 sq
antenna 0 Beacon () [6.0* 9.0 12.0 18.0 24.0* 36.0 48.0 54.0 Mbit] ESS,
PRIVACY
23:37:50.204834 6.0 Mb/s 5825 MHz 11a -82dBm signal -90dBm noise 35 sq
antenna 0 Beacon () [6.0* 9.0 12.0 18.0 24.0* 36.0 48.0 54.0 Mbit] ESS,
PRIVACY
```
I don't see anything in the output that suggests that it's a local inject,
but again, I'm new to tcpdump so I'm not sure.
When I use a pi image for the ground station, I'm able to ssh into it and
ping 10.5.0.2 and get a response. That does not happen here, even though
`gs-wfb` on the ground station side has the same 10.5.0.1 IP address and
the drone side's `drone-wfb` interface is 10.5.0.2. What would I need to do
to get that to work?
Thanks,
Kelly
…On Thu, Sep 26, 2024 at 6:05 AM Vasily Evseenko ***@***.***> wrote:
See two things:
1. that local injects exists (at least tunnels should inject keepalive
packets)
2. that remote packets exists (if not, see freq channels of any
captured packets - they should be equal to your channel)
—
Reply to this email directly, view it on GitHub
<#372 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA42DTPG5TKVZHO27HPDEZTZYPTBPAVCNFSM6AAAAABOZNV2QOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZWGIZDINI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
This is announces from some wifi AP. |
Beta Was this translation helpful? Give feedback.
-
|
I appreciate the help in any case. It's hard to debug when I'm sitting
right in front of it. :-)
The only difference I can discern between the reference image and my image
is the contents of /etc/wifibroadcast.cfg. With the one from the pi GS
image in place, I seem to be getting more data packets (I assume: They're
different than the announce packets and contain data), but wfb-cli gs still
says "Link Lost". I'm down to reading the source code now. :-)
…On Fri, Sep 27, 2024 at 9:09 AM Vasily Evseenko ***@***.***> wrote:
This is announces from some wifi AP.
If it works with pi image as GS then need to find what is difference with
your image and reference pi image. It is very hard to debug it by email
—
Reply to this email directly, view it on GitHub
<#372 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA42DTNWQOPYVNXBPC6ZJ6LZYVRJRAVCNFSM6AAAAABOZNV2QOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZXGYZTQMA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Still looking for differences between my image and the ref image. Here is the output from My image: The drone: Reference image on the pi GS: From this (and looking at ...at the bottom of the output when checking the status of the wfb service on the drone when it's connected to the pi image. Does any of this help understand what's going on? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
For me the most probable variant is (3) and then may be (1) |
Beta Was this translation helpful? Give feedback.
-
|
So I switched to a different adapter, now using the same one I use on the Pi reference image that is known to work well (I was using an ALFA AC600 before). Re-installed wfb 23.08 (since that matches the version found on the drone) with the new adapter. With this new adapter, I notice that One thing I notice: If I run
|
Beta Was this translation helpful? Give feedback.
-
|
FWIW, I just adjusted |
Beta Was this translation helpful? Give feedback.
-
|
Encryption keys mismatch. See below |
Beta Was this translation helpful? Give feedback.
-
|
txpower |
Beta Was this translation helpful? Give feedback.
-
|
Something else I see that's new: In |
Beta Was this translation helpful? Give feedback.
-
|
This means that gs.key and drone.key doesn't match. Regenerate them using |
Beta Was this translation helpful? Give feedback.
-
|
It's working!!! Thank you so much for your help. 👍 |
Beta Was this translation helpful? Give feedback.
This means that gs.key and drone.key doesn't match. Regenerate them using
wfb-keygen