Can't connect network with static IP

HI,

I’m using dietpi on an Intel Nuc.

I was using it via DHCP for my IP, I used No-Ip for dyndns and it’s work fine.

But when I try to change to static IP via detpi-config, my nuc can’t access outside network.
So I can’t configure dyndns, can’t use my nextcloud, etc …

On my router, I have activate the dmz to be sure that is not port forwarding problem, but nothing happens.

I want / have to be on static IP because I have to change the dns for my dietpi nuc (torrent download are blocked by my provider).

Someone have an idea ?

Plz deactivate the DMZ, it’s not necessary and can be quite dangerous if you don’t know what you are doing.

Make sure the IP is in the correct range, what are the DHCP and subnet settings in the router?

And can you show the ouput of ip a when you switched to static IP?

Best to show ip a for both STATIC and DHCP

HI,
Thanks to try to help me.

  1. Here’s command IP A with DHCP :
root@DietPi:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul                                                                                                         t qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP grou                                                                                                         p default qlen 1000
    link/ether f4:4d:30:63:24:26 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.58/24 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 75685sec preferred_lft 75685sec
    inet6 2a02:8429:807d:c301:f64d:30ff:fe63:2426/64 scope global dynamic mngtmp                                                                                                         addr
       valid_lft 604608sec preferred_lft 604608sec
    inet6 fe80::f64d:30ff:fe63:2426/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qle                                                                                                         n 1000
    link/ether 00:c2:c6:eb:ea:2e brd ff:ff:ff:ff:ff:ff
  1. Here’s IP A command withe static
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f4:4d:30:63:24:26 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.58/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2a02:8429:807d:c301:f64d:30ff:fe63:2426/64 scope global dynamic mngtmpaddr
       valid_lft 604794sec preferred_lft 604794sec
    inet6 fe80::f64d:30ff:fe63:2426/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:c2:c6:eb:ea:2e brd ff:ff:ff:ff:ff:ff
  1. Here’s a screen capture of subnet settings :

  2. When I try to use No-IP :
    Before applying settings :

[ INFO ] DietPi-DDNS | Preparing unprivileged DietPi-DDNS UNIX group ...
[  OK  ] DietPi-DDNS | groupmod -p ! dietpi-ddns
[ INFO ] DietPi-DDNS | Preparing unprivileged DietPi-DDNS UNIX user ...
[  OK  ] DietPi-DDNS | usermod -g dietpi-ddns -G  -d /nonexistent -s /usr/sbin/nologin -p ! dietpi-ddns
[ INFO ] DietPi-DDNS | Testing DDNS update ...
[FAILED] DietPi-DDNS | DDNS update test failed, please check your input: curl: (7) Failed to connect to dynupdate.noip.com port 443 after 2090 ms: Couldn't connect to server

And the result :

Here’s Static IP config in dietpi-config :

Thanks for your help.

On STATIC, the gateway doesn’t seems to be correct. It’s 192.168.0.1 but I guess it would need to be 192.168.1.1

Hi,
Yes it’s works.
Thank you very much.
You have good eyes, I didn’t saw it.
Thank you again.