[Bug 1873186] Re: knockd does not work on additional IP address of a NIC

2020-04-16 Thread Dan Streetman
> One this that still bothers me - As I stated in the debug comment, the PCAP filters are INDEED CORRECT and show the correct (supposed) IP in the expression when I tried using a virtual NIC, so why wasn't that actually working as expected? I don't know your *exact* system network config so I can'

[Bug 1873186] Re: knockd does not work on additional IP address of a NIC

2020-04-16 Thread Zizzy Zizzy
YES! That fixed the issue! THANK YOU! I was up until 3 AM trying to sort that out. No clue how I missed that directive in the man page. Zombie eyes, I guess. One this that still bothers me - As I stated in the debug comment, the PCAP filters are INDEED CORRECT and show the correct (supposed) IP in

[Bug 1873186] Re: knockd does not work on additional IP address of a NIC

2020-04-16 Thread Dan Streetman
I think you need to use the "Target" knockd config param, otherwise it uses the interface's primary ip addr. See 'man knockd' and scroll to the bottom, in the "KNOCK/EVENT DIRECTIVES" section. ** Changed in: knockd (Ubuntu) Status: New => Invalid -- You received this bug notification be

[Bug 1873186] Re: knockd does not work on additional IP address of a NIC

2020-04-16 Thread Zizzy Zizzy
Debug mode on, the PCAP rule shows the correct secondary IP, but it will not actually detect the knock on that IP. Adding pcap expression for door '25568': (dst host xx.xx.xx.76 and (((tcp dst port 25568 or 25568 or 25568) and tcp[tcpflags] & tcp-syn != 0))) -- You received this bug notification

[Bug 1873186] Re: knockd does not work on additional IP address of a NIC

2020-04-16 Thread Zizzy Zizzy
To clarify "does not work", the TCP (or UDP) knock on the configured port is never detected when using the secondary IP. If I switch to the primary IP, it works exactly as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https