ebtables - like iptables and ip6tables - rightly depends on net ("before net"). Furthermore the init script /etc/init.d/ebtables also specifies "use logger" as a dependency which on the face of it seems correct.
This however results in a circular dependency and an incorrect startup sequence if logger (e.g. syslog-ng) itslef also depends on net ("rc_need=net.foo") which is not an uncommon scenario.
iptables and ip6tables both overcome this issue by not listing "use logger" in their init scripts but rather relying on using the respective configuration file /etc/conf.d in case the dependency is desired. The relevant section in iptables (ip6tables contains the same information) reads as follows:
===== start /etc/conf.d/iptables =====
# If you need to log iptables messages as soon as iptables starts,
# AND your logger does NOT depend on the network, then you may wish
# to uncomment the next line.
# If your logger depends on the network, and you uncomment this line
# you will create an unresolvable circular dependency during startup.
# After commenting or uncommenting this line, you must run 'rc-update -u'.
===== end /etc/conf.d/iptables =====
Suggested fix: Apply the same logic used for iptables and ip6tables to resolve the issue. This is an easy fix and works well within the defined framework.