I have tried wat i’ve find on forums but nothing work
I’m on gnome. Anyone can suggest wat I can do?
Even with a rescue cd with the same 4.18 kernel I can’t get internet connection. I’m not an expert so …
Thanks
You’ve given us no information to advise specifically here. Hardware (chipset) details are needed as a minimum. To get that definitive information run
/sbin/lspci -nnk|grep -iA3 net
or
/usr/sbin/hwinfo --netcard
One method you could use to get that information to us would be to save to a text file and transfer to a memory stick, then post from an internet-connected machine.
Thanks deano, I didn’t know what info was needed.
I’ve put the information you asked and some more here
More is always good. 
From that we can now tell that the NIC is working (supported by the r8169 driver). The ethernet device eth0 has an assigned address 192.168.2.3, and the default gateway (192.168.2.1) is reachable.
The next step is to try and ping a well-known internet address eg 8.8.8.8
ping 8.8.8.8
I suspect that will work, and that your real issue may be that name resolution is not working. Check
grep name /etc/resolv.conf
If necessary, remove that file with
sudo rm -f /etc/resolv.conf
and restart the network with
sudo systemctl restart network
then see if you can ping/resolve by hostname.
Oops…my bad I missed this…
1. ping -c1 192.168.2.1
1. PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
1.
1. --- 192.168.2.1 ping statistics ---
1. 1 packets transmitted, 0 received, 100% packet loss, time 0ms
Some additional questions…
Can other hosts connect to the internet successfully via this router?
Can you ping other hosts on the LAN successfully?
Have you tried restarting the router?
Yes even me in the same cp but windows. Or before I loos’it on kernel 4.17.
I’ve restarted the router and I can ping other host in the lan !!!
I send you another file with the results for your code hope that help
http://susepaste.org/71220774
Those results look like progress. All good now?
No
Sorry
All the same, no internet not even acess to the modem
I don’t know if it is clear that this problem start with the actualization to the kernel 4.18.
I have set my desktop to keep only two kernels.
In the first dup I still have the k4.17 and if I boot to it I had internet but if I booted to k4.18 there was no internet. Unfortunately with the last dup I loose the k4.17
More
I have a rescue pen with TW k4.18 - no internet
I have a livecd with a 3 months old TW - I have internet
Okay, I misunderstood what you were trying to convey in post #7. So that output was from when you were booted with kernel 4.17. It’s clearly a kernel regression with the r8169 driver perhaps. As such you’re best advised to submit a bug report.
Ok, deano
Thanks for your support, l will try to submit a bug.
But nevertheless in case someone have a suggestion I will stay on this thread
Hi
There is a bug open with the same problem but slightly different hardware than mine “bug 1105573”
I tried the testing kmp that is there and now I have normal acess to modem and internal lan but still no internet 
Well, after some tries in the networkmanager and systemctl restart network I have internet again 
Good to know.
Reviewing this thread and your susepaste,
The only problem I see in what you posted is that you were unable to ping your default gateway.
After “some tries in the networkmanager and systemctl restart network” you say you have the Internet again,
You should re=run the following to verify your IP address hasn’t changed and your ping test has a different result
ip addr
ping -c3 192.168.2.1
Note I’m recommending more than one ping, that may not be necessary but makes clearer whether you have reliable connectivity or not.
If your IP address changed, it means there might have been an IP address conflict (some other device has been assigned that address also).
It’s a bit late now, but it might have also been interesting if you had inspected the DHCP lease on your DHCP server before you ran “systemctl restart network” to see if the lease had expired… There won’t likely be any useful information now but it might be useful to take a look at your system logs on your gateway device to see if there are rejected connections… I’m speculating that if your openSUSE might not have been registered as a “valid device” by your Internet Gateway due to no valid DHCP lease that connections might have been rejected… But this is highly speculative without knowing a lot about your gateway device.
Because it seems you’re now successfully connecting, it’ll be hard if not impossible to determine exactly what was wrong before so
Wildly speculating,
TSU
thank you deano for your help
tsu2 - sorry I’m not so expert 
but there is in fact one difference:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 64:70:02:01:f6:45 brd ff:ff:ff:ff:ff:ff
*inet 192.168.2.2/24* brd 192.168.2.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::7f47:375d:19c2:5c85/64 scope link noprefixroute
valid_lft forever preferred_lft forever
and as you see now:
ping -c3 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=2.39 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.954 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=9.75 ms
--- 192.168.2.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 0.954/4.361/9.745/3.851 ms
I think the main problem it is on the r8169 drive that came with 4.18 kernel, but as I have tried every thing I have found to fix it, it’s possible that I’ve change something to the wrong side
do I must mark this tread as solved?
thanks everybody.
No need to mark it as such, although you can always edit the title on your reply to indicate this if desired.