Mint13 MATE: DNS not working for new wireless connections

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
BrunoMiranda
Level 4
Level 4
Posts: 359
Joined: Thu Jun 24, 2010 2:22 pm

Mint13 MATE: DNS not working for new wireless connections

Post by BrunoMiranda »

Hi all!

I'm having a weird behavior on my Mint13 laptop: On my own wireless internet connection, everything is working fine. But if I add some new wireless connection, even an open one without encryption, I can connect, ping IP addresses (I use 8.8.8.8 ) but I cannot ping to any DNS name.

ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=423 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=346 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=369 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 346.078/379.832/423.816/32.550 ms



nslookup 8.8.8.8
;; connection timed out; no servers could be reached




Is seems DNS is not resolving to any new connections but on my own everything works fine.

While connected to my own working wifi:
(I'll add the results from another non-working connection when I connect myself to one)
sudo /usr/lib/linuxmint/mintWifi/mintWifi.py


-------------------------
* I. scanning WIFI PCI devices...
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

wlan1 IEEE 802.11bg ESSID:"Gateway2Hell"
Mode:Managed Frequency:2.462 GHz Access Point: 28:9A:FA:3D:08:18
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=36/70 Signal level=-74 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:51 Missed beacon:0

eth0 no wireless extensions.

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet Endereço de HW 00:03:0d:9f:ee:eb
UP BROADCAST MULTICAST MTU:1500 Métrica:1
pacotes RX:0 erros:0 descartados:0 excesso:0 quadro:0
Pacotes TX:0 erros:0 descartados:0 excesso:0 portadora:0
colisões:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
IRQ:41 Endereço de E/S:0x6000

lo Link encap:Loopback Local
inet end.: 127.0.0.1 Masc:255.0.0.0
endereço inet6: ::1/128 Escopo:Máquina
UP LOOPBACK RUNNING MTU:16436 Métrica:1
pacotes RX:0 erros:0 descartados:0 excesso:0 quadro:0
Pacotes TX:0 erros:0 descartados:0 excesso:0 portadora:0
colisões:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan1 Link encap:Ethernet Endereço de HW 00:10:60:36:23:7c
inet end.: 192.168.0.243 Bcast:192.168.0.255 Masc:255.255.255.0
endereço inet6: fe80::210:60ff:fe36:237c/64 Escopo:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Métrica:1
pacotes RX:3177 erros:0 descartados:0 excesso:0 quadro:0
Pacotes TX:2593 erros:0 descartados:0 excesso:0 portadora:0
colisões:0 txqueuelen:1000
RX bytes:2662331 (2.6 MB) TX bytes:436687 (436.6 KB)

-------------------------
* V. querying DHCP...
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.0.1
Address: 192.168.0.1#53

Non-authoritative answer:
Name: google.com
Address: 216.58.210.110



The hosts file seems clean and legit.
cat /etc/hosts

127.0.0.1 localhost
127.0.1.1 mint13

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters



When I use MATE's network manager to connect to a new wireless connection, it behaves kinda weird: sometimes it does not detect the network (the SSID does not show up in there), or if it does it does not ask me for a password. If I create a new connection and enter everything manually, it will connect but only ping by IP address and not by DNS name.

I've got 2 kernels (2.6.39-02063904-generic and 3.2.66-030266-generic) and it behaves the same way with both of them, so I think we can exclude kernel problems here...


Any help troubleshooting this one, please?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Bye for now,
Bruno


(Always backup before you screw up :)
BrunoMiranda
Level 4
Level 4
Posts: 359
Joined: Thu Jun 24, 2010 2:22 pm

Re: Mint13 MATE: DNS not working for new wireless connection

Post by BrunoMiranda »

Ok, here's the result of from a network I had trouble resolving DNS names:

sudo /usr/lib/linuxmint/mintWifi/mintWifi.py

-------------------------
* I. scanning WIFI PCI devices...
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

wlan1 IEEE 802.11bg ESSID:"CFP Seixal"
Mode:Managed Frequency:2.462 GHz Access Point: 00:0C:F6:16:45:38
Bit Rate=48 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=42/70 Signal level=-68 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:21 Missed beacon:0

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet Endereço de HW 00:03:0d:9f:ee:eb
UP BROADCAST MULTICAST MTU:1500 Métrica:1
pacotes RX:0 erros:0 descartados:0 excesso:0 quadro:0
Pacotes TX:0 erros:0 descartados:0 excesso:0 portadora:0
colisões:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
IRQ:41 Endereço de E/S:0x4000

lo Link encap:Loopback Local
inet end.: 127.0.0.1 Masc:255.0.0.0
endereço inet6: ::1/128 Escopo:Máquina
UP LOOPBACK RUNNING MTU:16436 Métrica:1
pacotes RX:4 erros:0 descartados:0 excesso:0 quadro:0
Pacotes TX:4 erros:0 descartados:0 excesso:0 portadora:0
colisões:0 txqueuelen:0
RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)

wlan1 Link encap:Ethernet Endereço de HW 00:10:60:36:23:7c
inet end.: 192.168.26.18 Bcast:192.168.255.255 Masc:255.255.0.0
endereço inet6: fe80::210:60ff:fe36:237c/64 Escopo:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Métrica:1
pacotes RX:262 erros:0 descartados:0 excesso:0 quadro:0
Pacotes TX:111 erros:0 descartados:0 excesso:0 portadora:0
colisões:0 txqueuelen:1000
RX bytes:30030 (30.0 KB) TX bytes:15652 (15.6 KB)

-------------------------
* V. querying DHCP...
-------------------------
* VI. querying nslookup google.com...
Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
Name: google.com
Address: 216.58.210.110



The weird thing is: (and I've seen this happening several times)

I connect to a network and ping does not work because DNS does not resolve names. But after running mintWifi.py, it starts to work normally! :?:
The same thing happened before running the script now.

Does anyone know if there is any command on mintWifi.py that resets DNS or does something relative to this? :?:

I'm puzzled and lost here... :?
Bye for now,
Bruno


(Always backup before you screw up :)
Locked

Return to “Networking”