Date   

Re: Beginner Questions: spyserver config

Joe M.
 

Experience. Of course, I still find the PCs I purchase nearly all have serial ports despite people telling me they have not been available for over 10 years on a PC (purchase quantity over the past 10 years is approaching 100 if not more). The only exceptions to this are a Surface tablet).

Have you tried it?

Nearly any device that requires an IP to be set has a default. I always set it by connecting a PC to it, set it as needed, then put that PC back on my network and connect the new device. That tactic has yet to fail.

When you connect two PCs direct to each other, one will act as a DHCP server and assign an IP to the other. I can't say the RPi does this, but I seem to recall that it will.

I do know of at least one bug on the RPi. For the VNC server, if you clone the SD card then change the RPI's IP, the VNC Server will still only respond to the original IP. Even the Real VNC people don't have an answer for that one.

Joe M.

On 2/20/2019 5:11 PM, Tom Snyder wrote:
On what do you base your statement of: "Most PCs will auto-configure so
the crossover is not needed", I've never seen any literature to support.

------------------------------------------------------------------------
*From:* main@airspy.groups.io <main@airspy.groups.io> on behalf of Joe
M. <mch@nb.net>
*Sent:* Wednesday, February 20, 2019 09:40
*To:* main@airspy.groups.io
*Subject:* Re: [airspy] Beginner Questions: spyserver config
Most PCs will auto-configure so the crossover is not needed.

But if the correct IP is not used, it will not matter if they are
connected by a wet noodle.

Joe M.

On 2/20/2019 12:29 PM, Tom Snyder wrote:

I think you need a crossover ethernet cable for communication to take
place. Or use a hub. A straight ethernet cable means talk is connected
to talk and listen is connected to listen. You need talk-listen and
listen-talk.

------------------------------------------------------------------------
*From:* main@airspy.groups.io <main@airspy.groups.io> on behalf of Joe
M. <mch@nb.net>
*Sent:* Wednesday, February 20, 2019 09:21
*To:* main@airspy.groups.io
*Subject:* Re: [airspy] Beginner Questions: spyserver config
Yes, it does. Connect to the IP of the RPi.

It will likely be a 192.168.x.x address. Port 5555.

You will enter that in the format 192.168.x.x:5555

Joe M.

On 2/20/2019 10:47 AM, Ken Alexander wrote:
Spyserver is running on a Raspberry Pi.

SDR# is running on a Windows laptop.

They are connected by a short ethernet cable.

Does that change how things should be set?



<http://www.avg.com/email-signature?utm_medium=email&;utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free.www.avg.com <http://www.avg.com>;
<http://www.avg.com/email-signature?utm_medium=email&;utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>



Re: Beginner Questions: spyserver config

Tom Snyder
 

On what do you base your statement of: "Most PCs will auto-configure so the crossover is not needed", I've never seen any literature to support.


From: main@airspy.groups.io <main@airspy.groups.io> on behalf of Joe M. <mch@...>
Sent: Wednesday, February 20, 2019 09:40
To: main@airspy.groups.io
Subject: Re: [airspy] Beginner Questions: spyserver config
 
Most PCs will auto-configure so the crossover is not needed.

But if the correct IP is not used, it will not matter if they are
connected by a wet noodle.

Joe M.

On 2/20/2019 12:29 PM, Tom Snyder wrote:
>
> I think you need a crossover ethernet cable for communication to take
> place.  Or use a hub.  A straight ethernet cable means talk is connected
> to talk and listen is connected to listen.  You need talk-listen and
> listen-talk.
>
> ------------------------------------------------------------------------
> *From:* main@airspy.groups.io <main@airspy.groups.io> on behalf of Joe
> M. <mch@...>
> *Sent:* Wednesday, February 20, 2019 09:21
> *To:* main@airspy.groups.io
> *Subject:* Re: [airspy] Beginner Questions: spyserver config
> Yes, it does. Connect to the IP of the RPi.
>
> It will likely be a 192.168.x.x address. Port 5555.
>
> You will enter that in the format 192.168.x.x:5555
>
> Joe M.
>
> On 2/20/2019 10:47 AM, Ken Alexander wrote:
>> Spyserver is running on a Raspberry Pi.
>>
>> SDR# is running on a Windows laptop.
>>
>> They are connected by a short ethernet cable.
>>
>> Does that change how things should be set?
>
>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>        Virus-free. www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>




Re: Beginner Questions: spyserver.config

Brian Gregory <bdgregory@...>
 

I would recommend changing
bind_port = 5555-6666
to just a single number of your choice so that you know for certain what port will be used and can set up your router to forward that port inward to your Spyserver.
5555 is the normal value but as far as I know you can pick any number between 1024 and 65535.


On Wed, 20 Feb 2019 at 11:36, Ken Alexander <ve3hls@...> wrote:
If all you see are 192.168.x.x numbers you cannot be reached from outside. Those 
are among the three sets of unroutable internet addresses. 172.16.x.x through 
172.31.255.255 and 10.x.x.x are also unroutable. The self-assigned addresses, 
169.254.0.0 to 169.254.255.255, also do not route to the Internet. 

No, sorry.  I was just using 192.168.xx.xx as an example of the types of number I've seen before.  They didn't appear in anything I was trying today.  spyserver.config came preset with  "bind_host = 0.0.0.0" .  I figured that was just a placeholder and not an actual address, but Prog said to use it.

Ken Alexander
So Phisai, Thailand
Blog:  bueng-ken.com


On Wed, Feb 20, 2019 at 11:09 AM jdow <jdow@...> wrote:
If all you see are 192.168.x.x numbers you cannot be reached from outside. Those
are among the three sets of unroutable internet addresses. 172.16.x.x through
172.31.255.255 and 10.x.x.x are also unroutable. The self-assigned addresses,
169.254.0.0 to 169.254.255.255, also do not route to the Internet.

{^_^}

On 20190219 23:50:15, Ken Alexander wrote:
> Thank you!
>
> So those numbers work then?  I thought maybe they were just placeholders. 
> Usually I see things like 192.168.xx.xx.  Port numbers, I know nothing.  Maybe
> less than nothing!  😜
> I'll give those numbers a try, right after I read that article!
>
> Thanks again!
>
> Ken Alexander
> So Phisai, Thailand
> Blog: bueng-ken.com <http://bueng-ken.com>
>
>
> On Wed, Feb 20, 2019 at 7:43 AM prog <info@...
> <mailto:info@...>> wrote:
>
>     On Wed, Feb 20, 2019 at 08:40 AM, Ken Alexander wrote:
>
>         I know they have something to do with networks but beyond that I'm
>         completely lost.
>
>     Nobody is expecting you to be expert in everything involved in the SpyServer.
>     The golden rule is: If you don't understand something, then leave it to the
>     default.
>     But learning is always good:
>     https://www.eetimes.com/document.asp?doc_id=1275967
>
>






iz5dkm@...
 

Hi Dave, I am also part of an astronomical observatory, Tavolaia astronomical observatory. http://www.cielisutavolaia.com/
Recently we have built a B0329 + 54 pulsar reception system, the data is public and available at this web address: https://drive.google.com/drive/folders/1yWSp668w82duEwZrNCzZZ8WrG7fRqYMG
3D corner antenna in drift scan, rx airspy R2, BW 10 MHz, IW5BHY software.
'73, Andrea, IZ5DKM.


David Eckhardt
 

There are actually a fair number of us doing RA with the AirSpy.  That SDR is the center of our receiver at the Little Thompson Observatory
 in Berthoud, Colorado, USA (starkids.org).  I'd encourage you to have a look at our site.  We do both optical and radio astronomy.  We have
a system somewhat similar to yours, but have managed to capture and record raw I/Q data for an 8-MHz wide display utilizing a Russian "hack" to the
SDR# code.  Our STEM project for this past year was to determine the temperature of the hydrogen clouds surrounding the center of our galaxy, SAGA*.
Fortunately, we have a volunteer who is good at fitting Gaussian curves to a big 'bump' to separate out multiple Gaussian curves to an otherwise
unresolved big "bump" in the data.  We are using Radio SkyPipe to record the analog data directly (for show-and-tell during our puplic star nights)). 
Our feed is a full-wavelength loop spaced 1/4-wavelength in front of a splash plate built by our students.  Most of our hardware is from
MiniCircuits as we have another volunteer is has an "in" with them(professionally).  By the looks of your data, you're doing pretty good. 

If we can be of any assistance, please email us at the Observatory and or myself.  We'll be glad to share successes and failures.

Dave - WØLEV
Volunteer:  Little Thompson Observatory
                  <starkids.org


On Wed, Feb 20, 2019 at 8:48 PM <iz5dkm@...> wrote:
hi guys, in this my first message I would like to revive this topic to find out how many people are interested in radio astronomy.
I am an Italian radio amateur who is dedicated to finding practical solutions in this fascinating field.
Unfortunately, my software skills are modest and this will require the support of you experts.
A two-year acquisition on the hydrogen line in SGR A, 400 cm satellite dish, self-built feed, self-built preamplifier, rx airspy mini, astrospy software, signal acquired in 10 minutes.



--
Dave - WØLEV
Just Let Darwin Work
Just Think


iz5dkm@...
 

hi guys, in this my first message I would like to revive this topic to find out how many people are interested in radio astronomy.
I am an Italian radio amateur who is dedicated to finding practical solutions in this fascinating field.
Unfortunately, my software skills are modest and this will require the support of you experts.
A two-year acquisition on the hydrogen line in SGR A, 400 cm satellite dish, self-built feed, self-built preamplifier, rx airspy mini, astrospy software, signal acquired in 10 minutes.


Re: Beginner Questions: spyserver config

Martin Smith
 

On Wed, Feb 20, 2019 at 05:30 PM, Ken Alexander wrote:


which is connected to my Pi with an ethernet cable.
So is the connection that you have ?
Raspberry pi<---- ethernet cable ----> Windows PC
Or is it
Raspberry pi<---- ethernet cable ---->broadband router<--- ethernet cable ---> Windows PC

The first setup would be unusual and mean that neither device would by default be assigned an IP address. A private static IP address would manually need to be configured on each machine and a static route manually added to each machines routing tables ("netstat -rn" to view the current routing tables) to enable packets to transfer across the cable. It would not be a typical configuration. (search for "how to add static route in linux permanently" and "how to add static route in windows permanently", if that is the option that you want to use and you really should learn a bit more about networking to understand why and what you are actually doing.). Another less slightly complex way would be to manually configure a DHCP server on the Raspberry pi and have it automatically configure the windows machine when connected, but a private network range different than any used on the PC would need to be used, and windows may get confused if not done exactly. Search for "how to connect to a raspberry pi directly with an Ethernet cable" and be prepared to screw up a few times, Either way would not be trivial to configure for a beginner.

The second scenario would be the typical configuration for the vast majority of people. The broadband router which is running a DHCP (dynamic host configuration protocol) service would automatically allocate each device that was connected a unique IP address along with a subnet mask, default router, a network address and a broadcast address. And you can connect to your router typically through a web interface and find out what IP addresses have been allocated.

Lets keep this very simple, what what way are your network cables connected ? and
1 On your windows PC what is the value for "IPv4 Address" ?
open a command terminal by pressing the windows key and r at the same time, then cmd.exe and hit the enter key and in the command terminal type "ipconfig" and hit enter.
2 On the Raspberry Pi what is your inet for eth0
Open a shell/xterm/terminal and type "/sbin/ifconfig -a" and hit enter.

Without knowing what your setup actually is no one can really help you.


Re: Beginner Questions: spyserver config

Joe M.
 

Most PCs will auto-configure so the crossover is not needed.

But if the correct IP is not used, it will not matter if they are connected by a wet noodle.

Joe M.

On 2/20/2019 12:29 PM, Tom Snyder wrote:

I think you need a crossover ethernet cable for communication to take
place. Or use a hub. A straight ethernet cable means talk is connected
to talk and listen is connected to listen. You need talk-listen and
listen-talk.

------------------------------------------------------------------------
*From:* main@airspy.groups.io <main@airspy.groups.io> on behalf of Joe
M. <mch@nb.net>
*Sent:* Wednesday, February 20, 2019 09:21
*To:* main@airspy.groups.io
*Subject:* Re: [airspy] Beginner Questions: spyserver config
Yes, it does. Connect to the IP of the RPi.

It will likely be a 192.168.x.x address. Port 5555.

You will enter that in the format 192.168.x.x:5555

Joe M.

On 2/20/2019 10:47 AM, Ken Alexander wrote:
Spyserver is running on a Raspberry Pi.

SDR# is running on a Windows laptop.

They are connected by a short ethernet cable.

Does that change how things should be set?



<http://www.avg.com/email-signature?utm_medium=email&;utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free. www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&;utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


Re: Beginner Questions: spyserver config

Tom Snyder
 


I think you need a crossover ethernet cable for communication to take place.  Or use a hub.  A straight ethernet cable means talk is connected to talk and listen is connected to listen.  You need talk-listen and listen-talk.


From: main@airspy.groups.io <main@airspy.groups.io> on behalf of Joe M. <mch@...>
Sent: Wednesday, February 20, 2019 09:21
To: main@airspy.groups.io
Subject: Re: [airspy] Beginner Questions: spyserver config
 
Yes, it does. Connect to the IP of the RPi.

It will likely be a 192.168.x.x address. Port 5555.

You will enter that in the format 192.168.x.x:5555

Joe M.

On 2/20/2019 10:47 AM, Ken Alexander wrote:
> Spyserver is running on a Raspberry Pi.
>
> SDR# is running on a Windows laptop.
>
> They are connected by a short ethernet cable.
>
> Does that change how things should be set?




Re: Beginner Questions: spyserver config

Ken Alexander
 

Sorry.  127.0.0.5 was a typo.  It always was 127.0.0.1.


On Wed, Feb 20, 2019 at 2:39 PM Martin Smith via Groups.Io <martin_z_smith=yahoo.ie@groups.io> wrote:
On Wed, Feb 20, 2019 at 11:08 AM, Ken Alexander wrote:

>
> back to 127.0.0.5 and changed bind_port to 555
>
127.0.0.5 is not the loopback address (127.0.0.1 is the default loopback address). And historically any port number lower than 1024 requires root access for a process to bind to under most UNIX distributions. Running any process as root while bound to a port is considered a much much higher security risk than running any process as user account of some description.

If you bind any process to a port on the loopback address, then for security only local programs physically running on that machine can access that port on the loopback address. loopback addresses are not remotely accessible across a network they are local to the machine. You should use the default bind_host of 0.0.0.0 which will bind the process to the loopback address AND the network accessible address of the machine. If you only want your spyserver accessible locally on your home network then do not enable port forwarding on your home router for that port and also set "list_in_directory = 0" in the spyserver.config file.




Re: Beginner Questions: spyserver config

Ken Alexander
 

No.  I can't envision a scenario where I would want to do that.  I'd just plug my Airspy into my computer and start SDR#.

Google "loopback address"

On Wed, Feb 20, 2019 at 2:39 PM Martin Smith via Groups.Io <martin_z_smith=yahoo.ie@groups.io> wrote:
> SDR:// 127.0.0.1:5555 ( http://127.0.0.1:5555 )
127.0.0.1 is called the loopback address, you could think of it as a short hand for the machine that you are sitting in front of and physically typing on.
So the question for you would be, is Spyserver running on the same windows machine that SDR# is running on ?




Re: Beginner Questions: spyserver config

Ken Alexander
 

127.0.0.1:5555 is what was set up already in SDR# on my Windows laptop, which is connected to my Pi with an ethernet cable.

Spyserver, running on my Pi is set to 0.0.0.0 and for ports it says 5555-6666, which I assume means...well, I don't really know what it means.

Trying to connect results in the Error message I already posted.

If I change the setting in SDR# from 127.0.0.1 to 0.0.0.0 to match what is set in spyserver.config I still get an Error message.  See the attachments in a previous post.

Setting 127.0.0.1 in both spyserver.config AND in SDR# gives me the same error message.

There are only so many possible combinations here.  I've tried them all and nothing works.

This ought to be really simple and I don't understand why it's not working.

Ken

On Wed, Feb 20, 2019 at 2:39 PM <hmarais@...> wrote:
Replace 127.0.0.1 with the IP address of the Raspberry PI when connecting from SDR#. Leave bind_host as 0.0.0.0 in the Spyserver config on the Raspberry PI.


Re: Beginner Questions: spyserver config

Joe M.
 

Yes, it does. Connect to the IP of the RPi.

It will likely be a 192.168.x.x address. Port 5555.

You will enter that in the format 192.168.x.x:5555

Joe M.

On 2/20/2019 10:47 AM, Ken Alexander wrote:
Spyserver is running on a Raspberry Pi.

SDR# is running on a Windows laptop.

They are connected by a short ethernet cable.

Does that change how things should be set?


Re: Beginner Questions: spyserver config

Ken Alexander
 

Spyserver is running on a Raspberry Pi.

SDR# is running on a Windows laptop.

They are connected by a short ethernet cable.

Does that change how things should be set?  There were no instructions provided so I have to rely on the group, and sorry to say but I'm a lot more confused than I was when I started.

Thanks, but I've barely be at this a week.  Maybe you could pretend you're talking to an 8-year old? 😜


On Wed, Feb 20, 2019 at 3:05 PM Mike Gould <mikeyg123@...> wrote:
As a bind address 0.0.0.0 means all interfaces. This will almost always just work 
127.0.0.1 means the local machine. This will only work if sdr# is running on the same machine as spyserver



On Wed, 20 Feb 2019 at 12:27, Ken Alexander <ve3hls@...> wrote:
All I want is for this to work inside my house.  I'm not even thinking about the internet right now.

I tried again and got this:  Could not connect to SDR://127.0.0.1:5555

Ken



On Wed, Feb 20, 2019 at 11:42 AM prog <info@...> wrote:
The default in SDR# is 127.0.0.1 (localhost).
Try getting something to work locally and get familiar with it before stepping forward.

--


Re: Beginner Questions: spyserver config

Mike Gould <mikeyg123@...>
 

As a bind address 0.0.0.0 means all interfaces. This will almost always just work 
127.0.0.1 means the local machine. This will only work if sdr# is running on the same machine as spyserver



On Wed, 20 Feb 2019 at 12:27, Ken Alexander <ve3hls@...> wrote:
All I want is for this to work inside my house.  I'm not even thinking about the internet right now.

I tried again and got this:  Could not connect to SDR://127.0.0.1:5555

Ken



On Wed, Feb 20, 2019 at 11:42 AM prog <info@...> wrote:
The default in SDR# is 127.0.0.1 (localhost).
Try getting something to work locally and get familiar with it before stepping forward.


Re: Beginner Questions: spyserver config

Martin Smith
 

On Wed, Feb 20, 2019 at 11:08 AM, Ken Alexander wrote:


back to 127.0.0.5 and changed bind_port to 555
127.0.0.5 is not the loopback address (127.0.0.1 is the default loopback address). And historically any port number lower than 1024 requires root access for a process to bind to under most UNIX distributions. Running any process as root while bound to a port is considered a much much higher security risk than running any process as user account of some description.

If you bind any process to a port on the loopback address, then for security only local programs physically running on that machine can access that port on the loopback address. loopback addresses are not remotely accessible across a network they are local to the machine. You should use the default bind_host of 0.0.0.0 which will bind the process to the loopback address AND the network accessible address of the machine. If you only want your spyserver accessible locally on your home network then do not enable port forwarding on your home router for that port and also set "list_in_directory = 0" in the spyserver.config file.


Re: Beginner Questions: spyserver config

Martin Smith
 

SDR:// 127.0.0.1:5555 ( http://127.0.0.1:5555 )
127.0.0.1 is called the loopback address, you could think of it as a short hand for the machine that you are sitting in front of and physically typing on.
So the question for you would be, is Spyserver running on the same windows machine that SDR# is running on ?


Re: Beginner Questions: spyserver config

hmarais@...
 

Replace 127.0.0.1 with the IP address of the Raspberry PI when connecting from SDR#. Leave bind_host as 0.0.0.0 in the Spyserver config on the Raspberry PI.


Re: Spyverter R2 with USRP B210 #shortwave

erik@...
 

Hi jdow,

Yes, as I tired to say, I got it now, I see the symmetry above / below 120MHz. My confusion was from the online literature about the Spyverter r2 that mentioned only a positive image, and therefore I was expecting the negative image (for whatever reason) may have been suppressed / attenuated.

I've just landed in Singapore, so I'm nowhere near my long-wire at the moment, so I can't 'play' just now, but am looking forward to spending some more time tinkering with the Spyverter R2.

As an aside - I'm half way through the book "The Hobbyist's Guide to the RTL-SDR: Really Cheap Software Defined Radio", and so far it seems a crying shame there is no Ettus support for SDR#, which is the primary s/w the book is based on. I found the pirates using the FLTSTAT sats especially amusing...

The Hobbyist's Guide to the RTL-SDR: Really Cheap Software Defined Radio


Re: Beginner Questions: spyserver config

Ken Alexander
 

All I want is for this to work inside my house.  I'm not even thinking about the internet right now.

I tried again and got this:  Could not connect to SDR://127.0.0.1:5555

Ken



On Wed, Feb 20, 2019 at 11:42 AM prog <info@...> wrote:
The default in SDR# is 127.0.0.1 (localhost).
Try getting something to work locally and get familiar with it before stepping forward.

7761 - 7780 of 38111