LAN by router via router. Two subnets. Can't ping a domain name. DNS.

tupadown228 · 2022-10-25 21:38:17

The router A is connected via WAN port to local ISP. From LAN port on the router A Ethernet cable goes to WAN port on the router B. DHCP server on the router B is configured automatic and I change ip address to 192.168.0.2. That's all. There is an internet on Windows and android devices, which are connected to the router B, but on the arch not(
i can connect to the router B interface panel on 192.168.0.2 and telegram client is work, lol, but i can't connect, for instance, to google.com.
).
If arch is connected to the router A, then all is fine. For example, I can ping http://google.com (UPD addition: but when arch is connected to the router B, i can't ping (sick!)).

I know there is something wrong with the dhcp server on arch. I hope.
UPD: There is the problem with the resolving domain names.

Help, please, i dunno what to do... sir please do helping...

There is NetworkManager journal logs after enabling.

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Tue 2022-09-13 1:07:43 ; 1 month 10 days ago
       Docs: man:NetworkManager(8)
   Main PID: 735 (NetworkManager)
      Tasks: 11 (limit: 19018)
     Memory: 13.5M
        CPU: 28min 54.822s
     CGroup: /system.slice/NetworkManager.service
             └─735 /usr/bin/NetworkManager --no-daemon

Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5120] manager: rfkill: Wi-Fi hardware radio set enabled
Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5286] audit: op="radio-control" arg="wireless-enabled:on" pid=2564197 uid=1000 result="success"
Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5291] manager: rfkill: Wi-Fi now enabled by radio killswitch
Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5536] device (wlp2s0): supplicant interface state: internal-starting -> disconnected
Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5536] device (p2p-dev-wlp2s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5548] Wi-Fi P2P device controlled by interface wlp2s0 created
Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5555] manager: (p2p-dev-wlp2s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/22)
Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5562] device (p2p-dev-wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5574] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Oct 24 21:18:04 mach1ne NetworkManager[735]: <info>  [1666635484.5587] device (p2p-dev-wlp2s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7147] policy: auto-activating connection 'dir-dir-825' (336ec7)
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7156] device (wlp2s0): Activation: starting connection 'dir-dir-825' (336336ec7)
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7159] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7163] manager: NetworkManager state is now CONNECTING
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7253] device (wlp2s0): set-hw-addr: reset MAC address to 336E (preserve)
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7399] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7402] device (wlp2s0): Activation: (wifi) access point 'dir-dir-825' has security, but secrets are required.
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7403] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7406] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7407] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> interface_disabled
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7417] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7419] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7422] device (wlp2s0): Activation: (wifi) connection 'dir-dir-825' has security, and secrets exist.  No new secrets needed.
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7422] Config: added 'ssid' value 'dir-dir-825'
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7422] Config: added 'scan_ssid' value '1'
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7422] Config: added 'bgscan' value 'simple:30:-70:86400'
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7423] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7423] Config: added 'psk' value '<hidden>'
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7572] device (wlp2s0): supplicant interface state: interface_disabled -> inactive
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7573] device (p2p-dev-wlp2s0): supplicant management interface state: interface_disabled -> inactive
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7776] device (wlp2s0): supplicant interface state: inactive -> authenticating
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7776] device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> authenticating
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7804] device (wlp2s0): supplicant interface state: authenticating -> associating
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.7805] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.8297] device (wlp2s0): supplicant interface state: associating -> associated
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.8298] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> associated
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.8420] device (wlp2s0): supplicant interface state: associated -> 4way_handshake
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.8421] device (p2p-dev-wlp2s0): supplicant management interface state: associated -> 4way_handshake
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.8986] device (wlp2s0): supplicant interface state: 4way_handshake -> completed
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.8988] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "dir-dir-825"
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.8988] device (p2p-dev-wlp2s0): supplicant management interface state: 4way_handshake -> completed
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.8990] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.9004] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.9118] dhcp4 (wlp2s0): state changed new lease, address=192.168.0.133
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.9136] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.9240] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.9242] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.9252] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.9260] manager: NetworkManager state is now CONNECTED_SITE
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.9261] policy: set 'dir-dir-825' (wlp2s0) as default for IPv4 routing and DNS
Oct 24 21:18:05 mach1ne NetworkManager[735]: <info>  [1666635485.9300] device (wlp2s0): Activation: successful, device activated.

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 
       valid_lft forever preferred_lft forever
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 3367 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 336e brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.133/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 70262sec preferred_lft 70262sec
    inet6 fe80:::::4a08/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

UPD:

ip a output:
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 
       valid_lft forever preferred_lft forever
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 3367 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 336336e brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.133/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 66040sec preferred_lft 66040sec
    inet6 fe80:::::4a08/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

ip r output:
default via 192.168.0.2 dev wlp2s0 proto dhcp src 192.168.0.133 metric 20600 
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.133 metric 600 

ping output:
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=107 time=30.6 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 30.573/30.573/30.573/0.000 ms

tracepath -b google.com
tracepath: google.com: Temporary failure in name resolution

tracepath -b 8.8.8.8
 1?: [LOCALHOST]                      pmtu 1500
 1:  _gateway (192.168.0.2)                                1.800ms 
 1:  _gateway (192.168.0.2)                                0.945ms

Last edited by tupadown228 (2022-10-28 16:17:42)

seth · 2022-10-26 07:12:48

2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 74:86:7a:57:74:47 brd ff:ff:ff:ff:ff:ff

There's no carrier what means there's no physical connection between the two hosts.
If you're sure that the cable is fine, it's the plugs and from your explanation it's either loose in the slot of "router B" or you're using a slot that isn't part of the routers switch, but eg. to connect it to a modem (it will often have a different color)

tupadown228 · 2022-10-26 09:01:26

seth wrote:

2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
There's no carrier what means there's no physical connection between the two hosts.
If you're sure that the cable is fine, it's the plugs and from your explanation it's either loose in the slot of "router B" or you're using a slot that isn't part of the routers switch, but eg. to connect it to a modem (it will often have a different color)

I use Wi-Fi. And what does it matter when the cable is plugged in the arch laptop, there is no internet too. I mean, there is no difference between wi-fi or ethernet cable.
The problem is in DHCP server on arch, but i don't know exactly what it is...

Last edited by tupadown228 (2022-10-27 23:21:28)

seth · 2022-10-26 09:30:56

Your OP specifically talks about a wired connection and you do have a lease on the WiFi connection.

Is the "ip a" output actually from a moment when you supposingly don't have a connection?
Please post a complete system journal (sudo journalctl -b) and the outputs of "ip a; ip r" and "ping -c1 8.8.8.8" from a moment when you have issues w/ the system.

tupadown228 · 2022-10-26 10:04:29

seth wrote:

Your OP specifically talks about a wired connection and you do have a lease on the WiFi connection.
Is the "ip a" output actually from a moment when you supposingly don't have a connection?
Please post a complete system journal (sudo journalctl -b) and the outputs of "ip a; ip r" and "ping -c1 8.8.8.8" from a moment when you have issues w/ the system.

Yup, I can't ping domains...

ip a output:
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 
       valid_lft forever preferred_lft forever
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ethere brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.133/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 66040sec preferred_lft 66040sec
    inet6 scope link noprefixroute 
       valid_lft forever preferred_lft forever

ip r output:
default via 192.168.0.2 dev wlp2s0 proto dhcp src 192.168.0.133 metric 20600 
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.133 metric 600 

ping output:
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=107 time=30.6 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 30.573/30.573/30.573/0.000 ms

tracepath -b google.com
tracepath: google.com: Temporary failure in name resolution

tracepath -b 8.8.8.8
 1?: [LOCALHOST]                      pmtu 1500
 1:  _gateway (192.168.0.2)                                1.800ms 
 1:  _gateway (192.168.0.2)                                0.945ms

Last edited by tupadown228 (2022-10-27 23:21:06)

seth · 2022-10-26 12:23:39

So this is only a DNS issue

resolvectl status
nslookup google.com
dig google.com
dig @8.8.8.8 google.com
# alternatively
drill google.com
drill @8.8.8.8 google.com

tupadown228 · 2022-10-26 13:21:09

seth wrote:

So this is only a DNS issue

resolvectl status
nslookup google.com
dig google.com
dig @8.8.8.8 google.com
# alternatively
drill google.com
drill @8.8.8.8 google.com

resolvectl  status
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

drill google.com
Error: error sending query: Could not send or receive, because of network error

drill @8.8.8.8 google.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 22270
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; google.com.INA

;; ANSWER SECTION:
google.com. 300 IN A 26.8.20.13

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 31 msec
;; SERVER: 8.8.8.8
;; WHEN: Wed Oct 26 :52 2022
;; MSG SIZE  rcvd: 44

i'm reading this and this right now...

Is it a good idea if i want to dive in and to understand all of these internet things via "See also" links in two wiki links above? Or should i read something else?.. Т_Т

seth · 2022-10-26 13:23:37

stat /etc/resolv.conf
cat /etc/resolv.conf

How do you configure your network?

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

tupadown228 · 2022-10-26 13:43:33

seth wrote:

stat /etc/resolv.conf
cat /etc/resolv.conf

How do you configure your network?

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

I don't know how... I don't do anything on arch, i guess.

  File: /etc/resolv.conf
  Size: 97        	Blocks: 8          IO Block: 4096   regular file
Device: 254,2	Inode: 1443415     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2022-10-26 0:32:42.627331830 
Modify: 2022-10-24 1:18:07.291993218 
Change: 2022-10-24 1:18:07.291993218 
 Birth: 2022-10-24 1:18:07.291993218 

# Generated by NetworkManager
nameserver 192.168.0.2
nameserver af80::a02e:ae50:9aaf:ed3f%wlp2s0

NetworkManager-wait-online.service       
| network-online.target.wants/ndisplay-manager.service                  
| system/nsystemd-resolved.service                 
| sysinit.target.wants/ndbus-org.freedesktop.nm-dispatcher.service 
| system/ndbus-org.freedesktop.resolve1.service    
| system/ngetty@tty1.service                       
| getty.target.wants/nNetworkManager.service                  
 | multi-user.target.wants/npostgresql.service                       
| multi-user.target.wants/nnftables.service                         
| multi-user.target.wants/nsshd.service                             
| multi-user.target.wants/nremote-fs.target                         
| multi-user.target.wants/npipewire-session-manager.service         
| user/ngnome-keyring-daemon.socket              
| sockets.target.wants/ngpg-agent.socket                         
| sockets.target.wants/ngpg-agent-browser.socket                 
| sockets.target.wants/ngpg-agent-extra.socket                   
| sockets.target.wants/ngcr-ssh-agent.socket                     
| sockets.target.wants/npipewire.socket                          
| sockets.target.wants/ndirmngr.socket                           
| sockets.target.wants/ngpg-agent-ssh.socket                     
| sockets.target.wants/np11-kit-server.socket                    
| sockets.target.wants/npulseaudio.socket                        
| sockets.target.wants/nxdg-user-dirs-update.service             
| default.target.wants/npipewire-media-session.service           
| pipewire.service.wants/n

Last edited by tupadown228 (2022-10-26 21:07:10)

seth · 2022-10-26 13:58:42

resolved seems to be enabled but not running/responding
DNS is configured by NM and set to 192.168.0.2

nmap -p53 192.168.0.2
drill @192.168.0.2 google.com

You completely trashed the formatting of the find command, but it doesn't look like there's a conflicting network configuring service.

I don't know how... I don't do anything on arch, i guess.

How did you install archlinux? What instructions/tutorial did you follow?

tupadown228 · 2022-10-26 15:09:38

seth wrote:

How did you install archlinux? What instructions/tutorial did you follow?

I followed official guide.

Starting Nmap 7.92 ( https://nmap.org ) at 2022-10-26 
Nmap scan report for router.local (192.168.0.2)
Host is up (0.0025s latency).

PORT   STATE SERVICE
53/tcp open  domain

Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds

drill @192.168.0.2 google.com >> dnsProblem 
Error: error sending query: Could not send or receive, because of network error

seth wrote:

DNS is configured by NM and set to 192.168.0.2

Should i do something on router B? Like set DNS server address?

UPD:

seth wrote:

resolved seems to be enabled but not running/responding
DNS is configured by NM and set to 192.168.0.2

I forgot to say. If I use router A, then DNS on arch works fine.

Last edited by tupadown228 (2022-10-26 21:05:27)

seth · 2022-10-26 15:33:56

There's probably an issue w/ the DNS server on 192.168.0.2 - you have a lease, a route, nmap figures that the DNS port is open, but drill doesn't get an answer.
Configure https://wiki.archlinux.org/title/Networ … NS_servers and use one of https://wiki.archlinux.org/title/Altern … S_services (in doubt 8.8.8.8 or 1.1.1.1)

tupadown228 · 2022-10-26 20:40:24

seth wrote:

There's probably an issue w/ the DNS server on 192.168.0.2 - you have a lease, a route, nmap figures that the DNS port is open, but drill doesn't get an answer.
Configure https://wiki.archlinux.org/title/Networ … NS_servers and use one of https://wiki.archlinux.org/title/Altern … S_services (in doubt 8.8.8.8 or 1.1.1.1)

I set a lot of custom DNS addresses but nothing change. I was desperate. I removed all changes.
And then I just plugged in and pulled out a ethernet cable from the router A, because i thought the problem was in DNS settings on the router B, then I connected to the router B via wi-fi and problem is gone... I don't know what happened and how long it will continue, but for now issue is solved... Thank you so much for your help and time!!!

P.S. I want to know what the hell it was. I was doing the same thing earlier and not once, but to no avail. What should i do? Check journal logs?

UPD: I don't see nothing in NM logs...

Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.4683] device (enp1s0): carrier: link connected
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.4687] device (enp1s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.4695] policy: auto-activating connection 'Wired connection 1' (77116d11af5)
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.4701] device (enp1s0): Activation: starting connection 'Wired connection 1' (77116d11af5)
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.4702] device (enp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.4705] manager: NetworkManager state is now CONNECTING
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.4706] device (enp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.4710] device (enp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.4722] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.6647] dhcp4 (enp1s0): state changed new lease, address=192.168.0.55
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.6666] device (enp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.6782] device (enp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.6784] device (enp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.6788] manager: NetworkManager state is now CONNECTED_SITE
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.6793] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.6794] manager: NetworkManager state is now CONNECTED_SITE
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.6795] policy: set 'Wired connection 1' (enp1s0) as default for IPv4 routing and DNS
Oct 26 1:12:49 mach1ne NetworkManager[735]: <info>  [1666815169.6853] device (enp1s0): Activation: successful, device activated.
Oct 26 1:12:52 mach1ne NetworkManager[735]: <info>  [1666815172.8620] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 26 1:12:59 mach1ne NetworkManager[735]: <info>  [1666815179.9892] manager: rfkill: Wi-Fi hardware radio set disabled
Oct 26 1:12:59 mach1ne NetworkManager[735]: <info>  [1666815179.9892] device (wlp2s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed')
Oct 26 1:12:59 mach1ne NetworkManager[735]: <info>  [1666815179.9894] dhcp4 (wlp2s0): canceled DHCP transaction
Oct 26 1:12:59 mach1ne NetworkManager[735]: <info>  [1666815179.9894] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Oct 26 1:12:59 mach1ne NetworkManager[735]: <info>  [1666815179.9895] dhcp4 (wlp2s0): state changed no lease
Oct 26 1:13:00 mach1ne NetworkManager[735]: <info>  [1666815180.0020] device (wlp2s0): set-hw-addr: set MAC address to D6 (scanning)
Oct 26 1:13:00 mach1ne NetworkManager[735]: <info>  [1666815180.0141] audit: op=\"radio-control\" arg=\"wireless-enabled:off\" pid=2564197 uid=1000 result=\"success\"
Oct 26 1:13:00 mach1ne NetworkManager[735]: <info>  [1666815180.0146] manager: rfkill: Wi-Fi now disabled by radio killswitch
Oct 26 1:13:00 mach1ne NetworkManager[735]: <info>  [1666815180.0159] device (p2p-dev-wlp2s0): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.1710] manager: rfkill: Wi-Fi hardware radio set enabled
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.1876] audit: op=\"radio-control\" arg=\"wireless-enabled:on\" pid=2564197 uid=1000 result=\"success\"
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.1893] manager: rfkill: Wi-Fi now enabled by radio killswitch
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.2164] device (wlp2s0): supplicant interface state: internal-starting -> disconnected
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.2164] device (p2p-dev-wlp2s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.2220] Wi-Fi P2P device controlled by interface wlp2s0 created
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.2267] manager: (p2p-dev-wlp2s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/23)
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.2280] device (p2p-dev-wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.2285] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Oct 26 1:13:18 mach1ne NetworkManager[735]: <info>  [1666815198.2294] device (p2p-dev-wlp2s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4220] policy: auto-activating connection 'cute-wi-fi-name' (2044ec7)
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4230] device (wlp2s0): Activation: starting connection 'cute-wi-fi-name' (2044ec7)
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4234] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4340] device (wlp2s0): set-hw-addr: reset MAC address to F6 (preserve)
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4479] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4486] device (wlp2s0): Activation: (wifi) access point 'cute-wi-fi-name' has security, but secrets are required.
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4488] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4496] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4498] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> interface_disabled
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4512] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4521] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4527] device (wlp2s0): Activation: (wifi) connection 'cute-wi-fi-name' has security, and secrets exist.  No new secrets needed.
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4529] Config: added 'ssid' value 'cute-wi-fi-name'
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4530] Config: added 'scan_ssid' value '1'
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4531] Config: added 'bgscan' value 'simple:30:-7:0'
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4532] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4534] Config: added 'psk' value '<hidden>'
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4791] device (wlp2s0): supplicant interface state: interface_disabled -> inactive
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4792] device (p2p-dev-wlp2s0): supplicant management interface state: interface_disabled -> inactive
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4996] device (wlp2s0): supplicant interface state: inactive -> authenticating
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.4997] device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> authenticating
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.5021] device (wlp2s0): supplicant interface state: authenticating -> associating
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.5022] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.5455] device (wlp2s0): supplicant interface state: associating -> associated
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.5455] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> associated
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.5603] device (wlp2s0): supplicant interface state: associated -> 4way_handshake
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.5604] device (p2p-dev-wlp2s0): supplicant management interface state: associated -> 4way_handshake
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6503] device (wlp2s0): supplicant interface state: 4way_handshake -> completed
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6504] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network \"cute-wi-fi-name\"
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6504] device (p2p-dev-wlp2s0): supplicant management interface state: 4way_handshake -> completed
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6505] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6512] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6625] dhcp4 (wlp2s0): state changed new lease, address=192.168.0.133
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6645] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6754] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6756] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 26 1:13:19 mach1ne NetworkManager[735]: <info>  [1666815199.6807] device (wlp2s0): Activation: successful, device activated.
Oct 26 1:13:22 mach1ne NetworkManager[735]: <info>  [1666815202.2470] device (enp1s0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 26 1:13:22 mach1ne NetworkManager[735]: <info>  [1666815202.2584] dhcp4 (enp1s0): canceled DHCP transaction
Oct 26 1:13:22 mach1ne NetworkManager[735]: <info>  [1666815202.2585] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Oct 26 1:13:22 mach1ne NetworkManager[735]: <info>  [1666815202.2585] dhcp4 (enp1s0): state changed no lease
Oct 26 1:13:22 mach1ne NetworkManager[735]: <info>  [1666815202.2642] policy: set 'cute-wi-fi-name' (wlp2s0) as default for IPv4 routing and DNS
Oct 26 1:13:22 mach1ne NetworkManager[735]: <info>  [1666815202.2653] manager: NetworkManager state is now CONNECTED_SITE
Oct 26 1:13:22 mach1ne NetworkManager[735]: <info>  [1666815202.8665] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 26 1:14:14 mach1ne NetworkManager[735]: <info>  [1666815254.1295] audit: op=\"connection-update\" uuid=\"2044ec7\" name=\"cute-wi-fi-name\" args=\"ipv4.dns,connection.timestamp,ipv6.dns\" pid=2985933 uid=1000 result=\"success\"

Last edited by tupadown228 (2022-10-26 21:05:00)

seth · 2022-10-26 21:06:33

hen I just plugged in and pulled out a ethernet cable from the router A, because i thought the problem was in DNS settings on the router B, then I connected to the router B via wi-fi

Hold on, are you actually connecting the system to two different gateways, possibly in the same subnet??
What exactly are "router A" and "router B", what's their relation (are they somehow connected) and just to be absolutely clear: the archlinux system is neither "router A" nor "router B"?

tupadown228 · 2022-10-26 21:56:47

seth wrote:

hen I just plugged in and pulled out a ethernet cable from the router A, because i thought the problem was in DNS settings on the router B, then I connected to the router B via wi-fi
Hold on, are you actually connecting the system to two different gateways, possibly in the same subnet??
What exactly are "router A" and "router B", what's their relation (are they somehow connected) and just to be absolutely clear: the archlinux system is neither "router A" nor "router B"?

Yes, arch is not router/switch/etc, which is connected only to the router B via wi-fi right now. I use arch as an developing toy and code sometimes on JS, lol, sorry.

The router A is connected via WAN port to the internet. From LAN port on the router A Ethernet cable goes to WAN port on the router B. DHCP server on the router B is configured automatic and I change ip address to 192.168.0.2. That's all what i know. Sorry for bad eng.

And... Can you, please, recommend some titles/links/materials about "How Network works/How to interact with it" to read for newbies, like me? Please... I started reading "Computer Networking: A Top-Down Approach" by Kurose & Ross, but it has few practical assignments and it is quite huge...

And thank you so much again <3

Last edited by tupadown228 (2022-10-26 22:12:14)

seth · 2022-10-27 08:58:22

DHCP server on the router B is configured automatic

Do you have 2 dhcp servers on the subnet?

sudo nmap --script broadcast-dhcp-discover # you *have* to run this as root

tupadown228 · 2022-10-27 09:24:28

seth wrote:

sudo nmap --script broadcast-dhcp-discover # you *have* to run this as root

Starting Nmap 7.92 ( https://nmap.org ) at 2022-10-27 
Pre-scan script results:
| broadcast-dhcp-discover: 
|   Response 1 of 1: 
|     Interface: wlp2s0
|     IP Offered: 192.168.0.149
|     DHCP Message Type: DHCPOFFER
|     Server Identifier: 192.168.0.2
|     IP Address Lease Time: 1d00h00m00s
|     Renewal Time Value: 12h00m00s
|     Rebinding Time Value: 21h00m00s
|     Subnet Mask: 255.255.255.0
|     Broadcast Address: 192.168.0.255
|     Router: 192.168.0.2
|_    Domain Name Server: 192.168.0.2
Nmap done: 0 IP addresses (0 hosts up) scanned in 10.35 seconds

Do you have 2 dhcp servers on the subnet?

Sorry. I don't really understand what do you mean. I configure DHCP server only on the router B. I didn't do anything with DHCP on arch. And if i did any changes, i deleted them, because they didn't work...

Last edited by tupadown228 (2022-10-27 09:35:58)

seth · 2022-10-27 12:24:10

I configure DHCP server only on the router B.

A rogue dhcp server causes all sorts of trouble and since you stated that

If arch is connected to the router A, then all is fine. For example, I can ping http://google.com (UPD addition: but when arch is connected to the router B, i can't ping (sick!)).

I suspected you might have a dhcp server on "router A" as well (but there isn't, nmap only found the one on "router B")
I assume "router A" is a router/modem from your ISP and "router B" is a private switch/router bind that?

To give us a record of the working status quo:

ip a
ip r
resolvectl status
cat /etc/resolv.conf # since the original problem seemed to have been the DNS on "router B"

twelveeighty · 2022-10-27 15:09:44

tupadown228 wrote:

I sticked a first end of cable in the main router A and sticked a second end in the router B.

I'm pretty sure you can't do that, unless you configured router B to act as a bridge/switch, which includes (as Seth mentioned) disabling DNS, DHCP, etc.

Why are you connecting two routers? What are you trying to accomplish?

tupadown228 · 2022-10-27 23:03:57

twelveeighty wrote:

tupadown228 wrote:
I sticked a first end of cable in the main router A and sticked a second end in the router B.
I'm pretty sure you can't do that, unless you configured router B to act as a bridge/switch, which includes (as Seth mentioned) disabling DNS, DHCP, etc.

The router A is connected via WAN port to local ISP. From LAN port on the router A Ethernet cable goes to WAN port on the router B. DHCP server on the router B is configured automatic and I change ip address to 192.168.0.2. What or how was I supposed to do?

twelveeighty wrote:

Why are you connecting two routers? What are you trying to accomplish?

I have fat walls in my apartment. The wi-fi coverage area is not enough for me. That's why i added second "router B". But I don't want to repeat wi-fi network from the router A, I want two "independent" wi-fi networks.

And i call them router A, B, because i think it's easier to remember than dir-123, asus-ABC, keenetic-XYZ and etc.

Last edited by tupadown228 (2022-10-27 23:08:58)

tupadown228 · 2022-10-27 23:25:33

seth wrote:

I assume "router A" is a router/modem from your ISP and "router B" is a private switch/router bind that?

It is not so, these routers are both my private routers( not switches or modems, or etc). The router A is connected to local ISP.

seth wrote:

A rogue dhcp server causes all sorts of trouble and since you stated that
If arch is connected to the router A, then all is fine. For example, I can ping http://google.com (UPD addition: but when arch is connected to the router B, i can't ping (sick!)).
I suspected you might have a dhcp server on "router A" as well (but there isn't, nmap only found the one on "router B")

Okay, should I drop settings of dhcp on router B?

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 
       valid_lft forever preferred_lft forever
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether  brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.133/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 71672sec preferred_lft 71672sec
    inet6  scope link noprefixroute 
       valid_lft forever preferred_lft forever



default via 192.168.0.2 dev wlp2s0 proto dhcp src 192.168.0.133 metric 600 
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.133 metric 600 



resolvectl status >> problem
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.


yup, changes is here:
# Generated by NetworkManager
nameserver 1.1.1.1                          # so, did i do that?.. 0_o
nameserver 192.168.0.2
nameserver 2606:4700:4700::1111    # and that?.. 0_o
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver ef80:::::%wlp2s0

UPD:

nameserver 1.1.1.1                          # so, did i do that?.. 0_o
nameserver 2606:4700:4700::1111    # and that?.. 0_o

Yup, without these lines, i can't ping domains... I forgot to restart NM after changes last time.... I'm so silly, i'm sorry...

seth is a wizard, thank you <3

Last edited by tupadown228 (2022-10-27 23:53:32)

seth · 2022-10-28 07:56:33

Okay, should I drop settings of dhcp on router B?

This depends on how you want to configure the setup and whether router A and B ultimately should form 2 bridged subnets.
There must not be more than one dhcp server per subnet if you don't want to run into trouble.
If router A and B are supposed to be in the same subnet (though " I want two "independent" wi-fi networks" doesn't sound like that, though you can separate networks on a higher level) it doesn't matter where the dhcp server runs.

Your actual problem is that the dns server on 192.168.0.2 ("router B") doesn't work, but if eg. there's a DNS server on router A (likely 192.168.0.1 ?) you could also specifiy that as DNS server instead of 1.1.1.1

How to configure the network entirely depends on what you want to achieve, but the usualy private usage would be to run everything in one subnet, even if you've independent APs.
The implication is that systems left-of-fat-wall and right-of-fat-wall are in the same LAN

tupadown228 · 2022-10-28 16:15:32

seth wrote:

but if eg. there's a DNS server on router A (likely 192.168.0.1 ?) you could also specifiy that as DNS server instead of 1.1.1.1

Nope, i have tried to set 192.168.0.1 as dns on B, then as dns on arch( of course I didn't forget to restart them every time :3 ), but nothing worked. I can't connect to any internal ip( like ip of a connected windows machine to A, or a dhcp) of the router A from the router B. Of course i can connect to devices which are connected to B.

So, you are right.
I looked some materials and first i'll try to complete setup with 2 bridged subnets, than try to configure one subnet( just for fun). If i fail, now i know how to make two bridged subnets with not working dhcp on second router.)))

Last edited by tupadown228 (2022-10-28 16:21:21)

twelveeighty · 2022-10-31 15:25:20

I understand the 'just for fun' part, it's good experience to get it work that way. However, if you get tired of that, be aware that Wifi repeater 'pucks' are pretty inexpensive these days and they would save you the hassle of independently configured routers/switches.

Arch Linux

#1 2022-10-25 21:38:17

LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#2 2022-10-26 07:12:48

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#3 2022-10-26 09:01:26

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#4 2022-10-26 09:30:56

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#5 2022-10-26 10:04:29

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#6 2022-10-26 12:23:39

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#7 2022-10-26 13:21:09

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#8 2022-10-26 13:23:37

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#9 2022-10-26 13:43:33

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#10 2022-10-26 13:58:42

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#11 2022-10-26 15:09:38

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#12 2022-10-26 15:33:56

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#13 2022-10-26 20:40:24

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#14 2022-10-26 21:06:33

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#15 2022-10-26 21:56:47

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#16 2022-10-27 08:58:22

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#17 2022-10-27 09:24:28

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#18 2022-10-27 12:24:10

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#19 2022-10-27 15:09:44

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#20 2022-10-27 23:03:57

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#21 2022-10-27 23:25:33

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#22 2022-10-28 07:56:33

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#23 2022-10-28 16:15:32

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

#24 2022-10-31 15:25:20

Re: LAN by router via router. Two subnets. Can't ping a domain name. DNS.

Board footer