Displaying 3 results from an estimated 3 matches for "so_freebind".
Did you mean:
ip_freebind
2017 Jan 16
2
disable/mask NetworkManager leads to unit startup fails
Hello!
For me it was best practice to disable "NetworkManager" on headless
installations.
Now suddenly I ran into an problem with several programs not starting
correctly upon boot anymore.
The problem seems to be that their unit files contain "After=network.target"
but network.target wont wait till network is up and working, just waits for
some low level network stuff.
2017 Jan 16
0
disable/mask NetworkManager leads to unit startup fails
...equires if you want no
attempt to start the service if the target fails to activate)
network-online.target (see referenced man page) which won't be
complete until at least one IP is on any interface.
If it's your own application and you can set the flags on the actual
bind then you can use so_freebind on the socket opened, some
applications may have this as a compile time or configurable option.
Another option is to enable net.ipv4.ip_nonlocal_bind and
net.ipv6.ip_nonlocal_bind which allows the kernel to bind a socket on
an IP it doesn't have (do note the caveat it may break some things)....
2017 Jan 17
1
disable/mask NetworkManager leads to unit startup fails
...equires if you want no attempt to
start the service if the target fails to activate) network-online.target
(see referenced man page) which won't be complete until at least one IP is
on any interface.
If it's your own application and you can set the flags on the actual bind
then you can use so_freebind on the socket opened, some applications may
have this as a compile time or configurable option.
Another option is to enable net.ipv4.ip_nonlocal_bind and
net.ipv6.ip_nonlocal_bind which allows the kernel to bind a socket on an IP
it doesn't have (do note the caveat it may break some things)....