It might be or it will be? :)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 26 2021
Jul 9 2021
It might be an issue with vlan_mon, but ipoe module will work with multiple accel instances
How accel-ppp will communicate with kernel modules like vlan_mon or ipoe? Will multiple instances use the same modules?
Agree with @svlobanov , run multiple instances in this case.
you can simply run multiple instances of accel-ppp
Jul 8 2021
Jun 30 2021
Jun 29 2021
Jun 16 2021
Jun 11 2021
May 8 2021
Successfully tested. Fixed by https://github.com/accel-ppp/accel-ppp/commit/b1ca6157c6fcd93966e115f113a032a42f77843d
Apr 28 2021
Created pull request
https://github.com/accel-ppp/accel-ppp/pull/15
Apr 27 2021
Mar 22 2021
==16746== Helgrind, a thread error detector ==16746== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al. ==16746== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==16746== Command: /tmp/debug/usr/sbin/accel-pppd -c /etc/accel-ppp/accel-ppp.conf ==16746== ***** started ***** start connecting pppoe ==16746== ---Thread-Announcement------------------------------------------ ==16746== ==16746== Thread #6 was created ==16746== at 0x4C0D915: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== by 0x486129D: create_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4862AED: pthread_create@@GLIBC_2.1 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x48633B6: pthread_create@GLIBC_2.0 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x484976D: create_thread (triton.c:320) ==16746== by 0x484ABC3: triton_run (triton.c:744) ==16746== by 0x1385E0: main (main.c:407) ==16746== ==16746== ---Thread-Announcement------------------------------------------ ==16746== ==16746== Thread #7 was created ==16746== at 0x4C0D915: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== by 0x486129D: create_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4862AED: pthread_create@@GLIBC_2.1 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x48633B6: pthread_create@GLIBC_2.0 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x484716B: md_run (md.c:48) ==16746== by 0x484AC55: triton_run (triton.c:757) ==16746== by 0x1385E0: main (main.c:407) ==16746== ==16746== ---Thread-Announcement------------------------------------------ ==16746== ==16746== Thread #1 is the program's root thread ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Lock at 0x4851260 was first observed ==16746== at 0x4830619: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x484A87C: triton_init (triton.c:666) ==16746== by 0x1384E2: main (main.c:360) ==16746== Address 0x4851260 is 0 bytes inside data symbol "threads_lock" ==16746== ==16746== Possible data race during write of size 4 at 0x4D497F8 by thread #6 ==16746== Locks held: 1, at address 0x4851260 ==16746== at 0x4849271: triton_thread (triton.c:201) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous read of size 4 by thread #7 ==16746== Locks held: none ==16746== at 0x4847455: md_thread (md.c:98) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== Address 0x4d497f8 is 56 bytes inside a block of size 156 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x48499D8: triton_context_register (triton.c:364) ==16746== by 0x5111F08: init_net (disc.c:95) ==16746== by 0x5112198: pppoe_disc_start (disc.c:149) ==16746== by 0x510D2DB: __pppoe_server_start (pppoe.c:1528) ==16746== by 0x510CC67: pppoe_server_start (pppoe.c:1406) ==16746== by 0x510F0A2: load_interfaces (pppoe.c:2075) ==16746== by 0x510F225: pppoe_init (pppoe.c:2107) ==16746== by 0x484A9EA: triton_load_modules (triton.c:704) ==16746== Block was alloc'd by thread #1 ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Possible data race during read of size 4 at 0x4D6E2E0 by thread #7 ==16746== Locks held: none ==16746== at 0x484734D: md_thread (md.c:82) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous write of size 4 by thread #6 ==16746== Locks held: none ==16746== at 0x483886B: memset (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x4847588: triton_md_register_handler (md.c:119) ==16746== by 0x1120CF: establish_ppp (ppp.c:124) ==16746== by 0x5109650: connect_channel (pppoe.c:463) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== Address 0x4d6e2e0 is 80 bytes inside a block of size 92 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x4847573: triton_md_register_handler (md.c:118) ==16746== by 0x1120CF: establish_ppp (ppp.c:124) ==16746== by 0x5109650: connect_channel (pppoe.c:463) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== Block was alloc'd by thread #6 ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Possible data race during read of size 4 at 0x4D6E2C4 by thread #7 ==16746== Locks held: none ==16746== at 0x484735F: md_thread (md.c:84) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous write of size 4 by thread #6 ==16746== Locks held: none ==16746== at 0x4838863: memset (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x4847588: triton_md_register_handler (md.c:119) ==16746== by 0x1120CF: establish_ppp (ppp.c:124) ==16746== by 0x5109650: connect_channel (pppoe.c:463) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== Address 0x4d6e2c4 is 52 bytes inside a block of size 92 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x4847573: triton_md_register_handler (md.c:118) ==16746== by 0x1120CF: establish_ppp (ppp.c:124) ==16746== by 0x5109650: connect_channel (pppoe.c:463) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== Block was alloc'd by thread #6 ==16746== ==16746== ---Thread-Announcement------------------------------------------ ==16746== ==16746== Thread #5 was created ==16746== at 0x4C0D915: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== by 0x486129D: create_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4862AED: pthread_create@@GLIBC_2.1 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x48633B6: pthread_create@GLIBC_2.0 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x484976D: create_thread (triton.c:320) ==16746== by 0x484ABC3: triton_run (triton.c:744) ==16746== by 0x1385E0: main (main.c:407) ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Lock at 0x4D4AE5C was first observed ==16746== at 0x4834228: pthread_mutex_init (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x513BE14: __add_server (serv.c:555) ==16746== by 0x513CC3C: add_server (serv.c:862) ==16746== by 0x513CE6B: load_config (serv.c:906) ==16746== by 0x513D11C: init (serv.c:955) ==16746== by 0x484A9EA: triton_load_modules (triton.c:704) ==16746== by 0x1385B8: main (main.c:402) ==16746== Address 0x4d4ae5c is 156 bytes inside a block of size 268 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x513CBB7: add_server (serv.c:847) ==16746== by 0x513CE6B: load_config (serv.c:906) ==16746== by 0x513D11C: init (serv.c:955) ==16746== by 0x484A9EA: triton_load_modules (triton.c:704) ==16746== by 0x1385B8: main (main.c:402) ==16746== Block was alloc'd by thread #1 ==16746== ==16746== Possible data race during write of size 4 at 0x4D4A518 by thread #5 ==16746== Locks held: 1, at address 0x4D4AE5C ==16746== at 0x1361DC: __list_del (list.h:86) ==16746== by 0x13622B: list_del (list.h:96) ==16746== by 0x136D36: _log_free_msg (log.c:276) ==16746== by 0x1365CF: do_log (log.c:113) ==16746== by 0x136B2F: log_ppp_debug (log.c:230) ==16746== by 0x513AD82: rad_server_req_exit (serv.c:259) ==16746== by 0x5134512: rad_req_read (req.c:423) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== ==16746== This conflicts with a previous read of size 4 by thread #6 ==16746== Locks held: none ==16746== at 0x5102D91: unpack_msg (log_syslog.c:42) ==16746== by 0x5102FE1: do_syslog (log_syslog.c:81) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== Address 0x4d4a518 is 56 bytes inside a block of size 76 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x1363EB: do_log (log.c:87) ==16746== by 0x136B2F: log_ppp_debug (log.c:230) ==16746== by 0x513AD82: rad_server_req_exit (serv.c:259) ==16746== by 0x5134512: rad_req_read (req.c:423) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== Block was alloc'd by thread #5 ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Lock at 0x4D4AE5C was first observed ==16746== at 0x4834228: pthread_mutex_init (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x513BE14: __add_server (serv.c:555) ==16746== by 0x513CC3C: add_server (serv.c:862) ==16746== by 0x513CE6B: load_config (serv.c:906) ==16746== by 0x513D11C: init (serv.c:955) ==16746== by 0x484A9EA: triton_load_modules (triton.c:704) ==16746== by 0x1385B8: main (main.c:402) ==16746== Address 0x4d4ae5c is 156 bytes inside a block of size 268 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x513CBB7: add_server (serv.c:847) ==16746== by 0x513CE6B: load_config (serv.c:906) ==16746== by 0x513D11C: init (serv.c:955) ==16746== by 0x484A9EA: triton_load_modules (triton.c:704) ==16746== by 0x1385B8: main (main.c:402) ==16746== Block was alloc'd by thread #1 ==16746== ==16746== Possible data race during write of size 4 at 0x4D4A24C by thread #5 ==16746== Locks held: 1, at address 0x4D4AE5C ==16746== at 0x136232: list_del (list.h:97) ==16746== by 0x136D36: _log_free_msg (log.c:276) ==16746== by 0x1365CF: do_log (log.c:113) ==16746== by 0x136B2F: log_ppp_debug (log.c:230) ==16746== by 0x513AD82: rad_server_req_exit (serv.c:259) ==16746== by 0x5134512: rad_req_read (req.c:423) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous read of size 4 by thread #6 ==16746== Locks held: none ==16746== at 0x5102D99: unpack_msg (log_syslog.c:42) ==16746== by 0x5102FE1: do_syslog (log_syslog.c:81) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== Address 0x4d4a24c is 36 bytes inside a block of size 185 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x136FF6: add_msg (log.c:332) ==16746== by 0x1364C7: do_log (log.c:96) ==16746== by 0x136B2F: log_ppp_debug (log.c:230) ==16746== by 0x513AD82: rad_server_req_exit (serv.c:259) ==16746== by 0x5134512: rad_req_read (req.c:423) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== Block was alloc'd by thread #5 ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Possible data race during write of size 4 at 0x4D4A24C by thread #5 ==16746== Locks held: none ==16746== at 0x136232: list_del (list.h:97) ==16746== by 0x136D36: _log_free_msg (log.c:276) ==16746== by 0x1365CF: do_log (log.c:113) ==16746== by 0x136A3D: log_ppp_info1 (log.c:210) ==16746== by 0x51358DF: rad_packet_print (packet.c:412) ==16746== by 0x5134563: rad_req_read (req.c:429) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous read of size 4 by thread #6 ==16746== Locks held: none ==16746== at 0x5102D99: unpack_msg (log_syslog.c:42) ==16746== by 0x5102FE1: do_syslog (log_syslog.c:81) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== Address 0x4d4a24c is 36 bytes inside a block of size 185 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x136FF6: add_msg (log.c:332) ==16746== by 0x1364C7: do_log (log.c:96) ==16746== by 0x136A3D: log_ppp_info1 (log.c:210) ==16746== by 0x5134543: rad_req_read (req.c:428) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== Block was alloc'd by thread #5 ==16746== ***** pppoe connected ==16746== ---Thread-Announcement------------------------------------------ ==16746== ==16746== Thread #8 was created ==16746== at 0x4C0D915: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== by 0x486129D: create_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4862AED: pthread_create@@GLIBC_2.1 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x48633B6: pthread_create@GLIBC_2.0 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x4847F7E: timer_run (timer.c:57) ==16746== by 0x484AC5A: triton_run (triton.c:758) ==16746== by 0x1385E0: main (main.c:407) ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Possible data race during read of size 4 at 0x4D73F4C by thread #8 ==16746== Locks held: none ==16746== at 0x484815F: timer_thread (timer.c:91) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous write of size 4 by thread #6 ==16746== Locks held: none ==16746== at 0x4838893: memset (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x4848374: triton_timer_add (timer.c:129) ==16746== by 0x117B9B: start_echo (ppp_lcp.c:669) ==16746== by 0x116234: lcp_layer_up (ppp_lcp.c:170) ==16746== by 0x114A2C: ppp_fsm_recv_conf_req_ack (ppp_fsm.c:232) ==16746== by 0x1180FA: lcp_recv (ppp_lcp.c:776) ==16746== by 0x112F65: ppp_chan_read (ppp.c:424) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== Address 0x4d73f4c is 76 bytes inside a block of size 88 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x484835F: triton_timer_add (timer.c:127) ==16746== by 0x117B9B: start_echo (ppp_lcp.c:669) ==16746== by 0x116234: lcp_layer_up (ppp_lcp.c:170) ==16746== by 0x114A2C: ppp_fsm_recv_conf_req_ack (ppp_fsm.c:232) ==16746== by 0x1180FA: lcp_recv (ppp_lcp.c:776) ==16746== by 0x112F65: ppp_chan_read (ppp.c:424) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== Block was alloc'd by thread #6 ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Possible data race during read of size 4 at 0x4D73F40 by thread #8 ==16746== Locks held: none ==16746== at 0x4848171: timer_thread (timer.c:93) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous write of size 4 by thread #6 ==16746== Locks held: none ==16746== at 0x483886B: memset (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x4848374: triton_timer_add (timer.c:129) ==16746== by 0x117B9B: start_echo (ppp_lcp.c:669) ==16746== by 0x116234: lcp_layer_up (ppp_lcp.c:170) ==16746== by 0x114A2C: ppp_fsm_recv_conf_req_ack (ppp_fsm.c:232) ==16746== by 0x1180FA: lcp_recv (ppp_lcp.c:776) ==16746== by 0x112F65: ppp_chan_read (ppp.c:424) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== Address 0x4d73f40 is 64 bytes inside a block of size 88 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x484835F: triton_timer_add (timer.c:127) ==16746== by 0x117B9B: start_echo (ppp_lcp.c:669) ==16746== by 0x116234: lcp_layer_up (ppp_lcp.c:170) ==16746== by 0x114A2C: ppp_fsm_recv_conf_req_ack (ppp_fsm.c:232) ==16746== by 0x1180FA: lcp_recv (ppp_lcp.c:776) ==16746== by 0x112F65: ppp_chan_read (ppp.c:424) ==16746== by 0x4849484: ctx_thread (triton.c:252) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== Block was alloc'd by thread #6 ==16746== ***** accel-cmd show sessions ***** accel-cmd reload ==16746== ---Thread-Announcement------------------------------------------ ==16746== ==16746== Thread #2 was created ==16746== at 0x4C0D915: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== by 0x486129D: create_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4862AED: pthread_create@@GLIBC_2.1 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x114227: init (ppp.c:768) ==16746== by 0x484A9EA: triton_load_modules (triton.c:704) ==16746== by 0x1385B8: main (main.c:402) ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Lock at 0x14686C was first observed ==16746== at 0x4831F07: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x112BAD: uc_thread (ppp.c:337) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== Address 0x14686c is 0 bytes inside data symbol "uc_lock" ==16746== ==16746== Possible data race during write of size 4 at 0x146B1C by thread #5 ==16746== Locks held: none ==16746== at 0x114139: load_config (ppp.c:749) ==16746== by 0x484D452: triton_event_fire (event.c:103) ==16746== by 0x1274EE: conf_reload_notify (std_cmd.c:319) ==16746== by 0x4848B79: __config_reload (triton.c:73) ==16746== by 0x4849095: triton_thread (triton.c:159) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous read of size 4 by thread #2 ==16746== Locks held: 1, at address 0x14686C ==16746== at 0x112BB7: uc_thread (ppp.c:338) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== Address 0x146b1c is 0 bytes inside data symbol "conf_unit_cache" ==16746== ***** disconnecting pppoe ==16746== ---Thread-Announcement------------------------------------------ ==16746== ==16746== Thread #3 was created ==16746== at 0x4C0D915: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== by 0x486129D: create_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4862AED: pthread_create@@GLIBC_2.1 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x48633B6: pthread_create@GLIBC_2.0 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x484976D: create_thread (triton.c:320) ==16746== by 0x484ABC3: triton_run (triton.c:744) ==16746== by 0x1385E0: main (main.c:407) ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Lock at 0x4851260 was first observed ==16746== at 0x4830619: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x484A87C: triton_init (triton.c:666) ==16746== by 0x1384E2: main (main.c:360) ==16746== Address 0x4851260 is 0 bytes inside data symbol "threads_lock" ==16746== ==16746== Lock at 0x4D4C4A4 was first observed ==16746== at 0x4830619: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x4849A41: triton_context_register (triton.c:376) ==16746== by 0x510941B: allocate_channel (pppoe.c:420) ==16746== by 0x510C2F6: pppoe_recv_PADR (pppoe.c:1219) ==16746== by 0x510C5B4: pppoe_serv_read (pppoe.c:1268) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== Address 0x4d4c4a4 is 52 bytes inside a block of size 156 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x48499D8: triton_context_register (triton.c:364) ==16746== by 0x510941B: allocate_channel (pppoe.c:420) ==16746== by 0x510C2F6: pppoe_recv_PADR (pppoe.c:1219) ==16746== by 0x510C5B4: pppoe_serv_read (pppoe.c:1268) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== Block was alloc'd by thread #6 ==16746== ==16746== Possible data race during write of size 4 at 0x4D4C4A8 by thread #7 ==16746== Locks held: 2, at addresses 0x4851260 0x4D4C4A4 ==16746== at 0x48498B8: triton_queue_ctx (triton.c:347) ==16746== by 0x4847409: md_thread (md.c:91) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous write of size 4 by thread #3 ==16746== Locks held: 1, at address 0x4851260 ==16746== at 0x4849271: triton_thread (triton.c:201) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== Address 0x4d4c4a8 is 56 bytes inside a block of size 156 alloc'd ==16746== at 0x482BBB9: malloc (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x10CF6E: _md_malloc (memdebug.c:47) ==16746== by 0x10D096: md_malloc (memdebug.c:68) ==16746== by 0x484CC89: md_mempool_alloc (mempool.c:201) ==16746== by 0x48499D8: triton_context_register (triton.c:364) ==16746== by 0x510941B: allocate_channel (pppoe.c:420) ==16746== by 0x510C2F6: pppoe_recv_PADR (pppoe.c:1219) ==16746== by 0x510C5B4: pppoe_serv_read (pppoe.c:1268) ==16746== by 0x4849544: ctx_thread (triton.c:273) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== Block was alloc'd by thread #6 ==16746== ***** pppoe disconnected ***** stopping ^C==16746== ---------------------------------------------------------------- ==16746== ==16746== Possible data race during read of size 4 at 0x146970 by thread #1 ==16746== Locks held: none ==16746== at 0x136706: log_info1 (log.c:139) ==16746== by 0x13880C: main (main.c:448) ==16746== ==16746== This conflicts with a previous write of size 4 by thread #5 ==16746== Locks held: none ==16746== at 0x13741B: load_config (log.c:497) ==16746== by 0x484D452: triton_event_fire (event.c:103) ==16746== by 0x1274EE: conf_reload_notify (std_cmd.c:319) ==16746== by 0x4848B79: __config_reload (triton.c:73) ==16746== by 0x4849095: triton_thread (triton.c:159) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== Address 0x146970 is 0 bytes inside data symbol "log_level" ==16746== ==16746== ---Thread-Announcement------------------------------------------ ==16746== ==16746== Thread #4 was created ==16746== at 0x4C0D915: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== by 0x486129D: create_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4862AED: pthread_create@@GLIBC_2.1 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x48633B6: pthread_create@GLIBC_2.0 (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4833DA0: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x484976D: create_thread (triton.c:320) ==16746== by 0x484ABC3: triton_run (triton.c:744) ==16746== by 0x1385E0: main (main.c:407) ==16746== ==16746== ---------------------------------------------------------------- ==16746== ==16746== Lock at 0x48512A0 was first observed ==16746== at 0x4830619: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x484A890: triton_init (triton.c:667) ==16746== by 0x1384E2: main (main.c:360) ==16746== Address 0x48512a0 is 0 bytes inside data symbol "ctx_list_lock" ==16746== ==16746== Possible data race during write of size 4 at 0x48512A4 by thread #4 ==16746== Locks held: 1, at address 0x48512A0 ==16746== at 0x4849D28: triton_context_unregister (triton.c:442) ==16746== by 0x510D680: pppoe_server_free (pppoe.c:1600) ==16746== by 0x510C6B0: pppoe_serv_close (pppoe.c:1291) ==16746== by 0x48495E1: ctx_thread (triton.c:287) ==16746== by 0x484921E: triton_thread (triton.c:192) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== ==16746== This conflicts with a previous read of size 4 by thread #5 ==16746== Locks held: none ==16746== at 0x48490AD: triton_thread (triton.c:163) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x482F40F: ??? (in /usr/lib/valgrind/vgpreload_helgrind-x86-linux.so) ==16746== by 0x486241A: start_thread (in /tmp/debug/lib/libpthread-2.22.so) ==16746== by 0x4C0D92D: clone (in /tmp/debug/lib/libc-2.22.so) ==16746== Address 0x48512a4 is 0 bytes inside data symbol "terminate" ==16746== ==16746== ==16746== Use --history-level=approx or =none to gain increased speed, at ==16746== the cost of reduced accuracy of conflicting-access information ==16746== For lists of detected and suppressed errors, rerun with: -s ==16746== ERROR SUMMARY: 36 errors from 12 contexts (suppressed: 2536 from 398)
Mar 18 2021
Mar 17 2021
Mar 16 2021
@triar is this issue fixed?
Jan 24 2021
Jan 13 2021
Jan 8 2021
Nov 18 2020
Oct 28 2020
Your accel-pppd version is too old (142c943721615020bca80de4c69e6bbf574529aa = Mon Oct 22 12:00:02 2018 +0200)
Oct 27 2020
Oct 26 2020
Oct 21 2020
Патч залит в основной код.
Oct 15 2020
Oct 6 2020
Sure, please open PR with the changes and description here https://github.com/accel-ppp/accel-ppp
Oct 2 2020
Oct 1 2020
Sep 6 2020
Sep 4 2020
Хотелось бы добить в код чтобы в логи писались команды reload , restart и shutdown.
просто потом в логах непонятно что был выполнен reload
Хотя бы минимально вывести одну строчку что команда была принята
Sep 3 2020
note: https://github.com/accel-ppp/accel-ppp/blob/master/accel-pppd/radius/radius.c#L577
add
if (!rpd || !rpd->authenticated) return;
Sep 2 2020
Thread 9 "accel-pppd" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffff62fa700 (LWP 5077)]
0x00007ffff7a46731 in raise () from /lib64/libc.so.6
(gdb) bt full
#0 0x00007ffff7a46731 in raise () from /lib64/libc.so.6
No symbol table info available.
#1 0x00007ffff7a3055b in abort () from /lib64/libc.so.6
No symbol table info available.
#2 0x00007ffff7823460 in find_pd (ses=0x7fffd41c4770) at /usr/src/accel-ppp-code-20-08-2020-DEBUG/accel-pppd/radius/radius.c:761
pd = 0x7fffd41c4840 rpd = 0x5555555d3228
#3 0x00007ffff7822a04 in ses_acct_start (ses=0x7fffd41c4770) at /usr/src/accel-ppp-code-20-08-2020-DEBUG/accel-pppd/radius/radius.c:572
rpd = 0x7ffff7fd0090
#4 0x00007ffff7fc9a28 in triton_event_fire (ev_id=10, arg=0x7fffd41c4770) at /usr/src/accel-ppp-code-20-08-2020-DEBUG/accel-pppd/triton/event.c:103
ev = 0x5555555ec560 h = 0x5555555ec580
#5 0x000055555555d322 in ap_session_ifup (ses=0x7fffd41c4770) at /usr/src/accel-ppp-code-20-08-2020-DEBUG/accel-pppd/ifcfg.c:59
No locals.
#6 0x000055555555bc63 in ap_session_activate (ses=0x7fffd41c4770) at /usr/src/accel-ppp-code-20-08-2020-DEBUG/accel-pppd/session.c:145
No locals.
#7 0x00007ffff79b84ea in __ipoe_session_activate (ses=0x7fffd41c4688) at /usr/src/accel-ppp-code-20-08-2020-DEBUG/accel-pppd/ctrl/ipoe/ipoe.c:1018
addr = 0 gw = 0 serv = 0x5555555e8718
#8 0x00007ffff7fc5c80 in ctx_thread (ctx=0x7fffec154868) at /usr/src/accel-ppp-code-20-08-2020-DEBUG/accel-pppd/triton/triton.c:273
h = 0x1f1a066759fa000 t = 0x7fffec10e808 call = 0x7fffc41e7f18 tt = 1 events = 32767
#9 0x00007ffff7fc5960 in triton_thread (thread=0x5555556266b8) at /usr/src/accel-ppp-code-20-08-2020-DEBUG/accel-pppd/triton/triton.c:192
set = {__val = {516, 0 <repeats 15 times>}} sig = 10 need_free = 0 stack = 0x0
#10 0x00007ffff7f93ea7 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#11 0x00007ffff7b0721f in clone () from /lib64/libc.so.6
No symbol table info available.
accel-ppp version 1.12.0-92-g38b6104
Sep 1 2020
[ipoe]
ipv6=1
verbose=5
username=lua:username
lua-file=/etc/accel-ppp.lua
password=empty
lease-time=21600
renew-time=10800
max-lease-time=43200
soft-terminate=0
Jul 23 2020
Jul 17 2020
Hi @yakovlev.alexey.n , how it possible to reproduce on the our LAB? Can you describe this moment if you know?
Jul 13 2020
Ситуация повторилась.
По lsof -np {PID} вижу открытых коннектов больше, чем интерфейсов. После рестарта сервиса все коннекты закрываются, висящие в том числе.
Uptime два месяца, расхождение по числу коннектов стало заметно после снижения нагрузки.
Jun 13 2020
Jun 10 2020
Jun 9 2020
Ok, thanks, will mark as resolved.
Yes, I tested. Daemon does not crash.
@Harunaga did you test the latest version? https://phabricator.accel-ppp.org/R1:d8c4209188481c3836d87266f5cc6e37661df8fd
Jun 8 2020
Jun 7 2020
You are talking about ifcfg,mode and start options, right? These are per-interface configuration, not per-session so I could not imagine how to configure per-interface options via access-accept message.
Jun 6 2020
I use the fully dynamic configuration of the subscriber's network interface. Radius server sends the network mask, gateway, IP address and routes in the Access-Accept packet. But some subscriber network interfaces should be ip-unnumbered = 1, while others should be ip-unnumbered=0. I have no way to change this option in the configuration file. I would like to send this parameter in Access-Accept packet with network mask and gateway.
Can you explain your idea in details? What do you want to add? Which messages should be modified? (access-request/access-accept/accountint-request?)
May 24 2020
May 15 2020
May 5 2020
Возможно такое поведение было связано с недавними проблемами в ядре сети.
Apr 28 2020
Apr 22 2020
I propose update accel-ppp.conf.5 for the actual state if something is missing
About https://accel-ppp.readthedocs.io/, we can also migrate this to the self-hosted side when appears some access issues.
Main goal docs on readthedocs.io to provide guides and detailed instruction instead of accel-ppp.conf.5
Возможно такое поведение было связано с недавними проблемами в ядре сети.
Нужно проверить. Задачу можно считать неактуальной / несрочной до подтверждения или опровержения версии.
Apr 21 2020
Apr 20 2020
Apr 16 2020
Вероятно, что дело в Idle-Timeout 600
Apr 8 2020
Apr 7 2020
@faceless fixed in organization repository https://github.com/accel-ppp/accel-ppp.git
Apr 6 2020
Note: The main reason - for last Requests accel-ppp answer to client MAC address instead of Relay MAC address.