My openmediavault NAS does not connect in any way to DNS and I cannot access the gui or use omv-firtaid to even reset interfaces or configuration

Qfnor · 24. April 2024

I changed the DNS to Google DNS (they are not 8.8.8.8.8 and 8.8.4.4.4 but routed from Jazztel DNS) and by not routing I have lost the functionality of the system here is a sample of what I'm talking about so you can help me:

Code

Global
       Protocols: +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: missing

Link 2 (wlo1)
    Current Scopes: DNS LLMNR/IPv4
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 172.253.2.194
       DNS Servers: 172.253.2.193 172.253.2.194 172.253.2.195 172.253.2.196 172.253.2.197
                    172.253.227.130 172.253.227.131 172.253.227.133 172.253.228.131 172.253.5.129
                    172.253.5.131 172.253.5.132 172.253.5.133 172.253.5.193 172.253.5.194
                    172.253.5.195 172.253.5.196 172.253.5.197
        DNS Domain: home

Link 3 (wlxb44bd626f8fd)
    Current Scopes: DNS LLMNR/IPv4
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 172.253.2.194
       DNS Servers: 172.253.2.193 172.253.2.194 172.253.2.195 172.253.2.196 172.253.2.197
                    172.253.227.130 172.253.227.131 172.253.227.133 172.253.228.131 172.253.5.129
                    172.253.5.131 172.253.5.132 172.253.5.133 172.253.5.193 172.253.5.194
                    172.253.5.195 172.253.5.196 172.253.5.197
        DNS Domain: home

Link 4 (wlx347de4402534)
    Current Scopes: DNS LLMNR/IPv4
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 172.253.227.133
       DNS Servers: 172.253.2.193 172.253.2.194 172.253.2.195 172.253.2.196 172.253.2.197
                    172.253.227.130 172.253.227.131 172.253.227.133 172.253.228.131 172.253.5.129
                    172.253.5.131 172.253.5.132 172.253.5.133 172.253.5.193 172.253.5.194
                    172.253.5.195 172.253.5.196 172.253.5.197

Alles anzeigen

I can only CLI, ssh and sftp

BlueCoffee · 24. April 2024

Zitat von Qfnor

I changed the DNS to Google DNS (they are not 8.8.8.8.8 and 8.8.4.4.4 but routed from Jazztel DNS) and by not routing I have lost the functionality of the system here is a sample of what I'm talking about so you can help me:

Code

Global
       Protocols: +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: missing

Link 2 (wlo1)
    Current Scopes: DNS LLMNR/IPv4
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 172.253.2.194
       DNS Servers: 172.253.2.193 172.253.2.194 172.253.2.195 172.253.2.196 172.253.2.197
                    172.253.227.130 172.253.227.131 172.253.227.133 172.253.228.131 172.253.5.129
                    172.253.5.131 172.253.5.132 172.253.5.133 172.253.5.193 172.253.5.194
                    172.253.5.195 172.253.5.196 172.253.5.197
        DNS Domain: home

Link 3 (wlxb44bd626f8fd)
    Current Scopes: DNS LLMNR/IPv4
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 172.253.2.194
       DNS Servers: 172.253.2.193 172.253.2.194 172.253.2.195 172.253.2.196 172.253.2.197
                    172.253.227.130 172.253.227.131 172.253.227.133 172.253.228.131 172.253.5.129
                    172.253.5.131 172.253.5.132 172.253.5.133 172.253.5.193 172.253.5.194
                    172.253.5.195 172.253.5.196 172.253.5.197
        DNS Domain: home

Link 4 (wlx347de4402534)
    Current Scopes: DNS LLMNR/IPv4
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 172.253.227.133
       DNS Servers: 172.253.2.193 172.253.2.194 172.253.2.195 172.253.2.196 172.253.2.197
                    172.253.227.130 172.253.227.131 172.253.227.133 172.253.228.131 172.253.5.129
                    172.253.5.131 172.253.5.132 172.253.5.133 172.253.5.193 172.253.5.194
                    172.253.5.195 172.253.5.196 172.253.5.197

Alles anzeigen

I can only CLI, ssh and sftp

where did you get this dns? I can't find anything on "172.253.2.194" even a dns check fails.

Soma · 24. April 2024

Zitat von BlueCoffee

where did you get this dns? I can't find anything on "172.253.2.194" even a dns check fails.

Whois IP 172.253.2.194

172.253.2.194 IP Address Details - IPinfo.io

BlueCoffee · 24. April 2024

Zitat von Soma

Whois IP 172.253.2.194

172.253.2.194 IP Address Details - IPinfo.io

I did that and it came up empty? typo maybe

Soma · 24. April 2024

Zitat von Qfnor

I can only CLI, ssh and sftp

Run omv-firstaid on CLI (if ssh, you will lose connection) and set the network only with DHCPv4.

After it's working proper, try again to set whatever you want.

[EDIT]

Your Topic makes no sense.

If you can CLI or ssh, you can run omv-firstaid

If you can't, then something else was done other than just changing the DNS of the NIC.

andrzejls · 24. April 2024

Zitat von Soma

Whois IP 172.253.2.194

172.253.2.194 IP Address Details - IPinfo.io

Google data center in L.A. (https://whatismyipaddress.com/), not DNS.

Qfnor · 24. April 2024

Zitat von Soma

Run omv-firstaid on CLI (if ssh, you will lose connection) and set the network only with DHCPv4.

After it's working proper, try again to set whatever you want.

[EDIT]
Your Topic makes no sense.
If you can CLI or ssh, you can run omv-firstaid
If you can't, then something else was done other than just changing the DNS of the NIC.

Alles anzeigen

It locks and gives me error, by the way I didn't know it was a data center and I got the ip's by doing dns leak test in this url: https://dnsleaktest.com/

Soma · 24. April 2024

Zitat von andrzejls

Google data center in L.A. (https://whatismyipaddress.com/), not DNS.

Well, OP uses it as a DNS server,

For me, the ISP DNS is more than enough on a system.

Keep DHCPv4 on the NIC, make a reserve on the router and no issues with changing IP or lack of DNS.

But that's me.

Qfnor · 24. April 2024

Zitat von Soma

Bueno, OP lo usa como servidor DNS,

Para mí, el DNS del ISP es más que suficiente en un sistema.
Mantenga DHCPv4 en la NIC, haga una reserva en el router y no tenga problemas con el cambio de IP o la falta de DNS.

Pero ese soy yo.

Alles anzeigen

Please I want to be able to use my router ip (192.168.1.1) again XDXDXDXD

Soma · 24. April 2024

Zitat von Qfnor

It locks and gives me error

Are you logged via SSH or locally?

If via SSH, post the outputs inside CODE box (symbol </> on the BLUE RIBBON of the posting box).

ip a

systemctl status systemd-networkd.service

Qfnor · 24. April 2024

I'd better show you everything

Code

Linux Qferver 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Apr 24 16:02:49 2024
root@Qferver:~# ip a
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: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e8:fb:1c:d6:eb:3f brd ff:ff:ff:ff:ff:ff
    altname wlp2s0
    inet 192.168.1.57/24 brd 192.168.1.255 scope global dynamic wlo1
       valid_lft 71096sec preferred_lft 71096sec
    inet 192.168.1.55/24 metric 600 brd 192.168.1.255 scope global secondary dynamic wlo1
       valid_lft 83982sec preferred_lft 83982sec
3: wlxb44bd626f8fd: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:4b:d6:26:f8:fd brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.125/24 metric 600 brd 192.168.1.255 scope global dynamic wlxb44bd626f8fd
       valid_lft 81976sec preferred_lft 81976sec
4: wlx347de4402534: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:7d:e4:40:25:34 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.56/24 brd 192.168.1.255 scope global wlx347de4402534
       valid_lft forever preferred_lft forever
5: wlo1.1@wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e8:fb:1c:d6:eb:3f brd ff:ff:ff:ff:ff:ff
6: br-mailcow: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:45:76:31:10 brd ff:ff:ff:ff:ff:ff
    inet 172.22.1.1/24 brd 172.22.1.255 scope global br-mailcow
       valid_lft forever preferred_lft forever
    inet6 fd4d:6169:6c63:6f77::1/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::42:45ff:fe76:3110/64 scope link
       valid_lft forever preferred_lft forever
    inet6 fe80::1/64 scope link
       valid_lft forever preferred_lft forever
7: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:a2:a8:42:f5 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:a2ff:fea8:42f5/64 scope link
       valid_lft forever preferred_lft forever
8: br-97adbbc29bbb: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:9d:c4:5b:ff brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-97adbbc29bbb
       valid_lft forever preferred_lft forever
    inet6 fe80::42:9dff:fec4:5bff/64 scope link
       valid_lft forever preferred_lft forever
10: vethabc3c01@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether c2:5c:56:1f:55:8b brd ff:ff:ff:ff:ff:ff link-netnsid 5
    inet6 fe80::c05c:56ff:fe1f:558b/64 scope link
       valid_lft forever preferred_lft forever
12: vethe93d42e@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether 2a:9f:47:98:c5:98 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::289f:47ff:fe98:c598/64 scope link
       valid_lft forever preferred_lft forever
14: veth468f04b@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-97adbbc29bbb state UP group default
    link/ether 8e:98:e0:28:83:91 brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet6 fe80::8c98:e0ff:fe28:8391/64 scope link
       valid_lft forever preferred_lft forever
16: veth80a93b4@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether 82:02:cb:96:90:1f brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::8002:cbff:fe96:901f/64 scope link
       valid_lft forever preferred_lft forever
18: vethd373437@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether 66:6d:d1:d3:f4:81 brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet6 fe80::646d:d1ff:fed3:f481/64 scope link
       valid_lft forever preferred_lft forever
20: veth4bb650d@if19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-97adbbc29bbb state UP group default
    link/ether fe:08:82:16:b1:5f brd ff:ff:ff:ff:ff:ff link-netnsid 11
    inet6 fe80::fc08:82ff:fe16:b15f/64 scope link
       valid_lft forever preferred_lft forever
22: veth441e76b@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether ba:85:8f:a4:02:a9 brd ff:ff:ff:ff:ff:ff link-netnsid 7
    inet6 fe80::b885:8fff:fea4:2a9/64 scope link
       valid_lft forever preferred_lft forever
24: veth40180d5@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether 9e:41:ec:87:eb:ae brd ff:ff:ff:ff:ff:ff link-netnsid 8
    inet6 fe80::9c41:ecff:fe87:ebae/64 scope link
       valid_lft forever preferred_lft forever
26: vethbb015d5@if25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether 5a:66:44:44:30:5e brd ff:ff:ff:ff:ff:ff link-netnsid 4
    inet6 fe80::5866:44ff:fe44:305e/64 scope link
       valid_lft forever preferred_lft forever
28: veth0caa722@if27: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether 96:08:25:1a:d5:1c brd ff:ff:ff:ff:ff:ff link-netnsid 6
    inet6 fe80::9408:25ff:fe1a:d51c/64 scope link
       valid_lft forever preferred_lft forever
30: veth89e627e@if29: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether 1e:44:2e:ce:71:95 brd ff:ff:ff:ff:ff:ff link-netnsid 10
    inet6 fe80::1c44:2eff:fece:7195/64 scope link
       valid_lft forever preferred_lft forever
32: veth6d7c34b@if31: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether d2:26:a4:79:9b:95 brd ff:ff:ff:ff:ff:ff link-netnsid 9
    inet6 fe80::d026:a4ff:fe79:9b95/64 scope link
       valid_lft forever preferred_lft forever
34: veth83c7496@if33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether d6:2a:6a:20:81:63 brd ff:ff:ff:ff:ff:ff link-netnsid 21
    inet6 fe80::d42a:6aff:fe20:8163/64 scope link
       valid_lft forever preferred_lft forever
36: veth2be3d90@if35: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether e2:66:61:8f:15:b2 brd ff:ff:ff:ff:ff:ff link-netnsid 16
    inet6 fe80::e066:61ff:fe8f:15b2/64 scope link
       valid_lft forever preferred_lft forever
38: veth953e421@if37: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether 26:a1:99:0a:b1:6d brd ff:ff:ff:ff:ff:ff link-netnsid 13
    inet6 fe80::24a1:99ff:fe0a:b16d/64 scope link
       valid_lft forever preferred_lft forever
40: veth135d0be@if39: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether c2:db:eb:14:3a:e9 brd ff:ff:ff:ff:ff:ff link-netnsid 12
    inet6 fe80::c0db:ebff:fe14:3ae9/64 scope link
       valid_lft forever preferred_lft forever
42: veth99e96d8@if41: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether a2:4c:24:12:4c:da brd ff:ff:ff:ff:ff:ff link-netnsid 20
    inet6 fe80::a04c:24ff:fe12:4cda/64 scope link
       valid_lft forever preferred_lft forever
44: vethe4cac1f@if43: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether ba:9b:bd:4c:ac:a8 brd ff:ff:ff:ff:ff:ff link-netnsid 15
    inet6 fe80::b89b:bdff:fe4c:aca8/64 scope link
       valid_lft forever preferred_lft forever
46: veth49fef9b@if45: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether da:2b:c3:d0:3b:b6 brd ff:ff:ff:ff:ff:ff link-netnsid 14
    inet6 fe80::d82b:c3ff:fed0:3bb6/64 scope link
       valid_lft forever preferred_lft forever
48: veth70604d0@if47: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether 9a:4e:50:bc:6b:b1 brd ff:ff:ff:ff:ff:ff link-netnsid 18
    inet6 fe80::984e:50ff:febc:6bb1/64 scope link
       valid_lft forever preferred_lft forever
50: veth955d727@if49: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether 72:0a:9a:35:3a:98 brd ff:ff:ff:ff:ff:ff link-netnsid 19
    inet6 fe80::700a:9aff:fe35:3a98/64 scope link
       valid_lft forever preferred_lft forever
52: veth72deca8@if51: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-mailcow state UP group default
    link/ether ce:dc:16:91:24:c6 brd ff:ff:ff:ff:ff:ff link-netnsid 17
    inet6 fe80::ccdc:16ff:fe91:24c6/64 scope link
       valid_lft forever preferred_lft forever

Alles anzeigen

Qfnor · 24. April 2024

Zitat von Soma

Are you logged via SSH or locally?
If via SSH, post the outputs inside CODE box (symbol </> on the BLUE RIBBON of the posting box).

ip a
systemctl status systemd-networkd.service

By the way, your profile picture reminds me of a Spanish YouTuber ¿La red de mario?, I know it has nothing to do with it but I don't want to remain in doubt

Soma · 24. April 2024

Zitat von Qfnor

192.168.1.57

You are using wireless.

Have you tried to access you OMV with the IP?

http://192.168.1.57

Qfnor · 24. April 2024

No routing, it is internal to the server to optimize the network, I route absolutely on 192.168.1.56 on "192.168.1.56" I access server on others directly on network to the powerful

andrzejls · 24. April 2024

Zitat von Qfnor

Please I want to be able to use my router ip (192.168.1.1) again XDXDXDXDTest

Test this DNS servers (very secure and encrypted) 9.9.9.9, 149.112.112.112

Soma · 24. April 2024

Zitat von Qfnor

No routing, it is internal to the server to optimize the network

I have no idea what you are talking about.

You have 3x wireless connections with different IPs assigned, and wlo1 even has 2 different IPs.

Code

2: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e8:fb:1c:d6:eb:3f brd ff:ff:ff:ff:ff:ff
    altname wlp2s0
    inet 192.168.1.57/24 brd 192.168.1.255 scope global dynamic wlo1
       valid_lft 71096sec preferred_lft 71096sec
    inet 192.168.1.55/24 metric 600 brd 192.168.1.255 scope global secondary dynamic wlo1
       valid_lft 83982sec preferred_lft 83982sec
3: wlxb44bd626f8fd: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:4b:d6:26:f8:fd brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.125/24 metric 600 brd 192.168.1.255 scope global dynamic wlxb44bd626f8fd
       valid_lft 81976sec preferred_lft 81976sec
4: wlx347de4402534: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:7d:e4:40:25:34 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.56/24 brd 192.168.1.255 scope global wlx347de4402534
       valid_lft forever preferred_lft forever

Alles anzeigen

Since I can't have a clue of what you did or were trying to achieve, all I can say is, try all those IPs on the browser to see if you can reach OMV.

Other than that, I have no more ideas on what you can do.

If you try to change anything via omv-firstaid, you need to select the proper NIC and edit its values.

And I never used Wireless, I don't even know how to set it on CLI.

Good Luck

Qfnor · 24. April 2024

Zitat von andrzejls

Test this DNS servers (very secure and encrypted) 9.9.9.9, 149.112.112.112

The problem is that I get an error when I touch the interfaces (in the OMV gui itself (in command because I can't access the web page)) and I can't change the DNS

Qfnor · 24. April 2024

Zitat von Soma
I have no idea what you are talking about.

You have 3x wireless connections with different IPs assigned, and wlo1 even has 2 different IPs.
Code
2: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e8:fb:1c:d6:eb:3f brd ff:ff:ff:ff:ff:ff
    altname wlp2s0
    inet 192.168.1.57/24 brd 192.168.1.255 scope global dynamic wlo1
       valid_lft 71096sec preferred_lft 71096sec
    inet 192.168.1.55/24 metric 600 brd 192.168.1.255 scope global secondary dynamic wlo1
       valid_lft 83982sec preferred_lft 83982sec
3: wlxb44bd626f8fd: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:4b:d6:26:f8:fd brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.125/24 metric 600 brd 192.168.1.255 scope global dynamic wlxb44bd626f8fd
       valid_lft 81976sec preferred_lft 81976sec
4: wlx347de4402534: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:7d:e4:40:25:34 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.56/24 brd 192.168.1.255 scope global wlx347de4402534
       valid_lft forever preferred_lft forever
Alles anzeigen
Since I can't have a clue of what you did or were trying to achieve, all I can say is, try all those IPs on the browser to see if you can reach OMV.
Other than that, I have no more ideas on what you can do.

If you try to change anything via omv-firstaid, you need to select the proper NIC and edit its values.
And I never used Wireless, I don't even know how to set it on CLI.

Good Luck
Alles anzeigen

Sorry in all urls I can access the web gui thought that because it was virtual it was not accessed and was internal, but web GUI not works

Soma · 24. April 2024

Zitat von Soma

192.168.1.55
192.168.1.56
192.168.1.57
192.168.1.125

These are the IPs that are showing via ip a

Try each one and see if you can access the GUI.

andrzejls · 24. April 2024

Zitat von Qfnor

The problem is that I get an error when I touch the interfaces (in the OMV gui itself (in command because I can't access the web page)) and I can't change the DNS

As Soma suggested, can you access OMV GUI using http://192.168.1.57 IP?.

My openmediavault NAS does not connect in any way to DNS and I cannot access the gui or use omv-firtaid to even reset interfaces or configuration

ryecoaaron 24. April 2024

Jetzt mitmachen!