NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Multiple OMAPI errors on SRXN3205 router
I upgraded my SRXN3205 firmware from v3.0.8-12 to v3.1.1-08. I'm seeing these repeated messages in my dhcp log. I don't recall seeing the error messages prior to the upgrade but do recall seeing the multiple DHCPINFORM and DHCPACK messages. I've done some research and it appears Windows 7 clients are the cause of the repeated requests. Should I be concerned about the flood of OMAPI error messages? Everything else appears to be working fine.
- Last output repeated 32 times -
2014 Apr 29 00:43:10 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:43:10 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:43:10 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:43:10 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:43:15 [SRXN3205] [dhcpd] Can't start OMAPI protocol: unexpected error
- Last output repeated 31 times -
2014 Apr 29 00:45:53 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:45:53 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:45:53 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:45:53 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:45:55 [SRXN3205] [dhcpd] Can't start OMAPI protocol: unexpected error
- Last output repeated 20 times -
2014 Apr 29 00:47:36 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:47:36 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:47:36 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:47:36 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:47:40 [SRXN3205] [dhcpd] Can't start OMAPI protocol: unexpected error
- Last output repeated 56 times -
2014 Apr 29 00:52:24 [SRXN3205] [dhcpd] DHCPREQUEST for 192.168.2.118 from 28:6a:ba:20:31:a6 via bdg
2014 Apr 29 00:52:24 [SRXN3205] [dhcpd] DHCPACK on 192.168.2.118 to 28:6a:ba:20:31:a6 via bdg
2014 Apr 29 00:52:24 [SRXN3205] [dhcpd] DHCPREQUEST for 192.168.2.118 from 28:6a:ba:20:31:a6 via bdg
2014 Apr 29 00:52:24 [SRXN3205] [dhcpd] DHCPACK on 192.168.2.118 to 28:6a:ba:20:31:a6 via bdg
2014 Apr 29 00:52:25 [SRXN3205] [dhcpd] Can't start OMAPI protocol: unexpected error
- Last output repeated 32 times -
2014 Apr 29 00:43:10 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:43:10 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:43:10 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:43:10 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:43:15 [SRXN3205] [dhcpd] Can't start OMAPI protocol: unexpected error
- Last output repeated 31 times -
2014 Apr 29 00:45:53 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:45:53 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:45:53 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:45:53 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:45:55 [SRXN3205] [dhcpd] Can't start OMAPI protocol: unexpected error
- Last output repeated 20 times -
2014 Apr 29 00:47:36 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:47:36 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:47:36 [SRXN3205] [dhcpd] DHCPINFORM from 192.168.2.113 via bdg
2014 Apr 29 00:47:36 [SRXN3205] [dhcpd] DHCPACK to 192.168.2.113
2014 Apr 29 00:47:40 [SRXN3205] [dhcpd] Can't start OMAPI protocol: unexpected error
- Last output repeated 56 times -
2014 Apr 29 00:52:24 [SRXN3205] [dhcpd] DHCPREQUEST for 192.168.2.118 from 28:6a:ba:20:31:a6 via bdg
2014 Apr 29 00:52:24 [SRXN3205] [dhcpd] DHCPACK on 192.168.2.118 to 28:6a:ba:20:31:a6 via bdg
2014 Apr 29 00:52:24 [SRXN3205] [dhcpd] DHCPREQUEST for 192.168.2.118 from 28:6a:ba:20:31:a6 via bdg
2014 Apr 29 00:52:24 [SRXN3205] [dhcpd] DHCPACK on 192.168.2.118 to 28:6a:ba:20:31:a6 via bdg
2014 Apr 29 00:52:25 [SRXN3205] [dhcpd] Can't start OMAPI protocol: unexpected error
2 Replies
- Hmmm. I just rebooted the router and the OMAPI error messages do not appear anymore. I confirmed this by doing an ipconfig/renew on my Windows 7 PC. I just get the other DHCP messages, which are "normal". Perhaps a second reboot after an upgrade is necessary. I'll report back in a day or so just in case.
- The second reboot appears to have worked. Haven't seen an OMAPI error since.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
