Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 21 replies
  • Subscribers 8 subscribers
  • Views 4494 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM vergibt keine IP mehr

m_vetdoc

installierte Version: UTM 9.712-13

Seit vielen Jahren nutze ich die UTM zur Absicherung meines Netzwerkes.

Die UTM läuft auf 192.168.2.1.

In diesem Netz 192.168.2.x (eth0) laufen die Eltern-PCs, unsere Kinder haben ihr eigenes Netz 192.168.1.x (eth1)

Die Netzwerkdienste DHCP, DNS und NTP sind konfiguriert, natürlich auch die Firewall. DHCP sind für die IPs 250-254 konfiguriert. Die Pcs der Kinder sind auf .71 und .72 definiert.

Das Ganze lief geschmeidig und ohne Probleme seit vielen Jahren.

Nur seit Wochen bekommen die PCs der Kinder ihre IP nicht mehr von der UTM zugeteilt. Auch wenn ich eine feste IP konfiguriere kommt keine Netzwerkverbindung zustande. Im Dashboard sehe ich beim Einschalten der PCs einen mini Verkehr, aber das war es dann auch schon.

Verändert habe ich an der Konfig der UTM eigentlich nichts. 

Ich finde nicht den Grund, warum das Netz 192.168.1.x nicht mehr läuft und bitte hier um Hilfe.



This thread was automatically locked due to age.
Parents
  • 0

    Hallo,

    Herzlich willkommen hier in der Community !

    (Sorry, my German-speaking brain isn't creating thoughts at the moment. Frowning2)

    Copy here the lines from the DHCP log when you reboot one of the children's PCs.

    MfG - Bob (Bitte auf Deutsch weiterhin.)

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hallo Bob,

    danke für die Rückmeldung. Es ist zwar heute meine erste Post hier, lese aber schon seit Jahren still mit. :-)

    Ich habe den DHCP-Server zuerst deaktiviert um dann wieder zu aktivieren. Dann erst den PC meiner Tochter gestartet.

    Hier das Log:

    2022:09:23-17:18:08 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:23-17:18:08 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:23-17:18:08 utm dhcpd: All rights reserved.
2022:09:23-17:18:08 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:23-17:18:08 utm dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
2022:09:23-17:18:08 utm dhcpd: Config file: /etc/dhcpd.conf
2022:09:23-17:18:08 utm dhcpd: Database file: /var/state/dhcp/dhcpd.leases
2022:09:23-17:18:08 utm dhcpd: PID file: /var/run/dhcpd.pid
2022:09:23-17:18:08 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:23-17:18:08 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:23-17:18:08 utm dhcpd: All rights reserved.
2022:09:23-17:18:08 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:23-17:18:08 utm dhcpd: Wrote 0 deleted host decls to leases file.
2022:09:23-17:18:08 utm dhcpd: Wrote 0 new dynamic host decls to leases file.
2022:09:23-17:18:08 utm dhcpd: Wrote 0 leases to leases file.
2022:09:23-17:18:08 utm dhcpd: Listening on LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:08 utm dhcpd: Sending on   LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:08 utm dhcpd: Sending on   Socket/fallback/fallback-net
2022:09:23-17:18:08 utm dhcpd: Server starting service.
2022:09:23-17:18:11 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:23-17:18:11 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:23-17:18:11 utm dhcpd: All rights reserved.
2022:09:23-17:18:11 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:23-17:18:11 utm dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
2022:09:23-17:18:11 utm dhcpd: Config file: /etc/dhcpd.conf
2022:09:23-17:18:11 utm dhcpd: Database file: /var/state/dhcp/dhcpd.leases
2022:09:23-17:18:11 utm dhcpd: PID file: /var/run/dhcpd.pid
2022:09:23-17:18:11 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:23-17:18:11 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:23-17:18:11 utm dhcpd: All rights reserved.
2022:09:23-17:18:11 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:23-17:18:11 utm dhcpd: Wrote 0 deleted host decls to leases file.
2022:09:23-17:18:11 utm dhcpd: Wrote 0 new dynamic host decls to leases file.
2022:09:23-17:18:11 utm dhcpd: Wrote 0 leases to leases file.
2022:09:23-17:18:11 utm dhcpd: Listening on LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:11 utm dhcpd: Sending on   LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:11 utm dhcpd: Sending on   Socket/fallback/fallback-net
2022:09:23-17:18:11 utm dhcpd: Server starting service.
2022:09:23-17:18:12 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:23-17:18:12 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:23-17:18:12 utm dhcpd: All rights reserved.
2022:09:23-17:18:12 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:23-17:18:12 utm dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
2022:09:23-17:18:12 utm dhcpd: Config file: /etc/dhcpd.conf
2022:09:23-17:18:12 utm dhcpd: Database file: /var/state/dhcp/dhcpd.leases
2022:09:23-17:18:12 utm dhcpd: PID file: /var/run/dhcpd.pid
2022:09:23-17:18:12 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:23-17:18:12 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:23-17:18:12 utm dhcpd: All rights reserved.
2022:09:23-17:18:12 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:23-17:18:12 utm dhcpd: Wrote 0 deleted host decls to leases file.
2022:09:23-17:18:12 utm dhcpd: Wrote 0 new dynamic host decls to leases file.
2022:09:23-17:18:12 utm dhcpd: Wrote 0 leases to leases file.
2022:09:23-17:18:12 utm dhcpd: Listening on LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:12 utm dhcpd: Sending on   LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:12 utm dhcpd: Listening on LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:23-17:18:12 utm dhcpd: Sending on   LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:23-17:18:12 utm dhcpd: Sending on   Socket/fallback/fallback-net
2022:09:23-17:18:12 utm dhcpd: Server starting service.
2022:09:23-17:18:32 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:18:32 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:18:36 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:18:36 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:18:39 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:18:39 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:18:48 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:18:48 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:19:05 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:19:05 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:19:36 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:19:36 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:19:41 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:19:41 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:19:50 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:19:50 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:20:07 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:23-17:20:07 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1

    Mehr Datenverkehr gibt es nicht auf eth1

    Grüssle

    Alex

  • 0 in reply to Amodin

    Nein, an den Kinder-PCs wurde nichts geändert. Sind immer noch die gleichen NUCs.

    Den PC der Tochter habe ich heute mal in das Netz der Eltern 192.168.2.x gestellt und sofort mit Start wurde von der UTM eine DHCP-IP vergeben. Also der PC läuft richtig.

    In Netzwerkdefinitionen stimmen die MAC Adressen auch noch überein.

    Es muss ein UTM Problem sein, denn wie geschrieben an den Kinder-PCs wurde nichts verändert, weder Hardware noch in den Settings.

  • 0 in reply to m_vetdoc

    Hallo Alex,

    What do you see in the DHCP log when you connected your daughter's PC to the parents' net?

    After you reconnected her PC to the Kinder net, did she then get an IP?  If not, show us the few lines where the PC tried and failed as in the log above.

    Also, it would be interesting to insert pictures of the Edits of the two DHCP servers with 'Advanced' open.

    MfG - Bob (Bitte auf Deutsch weiterhin.)
    PS Amodin kann auch Deutsch

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to m_vetdoc

    Mir fällt auf, daß der DHCP unterschiedliche Scopes hat.

    Beim ersten Start steht:

    2022:09:23-17:18:08 utm dhcpd: Listening on LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:08 utm dhcpd: Sending on   LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:08 utm dhcpd: Sending on   Socket/fallback/fallback-net
2022:09:23-17:18:08 utm dhcpd: Server starting service.

    beim zweiten hingegen:

    2022:09:23-17:18:12 utm dhcpd: Wrote 0 leases to leases file.
2022:09:23-17:18:12 utm dhcpd: Listening on LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:12 utm dhcpd: Sending on   LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:23-17:18:12 utm dhcpd: Listening on LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:23-17:18:12 utm dhcpd: Sending on   LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:23-17:18:12 utm dhcpd: Sending on   Socket/fallback/fallback-net
2022:09:23-17:18:12 utm dhcpd: Server starting service.

    Hast Du in diesen vier Sekunden irgendwas geändert (z.B. einen Schiebeschalter betätigt)?

  • 0 in reply to Alan Brand

    Ja, ich hatte in diesen vier Sekunden die beiden DHCP-Server 192.168.2.x und 192.168.1.x je einmal deaktiviert und dann wieder aktiviert.

  • 0 in reply to BAlfson

    What do you see in the DHCP log when you connected your daughter's PC to the parents' net?


    2022:09:24-03:50:48 utm dhcpd: DHCPREQUEST for 192.168.2.96 from 38:9d:92:d3:3d:2f via eth0
2022:09:24-03:50:48 utm dhcpd: DHCPACK on 192.168.2.96 to 38:9d:92:d3:3d:2f via eth0
2022:09:24-12:44:18 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:24-12:44:18 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:24-12:44:18 utm dhcpd: All rights reserved.
2022:09:24-12:44:18 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:24-12:44:18 utm dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
2022:09:24-12:44:18 utm dhcpd: Config file: /etc/dhcpd.conf
2022:09:24-12:44:18 utm dhcpd: Database file: /var/state/dhcp/dhcpd.leases
2022:09:24-12:44:18 utm dhcpd: PID file: /var/run/dhcpd.pid
2022:09:24-12:44:18 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:24-12:44:18 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:24-12:44:18 utm dhcpd: All rights reserved.
2022:09:24-12:44:18 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:24-12:44:18 utm dhcpd: Wrote 0 deleted host decls to leases file.
2022:09:24-12:44:18 utm dhcpd: Wrote 0 new dynamic host decls to leases file.
2022:09:24-12:44:18 utm dhcpd: Wrote 0 leases to leases file.
2022:09:24-12:44:18 utm dhcpd: Listening on LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:24-12:44:18 utm dhcpd: Sending on   LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:24-12:44:18 utm dhcpd: Listening on LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:24-12:44:18 utm dhcpd: Sending on   LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:24-12:44:18 utm dhcpd: Sending on   Socket/fallback/fallback-net
2022:09:24-12:44:18 utm dhcpd: Server starting service.
2022:09:24-12:47:01 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:24-12:47:01 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:24-12:47:01 utm dhcpd: All rights reserved.
2022:09:24-12:47:01 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:24-12:47:01 utm dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
2022:09:24-12:47:01 utm dhcpd: Config file: /etc/dhcpd.conf
2022:09:24-12:47:01 utm dhcpd: Database file: /var/state/dhcp/dhcpd.leases
2022:09:24-12:47:01 utm dhcpd: PID file: /var/run/dhcpd.pid
2022:09:24-12:47:01 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:24-12:47:01 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:24-12:47:01 utm dhcpd: All rights reserved.
2022:09:24-12:47:01 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:24-12:47:01 utm dhcpd: Wrote 0 deleted host decls to leases file.
2022:09:24-12:47:01 utm dhcpd: Wrote 0 new dynamic host decls to leases file.
2022:09:24-12:47:01 utm dhcpd: Wrote 0 leases to leases file.
2022:09:24-12:47:01 utm dhcpd: Listening on LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:24-12:47:01 utm dhcpd: Sending on   LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:24-12:47:01 utm dhcpd: Listening on LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:24-12:47:01 utm dhcpd: Sending on   LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:24-12:47:01 utm dhcpd: Sending on   Socket/fallback/fallback-net
2022:09:24-12:47:01 utm dhcpd: Server starting service.
2022:09:24-12:49:02 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:02 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:05 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:05 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:13 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:13 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:30 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:30 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:00 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:00 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:04 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:04 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:08 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:08 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:16 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:16 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:32 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:32 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:04 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:04 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:08 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:08 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:17 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:17 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:34 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:34 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:55:31 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth0
2022:09:24-12:55:32 utm dhcpd: DHCPOFFER on 192.168.2.253 to c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth0
2022:09:24-12:55:32 utm dhcpd: DHCPREQUEST for 192.168.2.253 (192.168.2.1) from c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth0
2022:09:24-12:55:32 utm dhcpd: DHCPACK on 192.168.2.253 to c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth0

    After you reconnected her PC to the Kinder net, did she then get an IP?  If not, show us the few lines where the PC tried and failed as in the log above.

    Nein, sie bekommt keine IP.

    2022:09:24-03:50:48 utm dhcpd: DHCPREQUEST for 192.168.2.96 from 38:9d:92:d3:3d:2f via eth0
2022:09:24-03:50:48 utm dhcpd: DHCPACK on 192.168.2.96 to 38:9d:92:d3:3d:2f via eth0
2022:09:24-12:44:18 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:24-12:44:18 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:24-12:44:18 utm dhcpd: All rights reserved.
2022:09:24-12:44:18 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:24-12:44:18 utm dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
2022:09:24-12:44:18 utm dhcpd: Config file: /etc/dhcpd.conf
2022:09:24-12:44:18 utm dhcpd: Database file: /var/state/dhcp/dhcpd.leases
2022:09:24-12:44:18 utm dhcpd: PID file: /var/run/dhcpd.pid
2022:09:24-12:44:18 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:24-12:44:18 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:24-12:44:18 utm dhcpd: All rights reserved.
2022:09:24-12:44:18 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:24-12:44:18 utm dhcpd: Wrote 0 deleted host decls to leases file.
2022:09:24-12:44:18 utm dhcpd: Wrote 0 new dynamic host decls to leases file.
2022:09:24-12:44:18 utm dhcpd: Wrote 0 leases to leases file.
2022:09:24-12:44:18 utm dhcpd: Listening on LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:24-12:44:18 utm dhcpd: Sending on   LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:24-12:44:18 utm dhcpd: Listening on LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:24-12:44:18 utm dhcpd: Sending on   LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:24-12:44:18 utm dhcpd: Sending on   Socket/fallback/fallback-net
2022:09:24-12:44:18 utm dhcpd: Server starting service.
2022:09:24-12:47:01 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:24-12:47:01 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:24-12:47:01 utm dhcpd: All rights reserved.
2022:09:24-12:47:01 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:24-12:47:01 utm dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
2022:09:24-12:47:01 utm dhcpd: Config file: /etc/dhcpd.conf
2022:09:24-12:47:01 utm dhcpd: Database file: /var/state/dhcp/dhcpd.leases
2022:09:24-12:47:01 utm dhcpd: PID file: /var/run/dhcpd.pid
2022:09:24-12:47:01 utm dhcpd: Internet Systems Consortium DHCP Server 4.4.1
2022:09:24-12:47:01 utm dhcpd: Copyright 2004-2018 Internet Systems Consortium.
2022:09:24-12:47:01 utm dhcpd: All rights reserved.
2022:09:24-12:47:01 utm dhcpd: For info, please visit https://www.isc.org/software/dhcp/
2022:09:24-12:47:01 utm dhcpd: Wrote 0 deleted host decls to leases file.
2022:09:24-12:47:01 utm dhcpd: Wrote 0 new dynamic host decls to leases file.
2022:09:24-12:47:01 utm dhcpd: Wrote 0 leases to leases file.
2022:09:24-12:47:01 utm dhcpd: Listening on LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:24-12:47:01 utm dhcpd: Sending on   LPF/eth0/00:0c:29:36:96:7e/192.168.2.0/24
2022:09:24-12:47:01 utm dhcpd: Listening on LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:24-12:47:01 utm dhcpd: Sending on   LPF/eth1/00:0c:29:36:96:60/192.168.1.0/24
2022:09:24-12:47:01 utm dhcpd: Sending on   Socket/fallback/fallback-net
2022:09:24-12:47:01 utm dhcpd: Server starting service.
2022:09:24-12:49:02 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:02 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:05 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:05 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:13 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:13 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:30 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:49:30 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:00 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:00 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:04 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:04 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:08 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:08 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:16 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:16 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:32 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:50:32 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:04 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:04 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:08 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:08 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:17 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:17 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:34 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:51:34 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-12:55:31 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth0
2022:09:24-12:55:32 utm dhcpd: DHCPOFFER on 192.168.2.253 to c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth0
2022:09:24-12:55:32 utm dhcpd: DHCPREQUEST for 192.168.2.253 (192.168.2.1) from c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth0
2022:09:24-12:55:32 utm dhcpd: DHCPACK on 192.168.2.253 to c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth0
2022:09:24-13:04:08 utm dhcpd: DHCPREQUEST for 192.168.2.253 from c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth1: wrong network.
2022:09:24-13:04:08 utm dhcpd: DHCPNAK on 192.168.2.253 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:10 utm dhcpd: DHCPREQUEST for 192.168.2.253 from c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth1: wrong network.
2022:09:24-13:04:10 utm dhcpd: DHCPNAK on 192.168.2.253 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:13 utm dhcpd: DHCPREQUEST for 192.168.2.253 from c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth1: wrong network.
2022:09:24-13:04:13 utm dhcpd: DHCPNAK on 192.168.2.253 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:19 utm dhcpd: DHCPREQUEST for 192.168.2.253 from c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth1: wrong network.
2022:09:24-13:04:19 utm dhcpd: DHCPNAK on 192.168.2.253 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:21 utm dhcpd: DHCPREQUEST for 192.168.2.253 from c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth1: wrong network.
2022:09:24-13:04:21 utm dhcpd: DHCPNAK on 192.168.2.253 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:24 utm dhcpd: DHCPREQUEST for 192.168.2.253 from c0:3f:d5:65:e2:19 (Mathilda-nuc) via eth1: wrong network.
2022:09:24-13:04:24 utm dhcpd: DHCPNAK on 192.168.2.253 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:39 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:39 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:44 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:44 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:48 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:48 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:56 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:04:56 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:05:11 utm dhcpd: DHCPDISCOVER from c0:3f:d5:65:e2:19 via eth1
2022:09:24-13:05:11 utm dhcpd: DHCPOFFER on 192.168.1.72 to c0:3f:d5:65:e2:19 via eth1

  • 0 in reply to m_vetdoc

    Nur neugierig, warum ist die Lease-Zeit für Kinder auf 10 Minuten eingestellt? Alle 10 Minuten werden sie nach einer IP-Adresse fragen.
    Haben Sie versucht, DHCP zu entfernen und neu zu erstellen?

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    Keine Ahnung, nicht bewußt auf 10 Minuten gestellt.

    Du meinst, ob ich den DHCP-Server schon einmal gelöscht und wieder neu angelegt habe? Nein, habe ich nicht.

    Dann mach ich das mal und teste.

  • 0 in reply to m_vetdoc
    m_vetdoc said:

    Du meinst, ob ich den DHCP-Server schon einmal gelöscht und wieder neu angelegt habe? Nein, habe ich nicht.

    Ja das würde ich versuchen. Vielleicht gibt es ein Problem mit DHCP.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    Beide DHCP Server gelöscht, UTM neu gestartet, wieder Beide angelegt.

    Es ändert sich nichts - keine IP Zuteilung.

    Übrigens, auch wenn ich eine feste IP4 dem Kinder-Nuc zuweise, kommt keine Verbindung zustande.

    Ich verstehe es nicht.

  • 0 in reply to m_vetdoc

    Have you checked wires, switch ports?  Anything potentially moved close that would interfere?  

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

Reply
  • 0 in reply to m_vetdoc

    Have you checked wires, switch ports?  Anything potentially moved close that would interfere?  

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

Children
Unfiltered HTML