search for: normalport

...and the current situation lets you choose an address but not a port? Assuming so, why would there be a restriction to a single host if there is port, while one could have multiple listen addresses if not? I would think the : scheme should apply to each argument, with lack of : being an implict :[normalport]. For me, the reason to use explicit listen is because you don't like *, and if you are using IP addresses you might well want to listen to v4 and v6. This raises the issue of whether "host" expands to all IP addresses associated with a domain name. > There are also certain co...

...and the current situation lets you choose an address but not a port? Assuming so, why would there be a restriction to a single host if there is port, while one could have multiple listen addresses if not? I would think the : scheme should apply to each argument, with lack of : being an implict :[normalport]. For me, the reason to use explicit listen is because you don't like *, and if you are using IP addresses you might well want to listen to v4 and v6. This raises the issue of whether "host" expands to all IP addresses associated with a domain name. > There are also certain co...

Cheers all, A recent discussion in the issue tracker brought up the idea to allow the `LISTEN` keyword to also accept a single "host:port" token (e.g. if there is only one argument, with at least one colon, and the last colon is followed only by numbers, split it into host and port) : https://github.com/networkupstools/nut/issues/2424 I see certain pros to the idea (may be more

Cheers all, A recent discussion in the issue tracker brought up the idea to allow the `LISTEN` keyword to also accept a single "host:port" token (e.g. if there is only one argument, with at least one colon, and the last colon is followed only by numbers, split it into host and port) : https://github.com/networkupstools/nut/issues/2424 I see certain pros to the idea (may be more

...on lets you choose an address but not a port? > > Assuming so, why would there be a restriction to a single host if there > is port, while one could have multiple listen addresses if not? I would > think the : scheme should apply to each argument, with lack of : being > an implict :[normalport]. > > For me, the reason to use explicit listen is because you don't like *, > and if you are using IP addresses you might well want to listen to v4 > and v6. > > This raises the issue of whether "host" expands to all IP addresses > associated with a domain name....

...on lets you choose an address but not a port? > > Assuming so, why would there be a restriction to a single host if there > is port, while one could have multiple listen addresses if not? I would > think the : scheme should apply to each argument, with lack of : being > an implict :[normalport]. > > For me, the reason to use explicit listen is because you don't like *, > and if you are using IP addresses you might well want to listen to v4 > and v6. > > This raises the issue of whether "host" expands to all IP addresses > associated with a domain name....