About eth0:
You say it is directly connected to the internet, thus no router in btween. Thus you are your own ISP. Are you really using some DHCP server somewhere on the internet?
About eth1:
You say it has a DHCP server running. Which means that it provides IP addresses, etc. to other systems. But how about the IP address, etc. of eth1?
And what about this? I suggested, asked you once and now ask you again. But this is the last time.
And please take into account that we have very scant information. As you say it is problematic to transfer the console output from your system without network connection to a neat paste into a post here. But that does not help us in understanding. Write output to a USB stick and go to another system to post, or whatever.
We need:
ip addr
(and no, not part of it, but all of it)
ip route
and
cat /etc/hosts
And of course the last after every change you make.
In a way that is true. There is other equipment between it and the internet, modems, gateways etc…
The IP Address of eth1 is fixed. Other devices connected to eth1 will apply to lease an IP Address from the DHCP server running from eth1.
I had been using that method until I was diverted to sysconfig-editor. Is there anything specific you want to know (I’m unable to do screen captures at the moment).
#ip addr
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: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:00:5a:00:01:33 brd ff:ff:ff:ff:ff:ff
altname enp5s0
altname ens3
inet 192.168.175.1/24 brd 192.168.175.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::200:5aff:fe00:133/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:1f:16:2a:d0:31 brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 192.168.1.100/24 brd 192.168.1.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::21f:16ff:fe2a:d031/64 scope link
valid_lft forever preferred_lft forever
4: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:1e:65:eb:ef:c2 brd ff:ff:ff:ff:ff:ff
altname wlp3s0
altname wls1
#ip route
default via 192.168.1.1 dev eth1 proto dhcp
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.100
192.168.175.0/24 dev eth2 proto kernel scope link src 192.168.175.1
#cat /etc/hosts
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
# special IPv6 addresses
127.0.0.1 localhost
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
It has occurred to me that 15.4 upgrade has changed the “eth” numbering - eth1 is now eth2, and eth0 is now eth1… I’m going through the firewall settings to see if they are okay…
I don’t understand what you mean. However, I always return settings to there original state if the change has no improvement.
That is fine, but we can not know that when you do not explain that.
There are many people with problems here that change a lot of things while they are waiting for answers. Thus when we answer, the whole situation has changed and we are always to late to understand what is going on. In other words, we mistrust people very much, but we trust computer listings.
================
I would say, either use the YaST module I suggested or change /etc/resolv.conf by editor. First check if it is a symbolic link or not. That sometimes happens.
Then edit, throw away the 127.0.0.2 and the 0.0.0.0. I assume that what remains is the DNS server you want to use. Else make it 8.8.8.8, that is Google’s DNS server (and use until repaired what was wrong).
I’ve had enough for today, I’ll be reverting back to 15.3 now (I cloned the disk before I started).
I’ll examine the 15.3 settings tomorrow. My gut feeling is that it is either dns or ipv4/ipv6 tunneling used by dns…
BTW I made this connection to the forum via a tether to my phone, however, if I disconnect the tether, and use my system - it still works. But I can’t make new connections, or reestablish old connections…
I think I’m getting to the bottom of this issue, but I need some more help.
I have been playing around with DNS Forwarders, but I wasn’t getting anywhere…
I couldn’t find any trace of DNS activity in the system logs.
In yast > networking > dns-server > logging- I changed the DNS log file destination to it’s own file, then after some more tests - the log file hadn’t been created.
I then realised that in yast > networking > dns-server > startup the current status is ‘inactive’.
I changed the After writing configuration to ‘Start’, then when I press Apply, I get an error ‘saving the configuration failed’.
/etc/resolv.conf is a link.
Whether or not yast > networking > dns-server updates the nameservers in the /etc/resolv.conf list, depends on the option selected in the Local DNS Resolotion Forwarder.
I have tried editing the file myself, and via yast - I haven’t been able to resolve this issue…
### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
nameserver 203.168.238.99
nameserver 118.127.62.178
nameserver 103.209.24.69
I have tried many, many name servers, including 1.1.1.1, 8.8.8.8, 1.0.0.1…
I have noticed that the firewall doesn’t open port 53 for dns…
Either I don’t understand what you are saying, or you don’t understand what I’m trying to achieve. I need to get dns to pass through my machine, from the “local area port” to the “wide area port”. For dns to pass through I would need port 53 open on the local port…?
Using yast > firewall > internal > services I can see dns is selected, but yast > firewall > internal > ports doesn’t include port 53. I tried to enter it manual but it didn’t stick.
If I add dns-over-tls it lists port 53 yast > firewall > internal > ports.
I have two things to report. Hopefully, this will find its way to the developers:-
1) yast > firewall - adding dns to an interface DOES NOT unblock port 53.
Workaround - add dns, then add dns-over-tls, then remove dns-over-tls.
2) Leap Updater - the Updater should NOT overwrite MODIFIED configuration files. It should use a wizard to merge then.
If that is not possible, then keep the old files, and generate a report listing the modified configuration files that have been replaced.
#sudo rpmconfigcheck
Searching for unresolved configuration files
Please check the following files (see /var/adm/rpmconfigcheck):
/etc/chrony.conf.rpmnew
/etc/named.conf.rpmnew
/etc/nginx/nginx.conf.rpmnew
/etc/nsswitch.conf.rpmnew
/etc/postfix/main.cf.rpmnew
/etc/postfix/master.cf.rpmnew
