Public bug reported:
I want to configure sm-notify to use a pre-configured port (at least)
for communication, so that I can open up my iptables rules specifically.
In the current situation, the upstart job for statd just calls "exec sm-
notify" without providing any environment variables for configuration.
Looking into the source of sm-notify there are no environment variables
being picked up for configuration, so all has to be done using command
invocation options/arguments. This, however, is currently impossible.
As such, whenever I restart Ubuntu clients, the iptables rules block out
sm-notify communication because it uses a randomly chosen privileged
port. This is even more important for the NFS-server side, where I also
only allow certain well-known incoming ports to communicate. So even if
the client-side outgoing iptables rules would allow any, the server
incoming configuration would block it because the source port is not
"well-known" and is most likely different for each client for each
system restart.
** Affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451775
Title:
Unable to configure sm-notify
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1451775/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
