That seems a good solution. Patch applied, with the man=page changes
re-written and expanded.
Cheers,
Simon.
On 14/03/17 15:11, Petr Menšík wrote:
> Hi,
>
> I have prepared two patches with suggestion how to fix it.
>
> Patch 1 warns when a label is used for --interface in default mode.
> Pa
Hi,
I have prepared two patches with suggestion how to fix it.
Patch 1 warns when a label is used for --interface in default mode.
Patch 2 corrects manual page about real behavior of --interface with
labels. Feel free to change it, I am not very good at complicated
sentences in English.
I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> But you can also be notified about interface changes via a netlink
> socket, so you can cache the interface information.
>
See my reply to Petr: there is an option for that but it's not the
default for historical reasons.
Cheers,
Simon.
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/02/17 21:52, Petr Menšík wrote:
> I would suggest a new option then. For example
> --bind-interfaces-exact. It would listen just like
> --bind-interfaces, but would allow you to listen only on virbr0,
> when ignoring any addresses with label
On Mi, 2017-02-22 at 20:51 +, Simon Kelley wrote:
> > You can get the destination address for datagrams from the
> > IP_PTKINFO auxiliary data:
> >
> > man 7 ip IP_PKTINFO (since Linux 2.2) Pass an IP_PKTINFO ancillary
> > message that contains a pktinfo structure that supplies some
> > inform
Simon Kelley píše v Út 21. 02. 2017 v 18:50 +:
> > Labels are now supported and dnsmasq is able to bind only to
> > secondary IPv4 interface with different address. (Since 2.67!) It
> > works well with --bind-interfaces. However it has inconsistent
> > behavior with and without that option.
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> You can get the destination address for datagrams from the
> IP_PTKINFO auxiliary data:
>
> man 7 ip IP_PKTINFO (since Linux 2.2) Pass an IP_PKTINFO ancillary
> message that contains a pktinfo structure that supplies some
> information about the i
On Di, 2017-02-21 at 18:50 +, Simon Kelley wrote:
>
>
> The different behavior is certainly undesirable, and can be fixed.
> Unfortunately, I can only see how to easily fix it so that the
> --bind-interfaces case works the same way as the default.
>
> The problem is that the sockets API tell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/02/17 17:38, Petr Mensik wrote:
> Hi!
>
> I am new maintainer of dnsmasq package in RHEL. I am looking for
> potential problems with upgrade from dnsmasq 2.66 to version 2.76.
> And I have found something. Commit [1] changed behaviour of
> -
sq-discuss] Support of labels in --interface
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/02/17 17:38, Petr Mensik wrote:
> Hi!
> Let's say my configuration is: 4: virbr0:
> mtu 1500 qdisc noqueue state UP
> group default qlen 1000 link/ether 52:54:00:2b:ee:d3 b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/02/17 17:38, Petr Mensik wrote:
> Hi!
> Let's say my configuration is: 4: virbr0:
> mtu 1500 qdisc noqueue state UP
> group default qlen 1000 link/ether 52:54:00:2b:ee:d3 brd
> ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 sco
Hi!
I am new maintainer of dnsmasq package in RHEL. I am looking for potential
problems with upgrade from dnsmasq 2.66 to version 2.76. And I have found
something.
Commit [1] changed behaviour of --interface eth0:0 behavior.
The first problem is, manual page is not updated. It tells you cannot
12 matches
Mail list logo
