[Dnsmasq-discuss] Problem listening on only one interface

[Ejner Fergo]

Hola again Simon,

I'm sorry to be so late with this answer, but unfortunately I have a
very valid excuse...

Anyway, you were absolutely correct. I changed the subnet of the
bonded interface and dnsmasq now only responds through eth1. Luckily
the subnet change didn't require that much reconfiguring on our
network, and I can see now that this is how it should be from the
start.

Many thanks, and have a great year!

Best regards,
Ejner Fergo

On Thu, Nov 19, 2009 at 3:56 PM, Simon Kelley <simon at thekelleys.org.uk> wrote:
> I'm not quite clear what is going on here, but there's one thing which
> really doesn't look right and may well be confusing things: both eth1 and
> bond0 are on the same subnet. If it's possible to fix that by changing the
> address of one of tham, that would be a worthwhile test.
>
>
> Cheers,
>
> Simon.
>
>
> Ejner Fergo wrote:
>>
>> Hi Simon,
>>
>> Thank you for replying!
>>
>> Here's the output of /proc/net/bonding/bond0:
>>
>> Ethernet Channel Bonding Driver: v3.3.0 (June 10, 2008)
>>
>> Bonding Mode: IEEE 802.3ad Dynamic link aggregation
>> Transmit Hash Policy: layer2 (0)
>> MII Status: up
>> MII Polling Interval (ms): 100
>> Up Delay (ms): 0
>> Down Delay (ms): 0
>>
>> 802.3ad info
>> LACP rate: slow
>> Active Aggregator Info:
>>        Aggregator ID: 2
>>        Number of ports: 4
>>        Actor Key: 9
>>        Partner Key: 3
>>        Partner Mac Address: 00:1f:28:63:4c:00
>>
>> Slave Interface: eth2
>> MII Status: up
>> Link Failure Count: 1
>> Permanent HW addr: 00:15:17:76:08:f1
>> Aggregator ID: 2
>>
>> Slave Interface: eth3
>> MII Status: up
>> Link Failure Count: 1
>> Permanent HW addr: 00:15:17:76:08:f0
>> Aggregator ID: 2
>>
>> Slave Interface: eth4
>> MII Status: up
>> Link Failure Count: 1
>> Permanent HW addr: 00:15:17:76:08:f3
>> Aggregator ID: 2
>>
>> Slave Interface: eth5
>> MII Status: up
>> Link Failure Count: 1
>> Permanent HW addr: 00:15:17:76:08:f2
>> Aggregator ID: 2
>>
>>
>> And here's the output of 'ip addr show':
>>
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>>    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
>> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>> state UP qlen 1000
>>    link/ether 00:e0:81:b0:70:9a brd ff:ff:ff:ff:ff:ff
>>    inet 10.0.0.251/24 brd 10.0.0.255 scope global eth0
>> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast
>> state UP qlen 1000
>>    link/ether 00:e0:81:b0:70:9b brd ff:ff:ff:ff:ff:ff
>>    inet 192.168.3.1/24 brd 192.168.3.255 scope global eth1
>> 4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc
>> pfifo_fast master bond0 state UP qlen 1000
>>    link/ether 00:15:17:76:08:f1 brd ff:ff:ff:ff:ff:ff
>> 5: eth3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc
>> pfifo_fast master bond0 state UP qlen 1000
>>    link/ether 00:15:17:76:08:f1 brd ff:ff:ff:ff:ff:ff
>> 6: eth4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc
>> pfifo_fast master bond0 state UP qlen 1000
>>    link/ether 00:15:17:76:08:f1 brd ff:ff:ff:ff:ff:ff
>> 7: eth5: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc
>> pfifo_fast master bond0 state UP qlen 1000
>>    link/ether 00:15:17:76:08:f1 brd ff:ff:ff:ff:ff:ff
>> 8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc
>> noqueue state UP
>>    link/ether 00:15:17:76:08:f1 brd ff:ff:ff:ff:ff:ff
>>    inet 192.168.3.3/24 brd 192.168.3.255 scope global bond0
>> 9: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
>> pfifo_fast state UNKNOWN qlen 100
>>    link/[65534]
>>    inet 10.8.0.1 peer 10.8.0.2/32 scope global tun0
>>
>>
>> Best regards,
>> Ejner Fergo
>>
>>
>> On Wed, Nov 18, 2009 at 9:46 PM, Simon Kelley <simon at thekelleys.org.uk>
>> wrote:
>>>
>>> Ejner Fergo wrote:
>>>>
>>>> Hola all,
>>>>
>>>> I'm a happy dnsmasq user for a couple of years now, though it is first
>>>> now I turn to this list to hopefully get some help.
>>>>
>>>> I run dnsmasq on a server with 6 NICs, where 'eth0' talks to the
>>>> outside world and 'eth1' is for the local network. The last 4 is
>>>> bonded into 'bond0'.
>>>> My problem is I only want to have 'eth1' to listen/respond to DNS/DHCP
>>>> requests, but no matter which option I use (interface,
>>>> except-interface, listen-address) the setup breaks and the
>>>> workstations can't get an address. If all these options are commented
>>>> out, everything works just fine but some workstations see 'bond0' as
>>>> the nameserver instead of 'eth1'.
>>>>
>>>> Looking at /var/log/messages on the server shows that it is random
>>>> whether 'eth1' or 'bond0' is used, for example:
>>>>
>>>
>>> Hi,
>>>
>>> Could you send the output from these two commands, please?
>>>
>>> cat /proc/net/bonding/bond0
>>> ip addr show
>>>
>>> Cheers,
>>>
>>> Simon.
>>>
>>
>
>