Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian issues with using old network-interfqace naming schema #107

Open
idkpmiller opened this issue Jan 22, 2023 · 1 comment
Open

Debian issues with using old network-interfqace naming schema #107

idkpmiller opened this issue Jan 22, 2023 · 1 comment

Comments

@idkpmiller
Copy link

Hi,
I have follwed the REAMDME for Debian and when I try and start the service I get errors pertaining to eth0 I do not have an eth0 ibn this machine the name of the first NIC is ens3, I have tried to configure this directly in the .conf as well as using any in both cases the same error are shown.

Here is the ouput of starting the service

root@galaxy:/usr/src/sniffer#
root@galaxy:/usr/src/sniffer# /etc/init.d/voipmonitor start
Starting voipmonitor: voipmonitor[768418]: set buffer memory limit to 505503744
voipmonitor[768418]: set threading mode 2
Loading configuration from file /etc/voipmonitor.conf OK
voipmonitor[768418]: set buffer memory limit to 505503744
voipmonitor version 31.1
local time 2023-01-22 16:00:30
voipmonitor[768418]: local time 2023-01-22 16:00:30
Can't get value from 'ethtool -g eth0'. This is not a fatal error. Some NICs don't support it.
voipmonitor[768418]: Can't get value from 'ethtool -g eth0'. This is not a fatal error. Some NICs don't support it.
Can't get value from 'ethtool -c eth0'. This is not a fatal error. Some NICs don't support it.
voipmonitor[768418]: Can't get value from 'ethtool -c eth0'. This is not a fatal error. Some NICs don't support it.
voipmonitor[768418]: detected rrdtool version 10702
interface eth0: libpcap error: SIOCGIFHWADDR: No such device

=======================================================

In terested in ideas or workarounds that are known for the problem.

Thanks
Paul

@milon21
Copy link

milon21 commented Jan 23, 2023

Hello,

if I understand it correctly then you changed the interface option in the voipmonitor.conf but you still see the eth0 interface ? Can you share your voipmonitor.conf ?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants