Re: [Dnsmasq-discuss] could not bind dnsmasq to mutiple interfaces with same ip-address ... success report

2010-05-16 Thread Michael Rack

Hi Simon,

now i changed every interface-line to a listen-address-line. All is 
working just fine :-D Including DHCP and DNS.


Perfect. Thank you !

Liebe Grüße aus Freilassing,

Michael Rack
RSM Freilassing
--
RSM Freilassing Tel.: +49 8654 607110
Nocksteinstr. 13Fax.: +49 8654 670438
D-83395 Freilassingwww.rsm-freilassing.de


Am 15.05.2010 05:00, schrieb Michael Rack:

Am 14.05.2010 16:08, schrieb Simon Kelley:
   

Different versions of dnsmasq? I only looked at the latest code to see
how it would behave with repeated IP addresses, older code may break
differently
 

dnsmasq -v prints the same Version 2.52 *strange*

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
   




Re: [Dnsmasq-discuss] could not bind dnsmasq to mutiple interfaces with same ip-address

2010-05-15 Thread Michael Rack

Am 14.05.2010 16:08, schrieb Simon Kelley:

Different versions of dnsmasq? I only looked at the latest code to see
how it would behave with repeated IP addresses, older code may break
differently

dnsmasq -v prints the same Version 2.52 *strange*



Re: [Dnsmasq-discuss] could not bind dnsmasq to mutiple interfaces with same ip-address

2010-05-14 Thread Simon Kelley
Michael Rack wrote:
 Hi Simon!
 
 I've installed dnsmasq to my new servers i bought. I copied all files 
 original as of the old server. But on startup i get this error message:
 dnsmasq: unknown interface bond5
 
 after removing bond5 i got the following error message:
 dnsmasq: unknown interface bond4
 
 after removing bond4, dnsmasq startet properly.
 
 The thing is, that every interface become the same ip-address in future. 
 The same configuration was already running on my old server, but wont 
 run on the new one.
 
 5: bond0: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
 UNKNOWN
 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
 inet 81.95.14.97/30 brd 81.95.14.99 scope global bond0
 6: bond1: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
 UNKNOWN
 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
 inet 81.95.14.101/30 brd 81.95.14.103 scope global bond1
 7: bond2: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
 UNKNOWN
 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
 inet 81.95.14.105/30 brd 81.95.14.107 scope global bond2
 8: bond3: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
 UNKNOWN
 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
 inet 91.205.12.0/32 brd 255.255.255.255 scope global bond3
 9: bond4: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
 UNKNOWN
 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
 inet 91.205.12.0/32 brd 255.255.255.255 scope global bond4
 10: bond5: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue 
 state UNKNOWN
 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
 inet 91.205.12.0/32 brd 255.255.255.255 scope global bond5
 
 The configurationfile looks like the following:
 
 interface=bond0
 interface=bond1
 interface=bond3
 #interface=bond4
 #interface=bond5
 bind-interfaces

 # PID File
 pid-file=/var/run/dnsmasq.pid

 # Konfigurations-Directory einlesen
 conf-dir=/etc/dnsmasq.d
 
 Can you see the Problem?

More than one interface with the same address is causing confusion. That
seems a very strange thing to do, but commenting out bond4 and bond5
won't cause any problems, dnsmasq will still be listening on 91.205.12.0
Unless there's a good reason, removing bind-interfaces will make this
configuration much easier to use.


HTH


Simon.

 
 Liebe Grüße aus Freilassing,
 
 Michael Rack
 RSM Freilassing




Re: [Dnsmasq-discuss] could not bind dnsmasq to mutiple interfaces with same ip-address

2010-05-14 Thread Simon Kelley
Michael Rack wrote:
 I have in mind, that dnsmasq does not handle DHCP Requests if there is a
 ip-address configured. I switched then to bind-interfaces...

you can use --interface without --bind-interfaces
 
 But why is the same config not working as before?
 DNSMAQ did not had problems on my old server with this configuration.

Different versions of dnsmasq? I only looked at the latest code to see
how it would behave with repeated IP addresses, older code may break
differently.

Cheers,
Simon.

 
 
 Am 14.05.2010 11:01, schrieb Simon Kelley:
 More than one interface with the same address is causing confusion. That
 seems a very strange thing to do, but commenting out bond4 and bond5
 won't cause any problems, dnsmasq will still be listening on 91.205.12.0
 Unless there's a good reason, removing bind-interfaces will make this
 configuration much easier to use.


 HTH


 Simon.

 




[Dnsmasq-discuss] could not bind dnsmasq to mutiple interfaces with same ip-address

2010-05-13 Thread Michael Rack

Hi Simon!

I've installed dnsmasq to my new servers i bought. I copied all files 
original as of the old server. But on startup i get this error message:

dnsmasq: unknown interface bond5


after removing bond5 i got the following error message:

dnsmasq: unknown interface bond4


after removing bond4, dnsmasq startet properly.

The thing is, that every interface become the same ip-address in future. 
The same configuration was already running on my old server, but wont 
run on the new one.


5: bond0: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
UNKNOWN

link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 81.95.14.97/30 brd 81.95.14.99 scope global bond0
6: bond1: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
UNKNOWN

link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 81.95.14.101/30 brd 81.95.14.103 scope global bond1
7: bond2: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
UNKNOWN

link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 81.95.14.105/30 brd 81.95.14.107 scope global bond2
8: bond3: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
UNKNOWN

link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 91.205.12.0/32 brd 255.255.255.255 scope global bond3
9: bond4: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue state 
UNKNOWN

link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 91.205.12.0/32 brd 255.255.255.255 scope global bond4
10: bond5: BROADCAST,MULTICAST,MASTER,UP mtu 1460 qdisc noqueue 
state UNKNOWN

link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 91.205.12.0/32 brd 255.255.255.255 scope global bond5


The configurationfile looks like the following:


interface=bond0
interface=bond1
interface=bond3
#interface=bond4
#interface=bond5
bind-interfaces

# PID File
pid-file=/var/run/dnsmasq.pid

# Konfigurations-Directory einlesen
conf-dir=/etc/dnsmasq.d


Can you see the Problem?

Liebe Grüße aus Freilassing,

Michael Rack
RSM Freilassing
--
RSM Freilassing Tel.: +49 8654 607110
Nocksteinstr. 13Fax.: +49 8654 670438
D-83395 Freilassingwww.rsm-freilassing.de




Re: [Dnsmasq-discuss] could not bind dnsmasq to mutiple interfaces with same ip-address

2010-05-13 Thread Rance Hall
On Thu, May 13, 2010 at 1:24 PM, Michael Rack
michael.r...@rsm-freilassing.de wrote:
 Hi Simon!

 I've installed dnsmasq to my new servers i bought. I copied all files
 original as of the old server. But on startup i get this error message:
 dnsmasq: unknown interface bond5

 after removing bond5 i got the following error message:
 dnsmasq: unknown interface bond4

 after removing bond4, dnsmasq startet properly.



I have never seen this error unless the interface really didn't exist.
 your removing the bond5 entry from the config file seems to suggest
that the IF really doesnt exist.

What does ifconfig say?



Re: [Dnsmasq-discuss] could not bind dnsmasq to mutiple interfaces with same ip-address

2010-05-13 Thread Michael Rack

The interfaces configuration was attached to my mail.


bond0 Link encap:Ethernet  HWaddr 00:00:00:00:00:00
  inet addr:81.95.14.97  Bcast:81.95.14.99  Mask:255.255.255.252
  UP BROADCAST RUNNING MASTER MULTICAST  MTU:1460  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

bond1 Link encap:Ethernet  HWaddr 00:00:00:00:00:00
  inet addr:81.95.14.101  Bcast:81.95.14.103  Mask:255.255.255.252
  UP BROADCAST RUNNING MASTER MULTICAST  MTU:1460  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

bond2 Link encap:Ethernet  HWaddr 00:00:00:00:00:00
  inet addr:81.95.14.105  Bcast:81.95.14.107  Mask:255.255.255.252
  UP BROADCAST RUNNING MASTER MULTICAST  MTU:1460  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

bond3 Link encap:Ethernet  HWaddr 00:00:00:00:00:00
  inet addr:91.205.12.0  Bcast:255.255.255.255  
Mask:255.255.255.255

  UP BROADCAST RUNNING MASTER MULTICAST  MTU:1460  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

bond4 Link encap:Ethernet  HWaddr 00:00:00:00:00:00
  inet addr:91.205.12.0  Bcast:255.255.255.255  
Mask:255.255.255.255

  UP BROADCAST RUNNING MASTER MULTICAST  MTU:1460  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

bond5 Link encap:Ethernet  HWaddr 00:00:00:00:00:00
  inet addr:91.205.12.0  Bcast:255.255.255.255  
Mask:255.255.255.255

  UP BROADCAST RUNNING MASTER MULTICAST  MTU:1460  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


No interface is currently up / no real interface is attached to the 
bonding-device. But without dnsmasq starts without problems, so the 
interface status does not matter. The Interface is really up, as you can 
see.


Liebe Grüße aus Freilassing,

Michael Rack
RSM Freilassing
--
RSM Freilassing Tel.: +49 8654 607110
Nocksteinstr. 13Fax.: +49 8654 670438
D-83395 Freilassingwww.rsm-freilassing.de


Am 13.05.2010 20:33, schrieb Rance Hall:

On Thu, May 13, 2010 at 1:24 PM, Michael Rack
michael.r...@rsm-freilassing.de  wrote:
   

Hi Simon!

I've installed dnsmasq to my new servers i bought. I copied all files
original as of the old server. But on startup i get this error message:
 

dnsmasq: unknown interface bond5
   

after removing bond5 i got the following error message:
 

dnsmasq: unknown interface bond4
   

after removing bond4, dnsmasq startet properly.

 


I have never seen this error unless the interface really didn't exist.
  your removing the bond5 entry from the config file seems to suggest
that the IF really doesnt exist.

What does ifconfig say?

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss