- 3
- 0
I've been trying to set up bitwarden on my NAS and after having a port conflict and switching to port 445, I now have a working system... IF I turn off the firewall.
Needless to say, my intent is to have the same working state with the firewall on, but when opening port 445 and denying the rest (other than other ports I intend to use like 22, etc) bitwarden will not connect.
To try to debug this, I wanted to log dropped packets using the following command:
iptables -A INPUT -i eth1 -p tcp --dport 445 -j LOG --log-prefix "IPTABLES-DROPPED: "
but I got the following response:
iptables: No chain/target/match by that name.
This didn't make sense to me, and after looking into it a bit, I found something that I don't know how to get around.
It seems to me (I could be wrong) that the "-j LOG" portion of the command isn't working as intended. This made me think that maybe the kernel module isn't installed. So I did a spot check:
lsmod | grep LOG
returned:
xt_LOG 1423 0
x_tables 16302 21 ...,xt_LOG,...
So now I'm stumped.
Thanks in advance!
Note: I have also posted this on reddit (pointing it out before someone mentions it). I'm not sure what the best method of getting both audiences to see this is. Apologies if this method was not the best.
Needless to say, my intent is to have the same working state with the firewall on, but when opening port 445 and denying the rest (other than other ports I intend to use like 22, etc) bitwarden will not connect.
To try to debug this, I wanted to log dropped packets using the following command:
iptables -A INPUT -i eth1 -p tcp --dport 445 -j LOG --log-prefix "IPTABLES-DROPPED: "
but I got the following response:
iptables: No chain/target/match by that name.
This didn't make sense to me, and after looking into it a bit, I found something that I don't know how to get around.
It seems to me (I could be wrong) that the "-j LOG" portion of the command isn't working as intended. This made me think that maybe the kernel module isn't installed. So I did a spot check:
lsmod | grep LOG
returned:
xt_LOG 1423 0
x_tables 16302 21 ...,xt_LOG,...
So now I'm stumped.
- Is there anyone who has successfully been able to log DROPPED packets on a Synology NAS? If so, how?
- Can anyone help me get bitwarden running as it does without firewall, with firewall on?
Thanks in advance!
Note: I have also posted this on reddit (pointing it out before someone mentions it). I'm not sure what the best method of getting both audiences to see this is. Apologies if this method was not the best.