Public bug reported:
systemd networkd in use. OVH server.
I've been pulling my hair out for an hour trying to get knockd to work
on a secondary IP assigned to the primary NIC. (It works fine if I
change the IP to the primary when knocking, but that is not the required
or desired use.)
I've tried adding the secondary IP as a virtual NIC named "failover",
then configuring knockd to use the NIC "failover". This does not work,
and "ifconfig failover" actually shows no packets going through the NIC,
even though the IP configured on the virtual NIC is working fine.
I can't find any docs or answered questions about this issue. I was
hoping to stumble upon an undocumented option to force knockd to listed
on a particular IP.
If knockd is really attached to the NIC and supposedly just listening to
syn for a particular port, then it should work. Instead, it appears to
be latching on the the primary IP of the NIC and ignoring all other IP's
on that NIC.
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
Kernel 4.15.0-96-generic
knockd package: 0.7-1ubuntu1.18.04.2 amd64
Any help is much appreciated.
** Affects: knockd (Ubuntu)
Importance: Undecided
Status: New
** Tags: ip secondary
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873186
Title:
knockd does not work on additional IP address of a NIC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1873186/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
