sniffer icon indicating copy to clipboard operation
sniffer copied to clipboard

Request for ARM64 (aarch64) Support for VoIPmonitor

Open lawlint312 opened this issue 1 year ago • 7 comments

Dear VoIPmonitor Team,

I hope this message finds you well. I'm writing to inquire about the possibility of adding support for ARM64 (aarch64) architecture for VoIPmonitor.

As ARM-based processors gain popularity across various computing platforms, including embedded systems and small-scale servers like the Raspberry Pi 4, there is a growing interest in running VoIPmonitor on ARM64 architecture. Currently, it appears that VoIPmonitor does not officially support ARM64, which limits its deployment on these platforms.

Could you please consider adding support for ARM64 architecture in future releases of VoIPmonitor? This would enable users leveraging ARM64-based devices to utilize VoIPmonitor effectively, expanding its accessibility and utility in diverse environments.

Thank you for considering this request. I look forward to any updates or insights you may provide regarding ARM64 support for VoIPmonitor.

Best regards,

Lawliet Near

lawlint312 avatar Jun 13 '24 09:06 lawlint312

Hello,

we already have static binaries for amrv6k and it should be compilable on any arm architectures - have you tried it?

voipmonitor avatar Jun 13 '24 12:06 voipmonitor

ARM 64 bit it is not working . can we get for ARM64 please

sandeep-plivo avatar Apr 23 '25 09:04 sandeep-plivo

any details please?

voipmonitor avatar Apr 23 '25 09:04 voipmonitor

local time 2025-04-23 03:43:45 2025-04-23 03:43:50,177 INFO exited: voipmonitor (exit status 0; expected) 2025-04-23 04:23:48,277 INFO reaped unknown pid 15 (terminated by SIGSEGV) 2025-04-23 04:40:43,381 INFO reaped unknown pid 463 (terminated by SIGSEGV) 2025-04-23 04:48:52,853 INFO reaped unknown pid 544 (terminated by SIGSEGV) 2025-04-23 05:03:20,722 INFO reaped unknown pid 614 (terminated by SIGSEGV) 2025-04-23 05:29:25,328 INFO reaped unknown pid 704 (terminated by SIGSEGV) 2025-04-23 06:34:48,586 INFO reaped unknown pid 793 (terminated by SIGSEGV) 2025-04-23 07:10:57,941 INFO reaped unknown pid 853 (terminated by SIGSEGV) 2025-04-23 07:27:54,069 WARN received SIGTERM indicating exit request

We are getting this error PCAP are are not getting captured. I tried cloning the repo and started the voipmointor using supervisord . I don't see any pcaps are getting captured. Do have any official package that supports ARM64. (We are using Amazon linux ARM64)

sandeep-plivo avatar Apr 23 '25 11:04 sandeep-plivo

Is it possible to get ssh access?

On Wed, Apr 23, 2025 at 1:11 PM Sandeep N Plivo @.***> wrote:

local time 2025-04-23 03:43:45 2025-04-23 03:43:50,177 INFO exited: voipmonitor (exit status 0; expected) 2025-04-23 04:23:48,277 INFO reaped unknown pid 15 (terminated by SIGSEGV) 2025-04-23 04:40:43,381 INFO reaped unknown pid 463 (terminated by SIGSEGV) 2025-04-23 04:48:52,853 INFO reaped unknown pid 544 (terminated by SIGSEGV) 2025-04-23 05:03:20,722 INFO reaped unknown pid 614 (terminated by SIGSEGV) 2025-04-23 05:29:25,328 INFO reaped unknown pid 704 (terminated by SIGSEGV) 2025-04-23 06:34:48,586 INFO reaped unknown pid 793 (terminated by SIGSEGV) 2025-04-23 07:10:57,941 INFO reaped unknown pid 853 (terminated by SIGSEGV) 2025-04-23 07:27:54,069 WARN received SIGTERM indicating exit request

We are getting this error PCAP are are not getting captured. I tried cloning the repo and started the voipmointor using supervisord . I don't see any pcaps are getting captured. Do have any official package that supports ARM64. (We are using Amazon linux ARM64)

— Reply to this email directly, view it on GitHub https://github.com/voipmonitor/sniffer/issues/112#issuecomment-2823934381, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVX7J5NGZEWTTFCRNAYPNL225YNHAVCNFSM6AAAAAB3VYRNFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRTHEZTIMZYGE . You are receiving this because you commented.Message ID: @.***> sandeep-plivo left a comment (voipmonitor/sniffer#112) https://github.com/voipmonitor/sniffer/issues/112#issuecomment-2823934381

local time 2025-04-23 03:43:45 2025-04-23 03:43:50,177 INFO exited: voipmonitor (exit status 0; expected) 2025-04-23 04:23:48,277 INFO reaped unknown pid 15 (terminated by SIGSEGV) 2025-04-23 04:40:43,381 INFO reaped unknown pid 463 (terminated by SIGSEGV) 2025-04-23 04:48:52,853 INFO reaped unknown pid 544 (terminated by SIGSEGV) 2025-04-23 05:03:20,722 INFO reaped unknown pid 614 (terminated by SIGSEGV) 2025-04-23 05:29:25,328 INFO reaped unknown pid 704 (terminated by SIGSEGV) 2025-04-23 06:34:48,586 INFO reaped unknown pid 793 (terminated by SIGSEGV) 2025-04-23 07:10:57,941 INFO reaped unknown pid 853 (terminated by SIGSEGV) 2025-04-23 07:27:54,069 WARN received SIGTERM indicating exit request

We are getting this error PCAP are are not getting captured. I tried cloning the repo and started the voipmointor using supervisord . I don't see any pcaps are getting captured. Do have any official package that supports ARM64. (We are using Amazon linux ARM64)

— Reply to this email directly, view it on GitHub https://github.com/voipmonitor/sniffer/issues/112#issuecomment-2823934381, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVX7J5NGZEWTTFCRNAYPNL225YNHAVCNFSM6AAAAAB3VYRNFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRTHEZTIMZYGE . You are receiving this because you commented.Message ID: @.***>

voipmonitor avatar Apr 23 '25 13:04 voipmonitor

Sorry, these are the servers running on the organization's private network.

sandeep-plivo avatar Apr 24 '25 04:04 sandeep-plivo

please provide any testing environment where we can log through ssh to debug this issue.

voipmonitor avatar Apr 24 '25 11:04 voipmonitor