Hi,
Is anyone willing to explain what seems to me to be an unexpected
behavior in a windows+cygwin PC to Roach1 network connection ?
With the Roach1 in the uboot state. Network address (192.168.3.240)
acquired via dhcp, from a directly connected windows+cygwin
PC host system (192.168.3.2).
Roa
Hi Matt,
We've got a roach1 configured as a spectrometer and
have similar issues.
Note that the FPGA part of the roach and also the Katcp communications
seem to work well. The symptom I have is
ssh
is not reliable without a reboot.
We've left the roach running as a spectrometer for a month o
Glen,
The problem you describe sounds like an issue we had during testing at
Green Bank last December where the NRAO DHCP server would release the DHCP
entry if the client did not renew it at regular intervals. It turns out
that the ROACH linux was not renewing the DHCP entries. I think the final
s
> Glen,
> The problem you describe sounds like an issue we had during testing at
> Green Bank last December where the NRAO DHCP server would release the DHCP
> entry if the client did not renew it at regular intervals. It turns out
> that the ROACH linux was not renewing the DHCP entries. I think t
Hello
> With the Roach1 in the uboot state. Network address (192.168.3.240)
> acquired via dhcp, from a directly connected windows+cygwin
> PC host system (192.168.3.2).
>
> Roach1 can ping the PC exactly as expected.
> PC cygwin ping of Roach1 hangs.
>
> While PC ping is hung if the Roach1 pings
From my experience with uBoot, you cannot ping a board running uBoot,
as uBoot does not listen for pings. You can however ping a PC from the
board running uBoot.
On 14/05/2012 00:23, Marc Welz wrote:
Hello
With the Roach1 in the uboot state. Network address (192.168.3.240)
acquired via dhcp
6 matches
Mail list logo
