Hi Michael,
I tried to read and write to/from the tftp server using the command
line tftp on my linux computer and all of that works fine
so it looks to me to be an issue with the RTEMS/EPICS setup.
Best Regards
Mirek
___
users mailing list
users@rtems.
On 2/14/24 10:22, Miroslaw Dach wrote:
Does anybody have any advice?
Hi Mirek,
Have you tried with a CLI TFTP client?
Since TFTP is generally seen as wildly insecure
these days, default distro. installs of TFTPd
tend to be restrictive.
cf. "man tftpd" and compare with your running
daemon.
h
Hi Frank,
Thank you for your feedback on that. It might be then the setup in EPICS.
Best Regards
Mirek
czw., 15 lut 2024 o 02:26 Frank Kühndel
napisał(a):
> Hello Miroslaw,
>
> On 2/14/24 21:54, Miroslaw Dach wrote:
> > Thanks for your e-mail.
> >> TFTP is normally only used for reading, and
Hello Miroslaw,
On 2/14/24 21:54, Miroslaw Dach wrote:
Thanks for your e-mail.
TFTP is normally only used for reading, and it doesn’t surprise me if
writing isn’t supported since there is no user authentication involved.
I thought that setting the parameter RTEMS_FILESYSTEM_READ_WRITE in the
f
Hi Andrew,
Thanks for your e-mail.
>TFTP is normally only used for reading, and it doesn’t surprise me if
writing isn’t supported since there is no user authentication involved.
I thought that setting the parameter RTEMS_FILESYSTEM_READ_WRITE in the
function call below would do the job:
if (moun
Hi Mirek,
TFTP is normally only used for reading, and it doesn’t surprise me if writing
isn’t supported since there is no user authentication involved.
It should be possible to enable NFSv2 in Rocky Linux 8, it still works on
RHEL-8 but you do have to change one or two files in the server’s /et
