Hello Forum hello experts!
I am from Germany and am trying my best English to describe my problem.
I have a Raspi4 with Nxfilter connected directly via LAN-cable to a Router/Modem Fritzbox 7590. Now I want to turn off the DHCP service on my Fritzbox and let Nx do the job, but...
Although the service is running on NX, the IP settings, including the statically assigned IPs, are entered, and there are no conflicts with other services and running DHCP, NX does not want to/cannot provide any end device with an IP!
As soon as I turn off the DHCP service on the FritzBox, my home network goes down, meaning that all devices connected to the LAN and WiFi can no longer communicate with the internet.
No devices appear under “Leased IP”!
Restarting the end devices, the Pi with NXFilter, or the FritzBox did not help.
Turning on/off the "Prevent conflict" did not help.
Changeing the IP-Range for the DHCP didnt help.
What works: Giving a Device a manual fixed IP adress (e.g. 192.168.201) , Gateway 192.168.178.1; DNS 192.168.178.9), put it with MAC-adress in the "Reserved-IP" menue and connect it via WiFi direct with the NXFilter! I have connection & internet, but cant see it in the "Lease" because it was not really getting a IP adress from NX-DHCP.
I have tried all the standard solutions without success.
Nx on Pi: 192.168.178.9
FritzBox: IP 192.168.178.1


I did some troubleshooting on cmd:
Can anyone help me solve this?
Many thnaks & regards
NeX
I am from Germany and am trying my best English to describe my problem.
I have a Raspi4 with Nxfilter connected directly via LAN-cable to a Router/Modem Fritzbox 7590. Now I want to turn off the DHCP service on my Fritzbox and let Nx do the job, but...
Although the service is running on NX, the IP settings, including the statically assigned IPs, are entered, and there are no conflicts with other services and running DHCP, NX does not want to/cannot provide any end device with an IP!
As soon as I turn off the DHCP service on the FritzBox, my home network goes down, meaning that all devices connected to the LAN and WiFi can no longer communicate with the internet.
No devices appear under “Leased IP”!
Restarting the end devices, the Pi with NXFilter, or the FritzBox did not help.
Turning on/off the "Prevent conflict" did not help.
Changeing the IP-Range for the DHCP didnt help.
What works: Giving a Device a manual fixed IP adress (e.g. 192.168.201) , Gateway 192.168.178.1; DNS 192.168.178.9), put it with MAC-adress in the "Reserved-IP" menue and connect it via WiFi direct with the NXFilter! I have connection & internet, but cant see it in the "Lease" because it was not really getting a IP adress from NX-DHCP.
I have tried all the standard solutions without success.
Nx on Pi: 192.168.178.9
FritzBox: IP 192.168.178.1
I did some troubleshooting on cmd:
Code:
nexus6@lovepi:~ $ [B]systemctl list-units --type=service --state=running[/B]
UNIT LOAD ACTIVE SUB DESCRIPTION
accounts-daemon.service loaded active running Accounts Service
avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
bluetooth.service loaded active running Bluetooth service
cron.service loaded active running Regular background program processing daemon
cups-browsed.service loaded active running Make remote CUPS printers available locally
cups.service loaded active running CUPS Scheduler
dbus.service loaded active running D-Bus System Message Bus
getty@tty1.service loaded active running Getty on tty1
lightdm.service loaded active running Light Display Manager
ModemManager.service loaded active running Modem Manager
NetworkManager.service loaded active running Network Manager
nfs-blkmap.service loaded active running pNFS block layout mapping daemon
nxfilter.service loaded active running NxFilter
polkit.service loaded active running Authorization Manager
rpcbind.service loaded active running RPC bind portmap service
ssh.service loaded active running OpenBSD Secure Shell server
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-timesyncd.service loaded active running Network Time Synchronization
systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files
udisks2.service loaded active running Disk Manager
user@1000.service loaded active running User Manager for UID 1000
wpa_supplicant.service loaded active running WPA supplicant
Legend: LOAD → Reflects whether the unit definition was properly loaded.
ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
SUB → The low-level unit activation state, values depend on unit type.
23 loaded units listed.
nexus6@lovepi:~ $[B] ip addr show eth0[/B]
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether dc:a6:32:68:4c:d8 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.9/24 brd 192.168.178.255 scope global dynamic noprefixroute eth0
valid_lft 604740sec preferred_lft 604740sec
inet6 2003:f8:5745:6500:b546:389c:e831:ec77/64 scope global dynamic noprefixroute
valid_lft 7141sec preferred_lft 3541sec
inet6 fd54:1c4a:d9b3:0:22ca:b78b:cfaf:59de/64 scope global dynamic noprefixroute
valid_lft 7141sec preferred_lft 3541sec
inet6 fe80::74e:94ac:fcac:149e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
nexus6@lovepi:~ $ [B]nmcli con show[/B]
NAME UUID TYPE DEVICE
Wired connection 1 f139d01a-dcba-3bf9-a0d4-238b186dc34d ethernet eth0
preconfigured f0550668-e1d9-4f3f-bcaa-ac2dd6f7f69f wifi wlan0
lo 420f7042-45e1-4dd4-97d7-9148c5c6ae4f loopback lo
nexus6@lovepi:~ $ [B]sudo netstat -tulnp | grep :67[/B]
udp 0 0 192.168.178.9:67 0.0.0.0:* 698/java
nexus6@lovepi:~ $ [B]dpkg -l | grep dhcpcd[/B]
ii dhcpcd-base 1:10.1.0-11 arm64 DHCPv4 and DHCPv6 dual-stack client (binaries and exit hooks)
nexus6@lovepi:~ $ [B]sudo systemctl status NetworkManager[/B]
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)
Active: active (running) since Sat 2025-10-18 19:06:24 CEST; 17min ago
Invocation: 33a5470473b84bde905978b9172279ca
Docs: man:NetworkManager(8)
Main PID: 773 (NetworkManager)
Tasks: 4 (limit: 3913)
CPU: 3.101s
CGroup: /system.slice/NetworkManager.service
└─773 /usr/sbin/NetworkManager --no-daemon
Oct 18 19:20:27 lovepi NetworkManager[773]: <info> [1760808027.9377] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS
Oct 18 19:20:27 lovepi NetworkManager[773]: <info> [1760808027.9628] device (eth0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Oct 18 19:20:27 lovepi NetworkManager[773]: <info> [1760808027.9667] device (eth0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Oct 18 19:20:27 lovepi NetworkManager[773]: <info> [1760808027.9671] device (eth0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Oct 18 19:20:27 lovepi NetworkManager[773]: <info> [1760808027.9681] manager: NetworkManager state is now CONNECTED_SITE
Oct 18 19:20:27 lovepi NetworkManager[773]: <info> [1760808027.9686] device (eth0): Activation: successful, device activated.
Oct 18 19:20:27 lovepi NetworkManager[773]: <info> [1760808027.9697] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 18 19:20:29 lovepi NetworkManager[773]: <info> [1760808029.1765] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Oct 18 19:20:29 lovepi NetworkManager[773]: <info> [1760808029.1789] policy: set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS
Oct 18 19:20:29 lovepi NetworkManager[773]: <info> [1760808029.1910] dhcp6 (eth0): state changed new lease
Many thnaks & regards
NeX
Comment