Hi,
I installed the paz00/ac100 tumbleweed image.
On every version (X11, XFCE, LXQT), I can’t reach other domains or upgrade with zypper.
A direct ping (ex. to 8.8.8.8) is no problem.
I tried adding nameserver 8.8.8.8 to */etc/resolv.conf *and
netconfig -f update
greetings
asgard
On 03/14/2018 12:46 PM, asgard4 wrote:
>
> I installed the paz00/ac100 tumbleweed image.
>
> On every version (X11, XFCE, LXQT), I can’t reach other domains or
> upgrade with zypper.
>
> A direct ping (ex. to 8.8.8.8) is no problem.
Ping uses ICMP packets, which are not the same as TCP or UDP packets; they
indicate (presumably) that a route works to the IP, but that does not mean
a lot of other things could not block your DNS packets using UDP or TCP,
and often those are blocked by environments.
Test the DNS side specifically:
dig @8.8.8.8 google.com
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
You are right, it is working if I remove the filtering from my router. BUT there was never a problem with android or ubuntu, maybe opensuse uses another port or something?
On 03/14/2018 04:56 PM, asgard4 wrote:
>
> ab;2858697 Wrote:
>>
>> Test the DNS side specifically:
>>
>>>
> Code:
> --------------------
> > >
> > dig @8.8.8.8 google.com
> >
> --------------------
>>>
>>
>
> You are right, it is working if I remove the filtering from my router.
> BUT there was never a problem with android or ubuntu, maybe opensuse
> uses another port or something?
‘dig’ is on openSUSE is it not? That would seem to invalidate your
conclusion.
I’ve never seen anything NOT use the standards-set UDP or TCP ports for
DNS stuff; port fifty-three (53) is the one that is used, always, and that
is basically required because there is nothing in the /etc/resolv.conf
file that allows specifying any other port. I have heard rumblings about
TLS-protected DNS, but I do not believe it is ratified, much less
implemented, yet.
My guess is that your other devices/boxes are not going out to 8.8.8.8 via
your router. Android implies a mobile device, so maybe it is using a
mobile data connection to get where it must. Ubuntu sounds like it should
work like opensuse; get a LAN/wire trace to see what it is really doing on
the wire as far as name resolution is concerned; I would guess it is
checking a local DNS server, and perhaps openSUSE is not doing that
because you mis-cnfigured it (using a wrong local IP, or bad netmask, or
just trying to point directly outside).
sudo /usr/sbin/tcpdump -n -s 0 -i any port 53
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
Please read the content of /etc/resolv.conf . Manually changing it requires removal of one line. But … to force regeneration of the file do
sudo rcnetwork stop
sudo rm /etc/resolv.conf
sudo rcnetwork start
FYI -
The comment in /etc/resolv.conf about “netconfig -f update” is confusing.
And,
When I ran a test, “netconfig -f update” undid all manual edits to the file which probably happened to you as well (so no wonder you couldn’t resolve any Internet domains if the original /etc/resolv.conf doesn’t work).
If you want to activate your modified /etc/resolv.conf, you should instead simply restart your network service, eg
systemctl restart network
Additionally,
“dig” can be used but is limited for troubleshooting.
The standard “do everything” command for displaying and troubleshooting name resolution is
nslookup
eg the following on your machine and see all the useful info
nslookup
> www.google.com
In your case, if you ran the above commands to test Google name resolution, you would have quickly found that you weren’t querying your newly configured nameserver.
Among the many things you can do with nslookup
HTH,
TSU