DHCPOFFER aber kein DHCPREQUEST

[AthLux]

Hallöchen

Ich versuche seit einigen Tagen meinen DHCP-Server auf einen anderen Rechner
(UML an tap0) zu verlegen.

Da dieser in einem anderen Segment, am virtuellen Device tap0, hängt kann ich ihn von den Clients nicht mehr direkt erreichen und verwende daher dafür dhcrelay.
Leider funktioiniert das ganze nicht.
Läuft der DHCP-Server am Rechner1, so funkt alles. Läuft am Rechner1 der DHCRelay und der DHCP-Server am Rechner2, so geht es nicht mehr.

Konfig1: DHCP-Server am Rechner1, alles geht:
/var/log/messages:
Feb 21 21:22:19 AthLux dhcpd: Warning: subnet 192.168.0.0/24 overlaps subnet 192.168.0.0/24
Feb 21 21:22:19 AthLux dhcpd: Wrote 0 deleted host decls to leases file.
Feb 21 21:22:19 AthLux dhcpd: Wrote 0 new dynamic host decls to leases file.
Feb 21 21:22:19 AthLux dhcpd: Wrote 0 leases to leases file.
Feb 21 21:22:19 AthLux dhcpd: Multiple interfaces match the same subnet: eth1 tap0
Feb 21 21:22:19 AthLux dhcpd: Multiple interfaces match the same shared network: eth1 tap0
Feb 21 21:22:19 AthLux dhcpd: dhcpd startup succeeded
Feb 21 21:22:51 AthLux dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via eth1
Feb 21 21:22:51 AthLux dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via eth1
Feb 21 21:22:51 AthLux dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via eth1
Feb 21 21:22:51 AthLux dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via eth1

Konfig2: DHCRelay am Rechner1, DHCP-Server am Rechner2, nix geht:
Feb 21 15:24:21 Domain dhcpd: Wrote 0 deleted host decls to leases file.
Feb 21 15:24:21 Domain dhcpd: Wrote 0 new dynamic host decls to leases file.
Feb 21 15:24:21 Domain dhcpd: Wrote 0 leases to leases file.
Feb 21 15:24:21 Domain dhcpd: dhcpd startup succeeded
Feb 21 15:24:58 Domain dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:24:58 Domain dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:24:58 Domain dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:24:58 Domain dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:02 Domain dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:02 Domain dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:02 Domain dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:02 Domain dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:11 Domain dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:11 Domain dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:11 Domain dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:11 Domain dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:27 Domain dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:27 Domain dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:27 Domain dhcpd: DHCPREQUEST for 192.168.0.253 from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:25:27 Domain dhcpd: DHCPACK on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:00 Domain dhcpd: DHCPDISCOVER from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:00 Domain dhcpd: DHCPOFFER on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:00 Domain dhcpd: DHCPDISCOVER from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:00 Domain dhcpd: DHCPOFFER on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:04 Domain dhcpd: DHCPDISCOVER from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:04 Domain dhcpd: DHCPOFFER on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:04 Domain dhcpd: DHCPDISCOVER from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:04 Domain dhcpd: DHCPOFFER on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:12 Domain dhcpd: DHCPDISCOVER from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:12 Domain dhcpd: DHCPOFFER on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:12 Domain dhcpd: DHCPDISCOVER from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:12 Domain dhcpd: DHCPOFFER on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:31 Domain dhcpd: DHCPDISCOVER from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:31 Domain dhcpd: DHCPOFFER on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:31 Domain dhcpd: DHCPDISCOVER from 00:50:56:09:00:67 via 192.168.0.254
Feb 21 15:26:31 Domain dhcpd: DHCPOFFER on 192.168.0.253 to 00:50:56:09:00:67 via 192.168.0.254

Routing?, Client-Konfig?
Ich bin Ratlos
Hat einer nen Rat?

[Laurs]

Tach!

Man muss beim Start von DHCRelay Interfaces angeben, an denen Requests und Replys "gehört" werden. Also quasi
dhcrelay -i eth0 -i eth1 IP_VOM_SERVER
So werden die Bootrequest vom Client an den Server übertragen und die Bootreplies, kommend vom anderen Netz, an den Client zurück.
Mit der Option -d läuft der Relay im Vordergrund, und verrät, ob er was tut!

Gruss
Stefan