Andrew

I am occasionally noticing these Update Failure issues in the log due to "too long for column." Should I be concerned about them and is there a way to avoid them? Every month I download the MAC vendor list from https://linuxnet.ca/ieee/oui.txt. Tue Jan 7 08:05:23 2020: netdbctl(32208): Importing 7053 MAC entries in to switchports table Tue Jan 7 08:05:31 2020: netdbctl(32208): DBD::mysql::st execute failed: Data too long for column 'vendor' at row 1 at /usr/local/lib/site_perl/NetDB.pm line 2495....

Where were you able to locate version 1.14 of NetDB.pm? I've downloaded the newest version of NetworkDB via SVN and it still had version 1.13. I'm trying to upgrade my server from Ubuntu 14 to 16 but since the upgrade I'm running into the errors below which I'm guessing are resolved in version 1.14. Importing 9123 intstatus entries in to switchstatus table Importing 8403 MAC entries in to switchports table DBD::mysql::st execute failed: Data too long for column 'vendor' at row 1 at /usr/local/lib/site_perl/NetDB.pm...

Attached is a version of SubnetCalc.php that works with Ubuntu 16 and PHP7. The ereg statements needed to be converted over to preg_match.

This is one downside I've had with switchmap too. At first the way I dealt with it...

I'm running NetDB v1.13 (rev 745). I downloaded the NetDB.pm and upgrade-v1.13-to-v1.14.sql....

I downloaded the NetDB.pm and upgrade-v1.13-to-v1.14.sql. After running upgrade-v1.13-to-v1.14.sql...

Most of the hosts on our network are assigned DHCP IPs from a Windows DHCP server....

Most of the hosts on our network are assigned DHCP IPs from a Windows DHCP server....