On Thu, May 13, 2010 at 3:17 PM, Michael Rack <[email protected]> wrote: > 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. 13 Fax.: +49 8654 670438 > D-83395 Freilassing www.rsm-freilassing.de > > > Am 13.05.2010 20:33, schrieb Rance Hall: >> On Thu, May 13, 2010 at 1:24 PM, Michael Rack >> <[email protected]> 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? >>
Sorry, I've been in a seminar all week and I'm not currently in my best form. Should have just let it go till I had had a nap. Something in the ifconfig output doesnt look "right" to me. But I'll qualify that by saying I still need a nap.
