-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Fix IPv4 and IPv6 issue where OSSEC-HIDS only binds on first IPv6 #1880
base: master
Are you sure you want to change the base?
Conversation
…ich is :: in most cases) and not allow IPv4 socket binding
What is the actual problem you're trying to solve? |
@ddpbsd Yes I have tested it in development openSUSE linux server. OSSEC server standalone works as charm and I like to it as OSSEC remoted host.
Which should bind it to IPv4 ip 192.168.2.1 but it binds to IPv6 ::192.168.2.1 which is not completely wrong but not what should happen. |
Are agents unable to connect? Have you tried defining |
No I haven't tested that but I try it and report back. Also I haven't got agent working it just says 'ERROR: Unknown imsg type' and I think I just haven't read enough manual. OSSEC-HIDS server works very well. |
I just did a fresh checkout of master on a fresh opensuse instance and was not able to reproduce the error. I'll have to fiddle with it a bit to see if I can find any settings that cause issues I guess. |
Hmm.. did you compile package from source or used rpm from repo? I have to dig this little bit further what is the main reason of this. Did you use Leap or Tumbleweed? |
I installed from source. "Start with what you know." I'll try looking at the package when I can make some time, but I'm not very experienced with Suse. |
I don't know if this is correct way to fix this but I couldn't bind OSSEC remoted any other than :: or ::192.168.0.1 if these defines where available. Without them everything works as expected.