[hpsdr] Problems building ghpsdr receiver client (from ghpsdr3 project) on Mac OSX

[Mark Leone]

> It certainly wasn't envisioned as something we were supporting the
> rudimentary Metis IP stack was written.  John's been looking at writing
> a Metis firmware such that it's a bit smarter, but I haven't seem how
> his struggles are going with that.
> 
Thanks for the explanation. I see now why any software talking to Metis will
have to work in discovery mode, since it doesn't have full Layer 3
capability. As far as pinging Metis from a remote subnet, I'm sure it was
working. I powered my HPSDR down and back up again and saw the ping success
packets stop and then start up again. This worked because I created static
routes for each direction (e.g. route add -net 192.168.2.0 netmask
255.255.255.0 eth0 for routing to Metis) and I enabled IP forwarding by
executing 'echo 1 > /proc/sys/net/ipv4/ip_forward'. In any case, routing is
a moot issue, since I need to have layer two connectivity across the two
interfaces in order to pass the discovery protocol in the broadcast frames.
So I'll keep working on the bridge implementation. 

> Incidentally, I've tested Metis over my Airport Extreme with my MacBook
> Pro on 802.11n and it works fine.  I haven't tried scaling back to
> 802.11g, but I honestly don't think there will be a huge issue for
> single hardware/firmware receiver applications.  The data rate is well
> less than 10Mbit/sec in that case.
> 
That's good to hear. I have an older 802.11g router, with a moderately
strong signal at the Ubuntu system, so it will be good to get a data point
on how well that works.

73

Mark - K4XML


 1326135230.0