Problem with Google

I can’t install this package, i don’t understand why ?
root@turris:~# opkg install knot-resolver_1.2.5-3_mvebu.ipk
Collected errors:

  • wfopen: knot-resolver_1.2.5-3_mvebu.ipk: No such file or directory.
  • pkg_init_from_file: Failed to extract control file from knot-resolver_1.2.5-3_mvebu.ipk.

You must make steps as described by “oerdnj” in previous post.

cd /tmp
wget https://repo.turris.cz/omnia-dev-ondrej/packages/turrispackages/knot-resolver_1.2.5-3_mvebu.ipk
opkg install knot-resolver_1.2.5-3_mvebu.ipk

Zdravím, Ondřeji. Tato Vaše odpověď by se velice líbila @miska, který nám na konci semináře “Turris Omnia prakticky” promítl poslední slide s informací: “Na Internetu se to poslední dobou jen hemží návody typu stáhněte si pomocí wget nebo curl nějaký balíček či skript a nainstalujte či spusťte ho na svém routeru. To doma nikdy nedělejte. Jde to proti všem best practise.”

Potěšil by jste jej … :slight_smile:

P.S.: Sorry for Czech, but it is only a off-topic :slight_smile:

1 Like

This isn’t just “somewhere from the internet”. Still, I recommend you to use that link with https:// at least :wink:

Good catch, I somehow missed the https:// in the repo.turris.cz, fixed, thanks.

1 Like

hello, did you change from:
knot-resolver_1.2.5-3_mvebu.ipk
to
knot-resolver_1.2.6-1_mvebu.ipk
?

Hi,
at this moment i have installed 1.2.5-3 .
Now i try reinstall with 1.2.6 but for relevant result is need some time. (is need few hours)

After three hours with version 1.2.6-1 it still works ok.

The announcement for Turris 0S 3.6 (due today) includes an upgrade of the Knot resolver. Will it solve this very serious bug?

I believe it will. (fill to 20 chars)

The problem with Google that appeared in Turris OS 3.6.2 is fixed and tested in 3.6.3 that is now in RC branch and it should be out in master today.

EDIT: 3.6.3 update have been published, your routers should intstall it automatically soon. In case you are eager user :slight_smile: you can install it manually.

just write these lines in SSH

opkg update
updater.sh
reboot
3 Likes

I’m asking again: what I have to do to revert changes I made to help you identify dns problems?
I have knot-resolver - 1.2.5-3 manually installed and I asked you for info how to revert changes. Could I edit auto.lua or should I use some commands?
Why you not provide these informations as a part of original post?

I have still issues with DNS even after this update. For example:

root@turris:~# dig support.skype.com ANY

; <<>> DiG 9.9.8-P4 <<>> support.skype.com ANY
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOTIMP, id: 49895
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;support.skype.com.             IN      ANY

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Apr 28 00:34:00 CEST 2017
;; MSG SIZE  rcvd: 46

root@turris:~# dig support.skype.com ANY @8.8.8.8

; <<>> DiG 9.9.8-P4 <<>> support.skype.com ANY @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63531
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;support.skype.com.             IN      ANY

;; ANSWER SECTION:
support.skype.com.      157     IN      CNAME   support.skype.com.edgekey.net.

;; Query time: 22 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Apr 28 00:34:05 CEST 2017
;; MSG SIZE  rcvd: 89

Is this common problem or is only my Omnia affected?

Hello,

ANY query type is special and should be used only for diagnostic purposes, which is reason why resolver might decide not to support it (which is the case of Knot resolver). It would be a problem only if other query types were failing.

To read more about ANY query type please see:
https://tools.ietf.org/html/draft-ietf-dnsop-refuse-any

2 Likes

Depends how did you install it. You can edit auto.lua manually if you installed it by downloading and installing package or you can delete overrides in /etc/config/updater and run updater.sh

I installed it exactly how it was suggested in this post:
https://forum.turris.cz/t/problem-with-google/3967/43?u=pav
I would like to know how to revert these changes as a part of install instructions. New OS version is out, my knot-resolver stays on old version (not all people will register this) and no info for people helping you that they have to do something. It is coincidence I found the record in auto.lua.
I thought I could edit this file, but I rather ask after seeing this “-- A file with auto-generated Install commands. Do not edit.” note.

Ok, then it should be fine just deleting lines from auto.lua mentioning knot-resolver. It is part of user base userlist, so it wouldn’t get uninstalled even if it isn’t mentioned in auto.lua at all.

As of the past week, now I can’t log into ebay accounts on Turris. I can with no problem if I use my mobile smartphone and 4G but not via Turris either Wifi or direct connection.

Hello. I think it is not a DNS problem, you would not be getting HTTP 503 error or timeouts… but I might be wrong.

Please verify if all of the names mentioned in error messages can be resolved using nslookup. Following article shows how it can be done using tool nslookup:
https://blog.thesysadmins.co.uk/nslookup-common-usage-examples.html

1 Like