Menu ▾ ▴

Help requested on running ptpd with Fedora 4

Help
vsbhel
2013-07-02
2013-07-02

  • vsbhel

    vsbhel - 2013-07-02

    Please guide me. I get the following output file on executing ptpd on Fedora 4. What does SO_BINDTODEVICE mean?

    [root@localhost src]# ./ptpd2 -g -beth0 -u172.24.2.55 -C > out

    (ptpd info) 09:57:17.518413 (___) Info: Going to check lock /var/run/kernel_clock

    (ptpd info) 09:57:17.580555 (___) Info: No ptpd daemons detected in parallel (as expected)

    (ptpd info) 09:57:17.641858 (___) Info: No ntpd daemons detected in parallel (as expected)

    (ptpd info) 09:57:17.642436 (___) Info: Going to check lock /var/run/kernel_clock

    (ptpd info) 09:57:17.678087 (___) Info: Startup finished sucessfully

    (ptpd error) 09:57:17.705219 (init) failed to call SO_BINDTODEVICE on the interface (strerror: No such file or directory)

    (ptpd error) 09:57:17.706047 (init) failed to initialize network

    (ptpd notice) 09:57:17.740807 (flt) self shutdown, probably due to an error

    Regards

    Shyamala 　

     

  • Jan Breuer

    Jan Breuer - 2013-07-02

    OK, Fedora 4 is very old (8 years) and uses Linux kernel 2.6.11. There may be other things broken.

    SO_BINDTODEVICE is used to force network stack to use selected network interface. It is not necessary to use this call.

    You can comment out
    #define USE_BINDTODEVICE
    from file src/dep/ptpd_dep.h
    recompile PTPd and try again.

    Regards
    Jan

     

    Last edit: Jan Breuer 2013-07-02

Log in to post a comment.