[hpsdr] HPSDRProgrammer_v2_nocap V2.0.4.9

[Ken N9VV]

APIPA addresses are a wonderful feature of the Metis and Ethernet 
interfaces that Phil VK6PH has created.

For those who are not familiar with APIPA addressing, here are some good 
references:
<URL: http://en.wikipedia.org/wiki/Link-local_address
 >

<URL:  http://wiki.wireshark.org/APIPA
 >

<URL: http://compnetworking.about.com/cs/protocolsdhcp/g/bldef_apipa.htm
 >

<URL: 
http://www.dummies.com/how-to/content/automatic-private-ip-addressing-apipa.html
 >

GL de N9VV

On 3/8/2014 1:06 PM, Dick Faust wrote:
> ***** High Performance Software Defined Radio Discussion List *****
>
> Dave
> Before starting to trouble shooting my Mercury board today I tested
> several different combinations that were configured with a wifi and NIC
> to duplicate last weeks problem
> In those below that worked ok the Wifi to local intranet LAN had IP
> addresses of 192.168.1.xxx form.
> Also they had a Local IP address of 169.254.220.153 on the NIC
>
> Dell Inspiron 1501 Win Vista Home Premium SP1 - OK
> HP d7v Win 7 Home Premium SP1 - OK
> Acer Aspire1 D257-13478 Win Starter SP1 - OK
>
> Original Nettop IP Win XP Pro SP3 IP on Local NIC 169.254.33.182, WiFi
> as above would not connect on Local and gives the error screen.
>
> Asus Motherboard running Win XP Pro SP3 only 1 NIC on board
>    Local IP 169.254.14.179 and on Metis  IP 169.254.220.153  worked ok
>
>
> On 3/4/2014 7:29 AM, Dave Larsen wrote:
>>
>> Dick
>>
>> I am busy at work but I will try to create your configure you system
>> in my shack an test it this week. This email let me know what I need.
>>
>> Dave KV0S
>>
>> On Mar 4, 2014 1:38 AM, "Dick Faust" <k9ivb at cox.net
>> <mailto:k9ivb at cox.net>> wrote:
>>
>>     Dave
>>     I do not have 2 links to the same address space.  One [the WiFi]
>>     goes to my router [DHCP IP 192.168.1.xxx], the second NIC goes
>>     directly to the Hermes or to the Metis [APIPA IP 169.254.x.x].  It
>>     does not make any difference if the WiFi connection is enabled or
>>     disabled you get the error screen [as an attachment gif this
>>     time].  The Adapter Watch program clearly shows each adapter
>>     connected to the separate networks.
>>     The older programmer works, the new one does not .
>>
>>     There was another post on the list today from G4KFZ with the same
>>     issue.
>>
>>     Perhaps in your testing you did not test with XP.  All of my XP
>>     systems were clean install XP Pro SP3 without any additional
>>     automatic updates from M$.  All of the Net Framework garbage was
>>     installed as well.
>>
>>     Dick K9IVB
>>
>>     On 3/3/2014 10:02 PM, Dave Larsen wrote:
>>
>>         Dick
>>
>>         I can not see the error message in either message. it seems
>>         the email software removed the image of paste text.
>>
>>         My best guess is that several people in HPSDRProgrammer and
>>         PowerSDR have had crouble if you have two interfaces to the
>>         same address space.
>>
>>         so if you have a wireless and a wired link to the same IP
>>         space. so there are two ways to get to the HPSDR board
>>
>>
>>         I did quite a bit of testinf with a hermes and metis on one
>>         network while I had another network present.  The I moved both
>>         boards to the other network and I had no problem program
>>         either board.  I did turn off the wireless on my laptop and
>>         used the wired line.
>>
>>         Dave KV0S
>>
>>         snip ..
>>
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help:
> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>

 1394306853.0