Can only access Google sites after upgrade - PPPOE

English Network/Internet
#1

Hello everyone.

I’m kinda desperate here.
As a few days ago, after a “zypped dup” the network stopped working right.
I’m on PPPOE and it connects allright.
But i can only access Google sites (Gmail, search, Youtube …).
Anything else just loads forever …

I pinged different hosts like google.com, yahoo.com, phoronix.com, etc.
It is ok, responses are around 190ms.

I am using Network Manager since whatever the other option Opensuse uses for PPPOE never worked for me.

Please help in anyway since this will be complicated (i don’t have another home computer).
I can’t connect from this PC since, well, it does not work …
I am posting from my work PC, which is at my work place (a few km away from home) …
Teamviewer does not work …

Heelp ?

PS
There’s no point in calling my ISP since they are usually clueless (been there before).

#2

That could be an MTU problem, and perhaps a failure in determining path MTU.

When I was on dsl and PPOE, I would ping with large packets. Check the man page for ping to see how to do that.

Standard ping uses small packets. As the packet size increase, there is a higher chance of packet loss. I used this to investigate dsl line problems.

You could maybe just set your MTU to smaller. The default is 1500. When using PPOE, I think the limit is 1492. Just setting MTU to that might help. If you have line problems, try something smaller like 1400, or 1200 or even 800.

You can set the MTU in Yast Network settings if you are not using NetworkManager. You can set it for the connection with NetworkManager.

#3

On 2015-09-14 09:06, Ionel wrote:

> But i can only access Google sites (Gmail, search, Youtube …).
> Anything else just loads forever …

Check the routing table.
Check sites with traceroute.

> I pinged different hosts like google.com, yahoo.com, phoronix.com, etc.
> It is ok, responses are around 190ms.

Maybe nrickert is right. Check by increasing ping size.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#4

I managed last evening to do something.

Since whatever opensuse threw at PPPOE never ever worked for me, i used Network manager since that did work after some arm wrestling.
I decreased the MTU down to 100 … nothing worked.
Then just set it to 2000 and it did work.
But this morning it stopped working again.
Just threw 2500 at it and it started working.

But this is just insane. I can’t just throw numbers at it whenever i actually need to load a darn page.
One note, tho. While under Plasma 5 i get some 5-6 messages of PPPOE connected/disconnected, especially if i try to load a page.
(Gnome does not show the messages since, well, it does not show them but connecting/disconnecting and not working anyway).
Tried rp-ppoe but never managed to get it to work ever …
Don’t know if it means something or not.

Another thing.
Out of severe frustration, i threw an ancient Knoppix 7.2 livecd and booted that.
Just threw the UserName and Password and kept hitting enter and the darn thing just worked.
There is something terribly wrong about the tumbleweed upgrade.
It borked something and did not bother telling what.
And with my extremely limited networking skill set it’s actually impossible for me to know wth happened …

I am really tempted to just wipe the darn thing from my system but that would need even more effort …

I just feel stupid …
>:(:(:’(

#5

I managed last evening to do something.

Since whatever opensuse threw at PPPOE never ever worked for me, i used Network manager since that did work after some arm wrestling.
I decreased the MTU down to 100 … nothing worked.
Then just set it to 2000 and it did work.
But this morning it stopped working again.
Just threw 2500 at it and it started working.

So, just setting it to 1492 is not working for you? Here’s how you can use ping to determine/verify the appropriate MTU size
http://muzso.hu/2009/05/17/how-to-determine-the-proper-mtu-size-with-icmp-pings

But this is just insane. I can’t just throw numbers at it whenever i actually need to load a darn page.
One note, tho. While under Plasma 5 i get some 5-6 messages of PPPOE connected/disconnected, especially if i try to load a page.
(Gnome does not show the messages since, well, it does not show them but connecting/disconnecting and not working anyway).
Tried rp-ppoe but never managed to get it to work ever …
Don’t know if it means something or not.

Maybe you can capture some pppd errors using

journalctl -f --no-pager | grep pppd

Another thing.
Out of severe frustration, i threw an ancient Knoppix 7.2 livecd and booted that.
Just threw the UserName and Password and kept hitting enter and the darn thing just worked.
There is something terribly wrong about the tumbleweed upgrade.
It borked something and did not bother telling what.
And with my extremely limited networking skill set it’s actually impossible for me to know wth happened …

I am really tempted to just wipe the darn thing from my system but that would need even more effort …

I just feel stupid …
>:(:(:’(

No, don’t be hard on yourself. Understanding the idiosyncrasies and intricacies of PPPOE sessions does require specific knowledge that would challenge most users trying to troubleshoot problematic connections.

#6

First thing i tried was to set it to 1492 … didn’t do anything …

I will try to do as you suggested but it feels unnecessary.
I mean, NM has the “Automatic” setting for MTU (presuming that is the culprit) which always worked before but not anymore.
I find it weird that i have to find a “good” value and feed it to NM from time to time …
Why did Knoppix work right away ? It seems it has set everything right.
Something is definitely rotten in the kingdom of networking on this tumbleweed box …

#7

On 2015-09-15 13:56, Ionel wrote:
> Why did Knoppix work right away ? It seems it has set everything right.
> Something is definitely rotten in the kingdom of networking on this
> tumbleweed box …

Well… IMO, Tumbleweed is kind of experimental, it is changing
continuously, on the knife edge. Maybe you should instead use the stable
release… (13.2)

Otherwise, once you locate the problem, you will have to report it in a
Bugzilla and track its solution, so that it is eventually solved.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#8

I agree that it should just work, but experimenting is sometimes necessary as part of the troubleshooting process. This may well be a regression with NM (or at least the pppd plugin), so a bug report is a good idea.

#9

The ping thing said 1465 is too long but 1464 is ok.

The thing is, the network will work at random with higher or lower values …
And also it seems now even google stops working …

“journalctl -f --no-pager | grep pppd” gives absolutely nothing (just emty space).

What to do ?
Regarding Tumbleweed, it’s not THAT bleeding edge.
Besides, i’ve had more issues with 13.1 before switching to tumbleweed, so …

#10

On 2015-09-15 21:16, Ionel wrote:

> “journalctl -f --no-pager | grep pppd” gives absolutely nothing (just
> emty space).

The command waits till there is new activity to print. You have to
connect to internet after running that command, do things on internet,
and then see if something is printed there.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#11

I would not suspect MTU.
Unless someone somewhere (particularly your ISP if many sites are affected) is using very ancient hardware (>15 years? ) and you are located somewhere in the industrialized world (not third world) you just should not see any MTU problems.

Instead,
I recommend you determine if

  • Your problem is related to routing tables. Use the “traceroute” command to map routes and responses to your destinations.
  • Your problem may be IPv6 routing related.

So, as an example
I am located on the west coast of USA.
There seems to have been a major switch by major routers approx 2 months ago to attach a higher priority to using IPv6 over IPv4.
But, the switchover revealed a number of poorly engineered and incomplete IPv6 routing “hints” resulting in a number of sites to all of a sudden become undiscoverable (because routes to the destination couldn’t be found).

The solution to the IPv6 routing problems?
Of course it was to simply disable IPv6 and force IPv4 which has been and is still very reliable.
Those routing companies can experiment on others until they get their act straightened out… and not victimizing me.

TSU

#12

Autoconnection with MTU 1500 worked.

I set it to automatic, disconnect and:

linux-acasa:/home/tata # journalctl -f --no-pager | grep pppd
sep 16 21:05:40 linux-acasa NetworkManager[759]: <info> pppd started with pid 2438
sep 16 21:05:40 linux-acasa pppd[2438]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:05:40 linux-acasa NetworkManager[759]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:05:40 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (plugin_init): initializing
sep 16 21:05:40 linux-acasa pppd[2438]: pppd 2.4.7 started by root, uid 0
sep 16 21:05:40 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase ‘serial connection’
sep 16 21:05:40 linux-acasa pppd[2438]: Using interface ppp0
sep 16 21:05:40 linux-acasa pppd[2438]: Connect: ppp0 <–> /dev/pts/1
sep 16 21:05:40 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
sep 16 21:05:43 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase ‘authenticate’
sep 16 21:05:43 linux-acasa pppd[2438]: PAP authentication succeeded
sep 16 21:05:43 linux-acasa pppd[2438]: local LL address fe80::0000:0000:3ee7:41b6
sep 16 21:05:43 linux-acasa pppd[2438]: remote LL address fe80::0000:0000:0000:0001
sep 16 21:05:43 linux-acasa pppd[2438]: local IP address 62.231.65.182
sep 16 21:05:43 linux-acasa pppd[2438]: remote IP address 10.0.0.1
sep 16 21:05:43 linux-acasa pppd[2438]: primary DNS address 193.231.252.1
sep 16 21:05:43 linux-acasa pppd[2438]: secondary DNS address 213.154.124.1
sep 16 21:05:44 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials…
sep 16 21:05:44 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager
sep 16 21:05:44 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
sep 16 21:05:44 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 9 / phase ‘running’
sep 16 21:05:44 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip6_up): ip6-up event
sep 16 21:05:44 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip6_up): sending IPv6 config to NetworkManager…
sep 16 21:05:44 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): ip-up event
sep 16 21:05:44 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): sending IPv4 config to NetworkManager…
sep 16 21:07:45 linux-acasa pppd[2438]: Terminating on signal 15
sep 16 21:07:45 linux-acasa pppd[2438]: Connect time 2.1 minutes.
sep 16 21:07:45 linux-acasa pppd[2438]: Sent 8170 bytes, received 304 bytes.
sep 16 21:07:45 linux-acasa pppd[2438]: cif6addr: ioctl(SIOCDIFADDR): No such address
sep 16 21:07:45 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 10 / phase ‘terminate’
sep 16 21:07:45 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
sep 16 21:07:45 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
sep 16 21:07:45 linux-acasa pppd[2438]: Connection terminated.
sep 16 21:07:45 linux-acasa pppd[2438]: Connect time 2.1 minutes.
sep 16 21:07:45 linux-acasa pppd[2438]: Sent 8170 bytes, received 304 bytes.
sep 16 21:07:45 linux-acasa pppd[2438]: Script /usr/sbin/pppoe -I ‘enp2s0’ finished (pid 2440), status = 0x1
sep 16 21:07:45 linux-acasa pppd[2438]: Exit.
sep 16 21:07:45 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 11 / phase ‘disconnect’
sep 16 21:07:45 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 1 / phase ‘dead’
sep 16 21:07:45 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_exit_notify): cleaning up
sep 16 21:08:07 linux-acasa NetworkManager[759]: <info> pppd started with pid 2845
sep 16 21:08:07 linux-acasa pppd[2845]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:08:07 linux-acasa NetworkManager[759]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:08:07 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (plugin_init): initializing
sep 16 21:08:07 linux-acasa pppd[2845]: pppd 2.4.7 started by root, uid 0
sep 16 21:08:07 linux-acasa pppd[2845]: Using interface ppp0
sep 16 21:08:07 linux-acasa pppd[2845]: Connect: ppp0 <–> /dev/pts/1
sep 16 21:08:07 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase ‘serial connection’
sep 16 21:08:07 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
sep 16 21:08:08 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase ‘authenticate’
sep 16 21:08:08 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials…
sep 16 21:08:08 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager
sep 16 21:08:08 linux-acasa pppd[2845]: PAP authentication succeeded
sep 16 21:08:08 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
sep 16 21:08:08 linux-acasa pppd[2845]: local LL address fe80::0000:0000:567b:ff3c
sep 16 21:08:08 linux-acasa pppd[2845]: remote LL address fe80::0000:0000:0000:0001
sep 16 21:08:08 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 9 / phase ‘running’
sep 16 21:08:08 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip6_up): ip6-up event
sep 16 21:08:08 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip6_up): sending IPv6 config to NetworkManager…
sep 16 21:08:08 linux-acasa pppd[2845]: local IP address 86.123.255.60
sep 16 21:08:08 linux-acasa pppd[2845]: remote IP address 10.0.0.1
sep 16 21:08:08 linux-acasa pppd[2845]: primary DNS address 193.231.252.1
sep 16 21:08:08 linux-acasa pppd[2845]: secondary DNS address 213.154.124.1
sep 16 21:08:08 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): ip-up event
sep 16 21:08:08 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): sending IPv4 config to NetworkManager…
sep 16 21:09:11 linux-acasa pppd[2845]: Terminating on signal 15
sep 16 21:09:11 linux-acasa pppd[2845]: Connect time 1.1 minutes.
sep 16 21:09:11 linux-acasa pppd[2845]: Sent 6748 bytes, received 304 bytes.
sep 16 21:09:11 linux-acasa pppd[2845]: cif6addr: ioctl(SIOCDIFADDR): No such address
sep 16 21:09:11 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 10 / phase ‘terminate’
sep 16 21:09:11 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
sep 16 21:09:11 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
sep 16 21:09:11 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 11 / phase ‘disconnect’
sep 16 21:09:11 linux-acasa pppd[2845]: Connection terminated.
sep 16 21:09:11 linux-acasa pppd[2845]: Connect time 1.1 minutes.
sep 16 21:09:11 linux-acasa pppd[2845]: Sent 6748 bytes, received 304 bytes.
sep 16 21:09:11 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 1 / phase ‘dead’
sep 16 21:09:11 linux-acasa pppd[2845]: Script /usr/sbin/pppoe -I ‘enp2s0’ finished (pid 2847), status = 0x1
sep 16 21:09:11 linux-acasa pppd[2845]: Exit.
sep 16 21:09:11 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_exit_notify): cleaning up

#13

CONTINUATION

sep 16 21:09:24 linux-acasa NetworkManager[759]: <info> pppd started with pid 3141
sep 16 21:09:24 linux-acasa pppd[3141]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:09:24 linux-acasa NetworkManager[759]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:09:24 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (plugin_init): initializing
sep 16 21:09:24 linux-acasa pppd[3141]: pppd 2.4.7 started by root, uid 0
sep 16 21:09:24 linux-acasa pppd[3141]: Using interface ppp0
sep 16 21:09:24 linux-acasa pppd[3141]: Connect: ppp0 <–> /dev/pts/1
sep 16 21:09:24 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase ‘serial connection’
sep 16 21:09:24 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
sep 16 21:09:25 linux-acasa NetworkManager[3150]: <info> pppd started with pid 3157
sep 16 21:09:25 linux-acasa pppd[3157]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:09:25 linux-acasa NetworkManager[3150]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (plugin_init): initializing
sep 16 21:09:25 linux-acasa pppd[3157]: pppd 2.4.7 started by root, uid 0
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase ‘serial connection’
sep 16 21:09:25 linux-acasa pppd[3157]: Using interface ppp1
sep 16 21:09:25 linux-acasa pppd[3157]: Connect: ppp1 <–> /dev/pts/2
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase ‘authenticate’
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials…
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager
sep 16 21:09:25 linux-acasa pppd[3157]: PAP authentication succeeded
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
sep 16 21:09:25 linux-acasa pppd[3157]: local LL address fe80::0000:0000:3ee7:4246
sep 16 21:09:25 linux-acasa pppd[3157]: remote LL address fe80::0000:0000:0000:0001
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 9 / phase ‘running’
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip6_up): ip6-up event
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip6_up): sending IPv6 config to NetworkManager…
sep 16 21:09:25 linux-acasa pppd[3157]: local IP address 62.231.66.70
sep 16 21:09:25 linux-acasa pppd[3157]: remote IP address 10.0.0.1
sep 16 21:09:25 linux-acasa pppd[3157]: primary DNS address 193.231.252.1
sep 16 21:09:25 linux-acasa pppd[3157]: secondary DNS address 213.154.124.1
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): ip-up event
sep 16 21:09:25 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): sending IPv4 config to NetworkManager…
sep 16 21:09:27 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase ‘authenticate’
sep 16 21:09:27 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials…
sep 16 21:09:27 linux-acasa dbus[641]: [system] Rejected send message, 9 matched rules; type=“error”, sender=":1.114" (uid=0 pid=3150 comm="/usr/sbin/NetworkManager --no-daemon “) interface=”(unset)"
member="(unset)" error name=“org.freedesktop.DBus.Error.UnknownMethod” requested_reply=“0” destination=":1.113" (uid=0 pid=3141 comm="/usr/sbin/pppd nodetach lock nodefaultroute ipv6 ,")
sep 16 21:09:27 linux-acasa NetworkManager[759]: (process:3141): nm-pppd-plugin-WARNING **: nm-ppp-plugin: (get_credentials): could not get secrets: (19) GDBus.Error:org.freedesktop.DBus.Error.Unknown
Method: Method “NeedSecrets” with signature “” on interface “org.freedesktop.NetworkManager.PPP” doesn’t exist
sep 16 21:09:27 linux-acasa pppd[3141]: PAP authentication succeeded
sep 16 21:09:27 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
sep 16 21:09:27 linux-acasa dbus[641]: [system] Rejected send message, 9 matched rules; type=“error”, sender=":1.114" (uid=0 pid=3150 comm="/usr/sbin/NetworkManager --no-daemon “) interface=”(unset)"
member="(unset)" error name=“org.freedesktop.DBus.Error.UnknownMethod” requested_reply=“0” destination=":1.113" (uid=0 pid=3141 comm="/usr/sbin/pppd nodetach lock nodefaultroute ipv6 ,")
sep 16 21:09:27 linux-acasa pppd[3141]: sif6addr: ioctl(SIOCSIFADDR): Permission denied (line 2624)
sep 16 21:09:27 linux-acasa pppd[3141]: cif6addr: ioctl(SIOCDIFADDR): No such address
sep 16 21:09:27 linux-acasa pppd[3141]: local IP address 62.231.66.192
sep 16 21:09:27 linux-acasa pppd[3141]: remote IP address 10.0.0.1
sep 16 21:09:27 linux-acasa pppd[3141]: primary DNS address 193.231.252.1
sep 16 21:09:27 linux-acasa pppd[3141]: secondary DNS address 213.154.124.1
sep 16 21:09:27 linux-acasa dbus[641]: [system] Rejected send message, 9 matched rules; type=“error”, sender=":1.114" (uid=0 pid=3150 comm="/usr/sbin/NetworkManager --no-daemon “) interface=”(unset)"
member="(unset)" error name=“org.freedesktop.DBus.Error.UnknownMethod” requested_reply=“0” destination=":1.113" (uid=0 pid=3141 comm="/usr/sbin/pppd nodetach lock nodefaultroute ipv6 ,")
sep 16 21:09:27 linux-acasa dbus[641]: [system] Rejected send message, 9 matched rules; type=“error”, sender=":1.114" (uid=0 pid=3150 comm="/usr/sbin/NetworkManager --no-daemon “) interface=”(unset)"
member="(unset)" error name=“org.freedesktop.DBus.Error.UnknownMethod” requested_reply=“0” destination=":1.113" (uid=0 pid=3141 comm="/usr/sbin/pppd nodetach lock nodefaultroute ipv6 ,")
sep 16 21:09:27 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 9 / phase ‘running’
sep 16 21:09:27 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): ip-up event
sep 16 21:09:27 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): sending IPv4 config to NetworkManager…
sep 16 21:09:28 linux-acasa pppoe[3159]: PADT: Generic-Error: RP-PPPoE: Child pppd process terminated
sep 16 21:09:28 linux-acasa pppd[3157]: Modem hangup
sep 16 21:09:28 linux-acasa pppd[3157]: Connect time 0.1 minutes.
sep 16 21:09:28 linux-acasa pppd[3157]: Sent 0 bytes, received 172 bytes.
sep 16 21:09:28 linux-acasa pppd[3157]: Connection terminated.
sep 16 21:09:28 linux-acasa pppd[3157]: Connect time 0.1 minutes.
sep 16 21:09:28 linux-acasa pppd[3157]: Sent 0 bytes, received 172 bytes.
sep 16 21:09:28 linux-acasa pppd[3157]: Script /usr/sbin/pppoe -I ‘enp2s0’ finished (pid 3159), status = 0x0
sep 16 21:09:28 linux-acasa pppd[3157]: Exit.
sep 16 21:09:28 linux-acasa NetworkManager[3150]: PADT: Generic-Error: RP-PPPoE: Child pppd process terminated
sep 16 21:09:28 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
sep 16 21:09:28 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
sep 16 21:09:28 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 11 / phase ‘disconnect’
sep 16 21:09:28 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 1 / phase ‘dead’
sep 16 21:09:28 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_exit_notify): cleaning up
sep 16 21:09:28 linux-acasa NetworkManager[3150]: <warn> pppd pid 3157 exited with error: A modem hung up the phone

#14

CONTINUATION

sep 16 21:09:29 linux-acasa NetworkManager[3150]: <info> pppd started with pid 3469
sep 16 21:09:29 linux-acasa pppd[3469]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:09:29 linux-acasa pppd[3469]: pppd 2.4.7 started by root, uid 0
sep 16 21:09:29 linux-acasa pppd[3469]: Using interface ppp1
sep 16 21:09:29 linux-acasa pppd[3469]: Connect: ppp1 <–> /dev/pts/2
sep 16 21:09:29 linux-acasa NetworkManager[3150]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
sep 16 21:09:29 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (plugin_init): initializing
sep 16 21:09:29 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase ‘serial connection’
sep 16 21:09:29 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
sep 16 21:09:32 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase ‘authenticate’
sep 16 21:09:32 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials…
sep 16 21:09:32 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager
sep 16 21:09:32 linux-acasa pppd[3469]: PAP authentication succeeded
sep 16 21:09:32 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
sep 16 21:09:32 linux-acasa pppd[3469]: sif6addr: ioctl(SIOCSIFADDR): Permission denied (line 2624)
sep 16 21:09:32 linux-acasa pppd[3469]: cif6addr: ioctl(SIOCDIFADDR): No such address
sep 16 21:09:32 linux-acasa pppd[3469]: local IP address 79.114.123.96
sep 16 21:09:32 linux-acasa pppd[3469]: remote IP address 10.0.0.1
sep 16 21:09:32 linux-acasa pppd[3469]: primary DNS address 193.231.252.1
sep 16 21:09:32 linux-acasa pppd[3469]: secondary DNS address 213.154.124.1
sep 16 21:09:32 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 9 / phase ‘running’
sep 16 21:09:32 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): ip-up event
sep 16 21:09:32 linux-acasa NetworkManager[3150]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): sending IPv4 config to NetworkManager…
sep 16 21:09:32 linux-acasa pppoe[3143]: PADT: Generic-Error: RP-PPPoE: Child pppd process terminated
sep 16 21:09:32 linux-acasa pppd[3141]: Modem hangup
sep 16 21:09:32 linux-acasa pppd[3141]: Connect time 0.1 minutes.
sep 16 21:09:32 linux-acasa pppd[3141]: Sent 0 bytes, received 4 bytes.
sep 16 21:09:32 linux-acasa pppd[3141]: Connection terminated.
sep 16 21:09:32 linux-acasa NetworkManager[759]: PADT: Generic-Error: RP-PPPoE: Child pppd process terminated
sep 16 21:09:32 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase ‘network’
sep 16 21:09:32 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase ‘establish’
sep 16 21:09:32 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 11 / phase ‘disconnect’
sep 16 21:09:32 linux-acasa dbus[641]: [system] Rejected send message, 9 matched rules; type=“error”, sender=":1.114" (uid=0 pid=3150 comm="/usr/sbin/NetworkManager --no-daemon “) interface=”(unset)"
member="(unset)" error name=“org.freedesktop.DBus.Error.UnknownMethod” requested_reply=“0” destination=":1.113" (uid=0 pid=3141 comm="/usr/sbin/pppd nodetach lock nodefaultroute ipv6 ,")
sep 16 21:09:32 linux-acasa dbus[641]: [system] Rejected send message, 9 matched rules; type=“error”, sender=":1.114" (uid=0 pid=3150 comm="/usr/sbin/NetworkManager --no-daemon “) interface=”(unset)"
member="(unset)" error name=“org.freedesktop.DBus.Error.UnknownMethod” requested_reply=“0” destination=":1.113" (uid=0 pid=3141 comm="/usr/sbin/pppd nodetach lock nodefaultroute ipv6 ,")
sep 16 21:09:32 linux-acasa dbus[641]: [system] Rejected send message, 9 matched rules; type=“error”, sender=":1.114" (uid=0 pid=3150 comm="/usr/sbin/NetworkManager --no-daemon “) interface=”(unset)"
member="(unset)" error name=“org.freedesktop.DBus.Error.UnknownMethod” requested_reply=“0” destination=":1.113" (uid=0 pid=3141 comm="/usr/sbin/pppd nodetach lock nodefaultroute ipv6 ,")
sep 16 21:09:32 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 1 / phase ‘dead’
sep 16 21:09:32 linux-acasa pppd[3141]: Script /usr/sbin/pppoe -I ‘enp2s0’ finished (pid 3143), status = 0x0
sep 16 21:09:32 linux-acasa pppd[3141]: Exit.
sep 16 21:09:32 linux-acasa NetworkManager[759]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_exit_notify): cleaning up

[FONT=monospace]

I manually disconnected, connected again, did not wok anymore.
Tried different MTUs, even to 1500, to no avail.
Restarted some times with 1500 and it works again.

[FONT=monospace]Here are some traceroutes:

    **linux-acasa:/home/tata #** traceroute tomshardware.com

traceroute to tomshardware.com (54.213.226.14), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 1.559 ms 1.584 ms 1.475 ms
2 * * *
3 xr01.frankfurt.rdsnet.ro (213.154.124.153) 24.230 ms 24.246 ms 24.119 ms
4 213-154-124-119.rdsnet.ro (213.154.124.119) 8.121 ms 8.094 ms 8.067 ms
5 ffm-bb1-link.telia.net (62.115.142.194) 43.695 ms ffm-bb2-link.telia.net (213.155.132.206) 35.482 ms bpt-b4-link.telia.net (213.248.83.189) 23.751 ms
6 nyk-bb1-link.telia.net (213.155.131.147) 132.178 ms win-bb2-link.telia.net (62.115.143.118) 22.536 ms prag-bb1-link.telia.net (213.155.137.36) 27.965 ms
7 las-b21-link.telia.net (213.155.135.155) 200.816 ms las-b21-link.telia.net (213.248.80.8) 196.785 ms ffm-bb2-link.telia.net (62.115.136.132) 35.982 ms
8 sjo-b21-link.telia.net (62.115.138.191) 230.608 ms nyk-bb2-link.telia.net (213.155.131.151) 129.278 ms sjo-b21-link.telia.net (62.115.138.193) 220.139 ms
9 las-b21-link.telia.net (213.248.80.8) 196.725 ms las-b3-link.telia.net (62.115.138.103) 211.135 ms 208.354 ms
10 las-b3-link.telia.net (213.155.131.75) 196.100 ms las-b3-link.telia.net (213.155.134.77) 212.166 ms sjo-b21-link.telia.net (213.155.135.187) 221.969 ms
11 las-b21-link.telia.net (62.115.137.37) 208.007 ms * las-b3-link.telia.net (62.115.138.101) 224.359 ms
12 a100-ic-300111-las-b3.c.telia.net (62.115.11.178) 206.858 ms * *
13 205.251.232.118 (205.251.232.118) 234.786 ms 219.573 ms 235.425 ms
14 205.251.232.118 (205.251.232.118) 237.380 ms * 205.251.232.116 (205.251.232.116) 225.170 ms
15 205.251.232.149 (205.251.232.149) 237.162 ms 205.251.232.118 (205.251.232.118) 223.715 ms 218.989 ms
16 205.251.232.255 (205.251.232.255) 223.841 ms 223.306 ms 205.251.232.149 (205.251.232.149) 226.567 ms
17 205.251.232.149 (205.251.232.149) 224.053 ms 205.251.232.167 (205.251.232.167) 217.345 ms 205.251.232.143 (205.251.232.143) 229.899 ms
18 * 54.239.48.177 (54.239.48.177) 225.873 ms *
19 * * ec2-54-213-226-14.us-west-2.compute.amazonaws.com (54.213.226.14) 209.352 ms

       **linux-acasa:/home/tata #** traceroute lwn.com

traceroute to lwn.com (5.22.149.135), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 1.646 ms 1.534 ms 1.471 ms
2 * * *
3 xr01.frankfurt.rdsnet.ro (213.154.124.153) 24.485 ms 24.433 ms 24.382 ms
4 decix2.ip.vsenet.de (80.81.193.100) 24.792 ms 24.846 ms 24.972 ms
5 xe-0-0-0.104.vs-r3.69.ip.vsenet.de (217.24.235.229) 27.962 ms 27.951 ms xe-0-0-0.105.vs-r3.69.ip.vsenet.de (217.24.235.247) 26.298 ms
6 xe-0-0-2.0.edge1.igb.de.skyway-dc.net (212.18.205.109) 27.972 ms 27.706 ms 27.874 ms
7 xe-1-1-1.53.core.igb.de.skyway-dc.net (78.109.59.82) 30.479 ms 30.474 ms 30.418 ms
8 78.109.58.44 (78.109.58.44) 30.855 ms 30.754 ms 30.857 ms
9 url-forwarding.moniker.com (5.22.149.135) 29.724 ms 28.907 ms 29.786 ms

       **linux-acasa:/home/tata #** traceroute opensuse.ro

traceroute to opensuse.ro (5.39.92.43), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 1.517 ms 1.418 ms 1.355 ms
2 * * *
3 xr01.frankfurt.rdsnet.ro (213.154.124.153) 22.913 ms 22.933 ms 22.998 ms
4 * * *
5 rbx-g2-a9.fr.eu (37.187.232.97) 32.185 ms rbx-g2-a9.fr.eu (91.121.128.88) 37.006 ms rbx-g2-a9.fr.eu (37.187.232.97) 33.736 ms
6 vss-9b-6k.routers.ovh.net (178.33.100.74) 57.485 ms 55.234 ms 55.023 ms
7 france.rackhosting.co (5.39.92.43) 33.275 ms 32.831 ms 32.789 ms[/FONT][/FONT]

#15

CONTINUATION

[FONT=monospace][FONT=monospace]linux-acasa:/home/tata # traceroute forums.opensuse.org
traceroute to forums.opensuse.org (130.57.66.6), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 1.279 ms 1.465 ms 1.759 ms
2 * * *
3 213-154-124-119.rdsnet.ro (213.154.124.119) 8.376 ms xr01.frankfurt.rdsnet.ro (213.154.124.153) 23.139 ms 213-154-124-119.rdsnet.ro (213.154.124.119) 8.417 ms
4 213-154-124-119.rdsnet.ro (213.154.124.119) 8.270 ms ffm-b2-link.telia.net (62.115.44.41) 37.111 ms 213-154-124-119.rdsnet.ro (213.154.124.119) 8.213 ms
5 bpt-b4-link.telia.net (213.248.83.189) 24.147 ms ffm-bb2-link.telia.net (80.91.246.218) 40.101 ms ffm-bb2-link.telia.net (62.115.138.82) 48.702 ms
6 prag-bb1-link.telia.net (80.91.250.163) 24.457 ms ffm-b12-link.telia.net (62.115.142.53) 42.340 ms ffm-b12-link.telia.net (62.115.142.39) 37.058 ms
7 be100.agr21.fra03.atlas.cogentco.com (130.117.14.89) 35.220 ms ffm-bb2-link.telia.net (62.115.134.214) 35.975 ms ffm-bb2-link.telia.net (62.115.139.227) 41.716 ms
8 ffm-b12-link.telia.net (62.115.140.15) 43.050 ms be2188.ccr42.fra03.atlas.cogentco.com (130.117.48.114) 35.292 ms ffm-b12-link.telia.net (62.115.142.53) 44.506 ms
9 be100.agr21.fra03.atlas.cogentco.com (130.117.14.89) 36.913 ms be2262.ccr42.ams03.atlas.cogentco.com (154.54.37.33) 44.971 ms 44.738 ms
10 be2182.ccr21.lpl01.atlas.cogentco.com (154.54.77.246) 61.443 ms 61.612 ms be2188.ccr42.fra03.atlas.cogentco.com (130.117.48.114) 37.178 ms
11 be2385.ccr22.ymq02.atlas.cogentco.com (154.54.44.141) 130.436 ms be2384.ccr21.ymq02.atlas.cogentco.com (154.54.44.137) 136.545 ms be2385.ccr22.ymq02.atlas.cogentco.com (154.54.44.141) 131.532 m
s
12 be2090.ccr21.yyz02.atlas.cogentco.com (154.54.30.205) 135.960 ms be2093.ccr22.yyz02.atlas.cogentco.com (154.54.44.105) 135.242 ms 135.270 ms
13 be2597.ccr22.cle04.atlas.cogentco.com (154.54.31.89) 138.473 ms be2596.ccr21.cle04.atlas.cogentco.com (154.54.31.53) 138.797 ms be2385.ccr22.ymq02.atlas.cogentco.com (154.54.44.141) 140.092 ms
14 be2351.ccr41.ord01.atlas.cogentco.com (154.54.44.85) 163.837 ms 164.352 ms 164.947 ms
15 be2597.ccr22.cle04.atlas.cogentco.com (154.54.31.89) 144.106 ms 149.916 ms be2596.ccr21.cle04.atlas.cogentco.com (154.54.31.53) 141.218 ms
16 38.104.103.50 (38.104.103.50) 145.906 ms be2351.ccr41.ord01.atlas.cogentco.com (154.54.44.85) 167.077 ms 38.104.103.50 (38.104.103.50) 146.000 ms
17 tg9-1.ar10.lsvlnv23.integra.net (209.63.100.146) 385.271 ms 372.788 ms be2217.ccr41.ord03.atlas.cogentco.com (154.54.24.206) 148.692 ms
18 38.104.103.50 (38.104.103.50) 151.641 ms 149.426 ms 151.152 ms
19 67.138.209.58 (67.138.209.58) 202.455 ms 202.310 ms 202.455 ms
20 tg9-1.ar10.lsvlnv23.integra.net (209.63.100.146) 249.691 ms 247.217 ms 242.869 ms
21 67.138.209.58 (67.138.209.58) 204.669 ms 192.94.118.230 (192.94.118.230) 216.027 ms 67.138.209.58 (67.138.209.58) 204.286 ms
22 192.94.118.247 (192.94.118.247) 215.278 ms 212.317 ms 212.059 ms
23 www.opensuse.org (130.57.66.6) 207.725 ms 192.94.118.230 (192.94.118.230) 216.721 ms 216.818 ms

   **linux-acasa:/home/tata #** traceroute okazii.ro

traceroute to okazii.ro (86.104.214.2), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 1.557 ms 1.471 ms 1.563 ms
2 * * *
3 dr22.bucuresti.rdsnet.ro (213.154.100.12) 22.257 ms dr22.bucuresti.rdsnet.ro (213.154.100.28) 16.851 ms dr22.bucuresti.rdsnet.ro (213.154.100.12) 22.333 ms
4 86-126-92-106.rdsnet.ro (86.126.92.106) 22.384 ms 22.230 ms 22.386 ms
5 xcr.netbridge.ro (195.246.243.253) 23.956 ms 23.452 ms 23.676 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

And last
linux-acasa:/home/tata # traceroute yahoo.com
traceroute to yahoo.com (206.190.36.45), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 1.661 ms 1.605 ms 1.566 ms
2 * * *
3 xr01.londra.rdsnet.ro (213.154.124.204) 35.695 ms xr01.frankfurt.rdsnet.ro (213.154.124.153) 23.098 ms 23.061 ms
4 ge-1-3-0.pat2.dee.yahoo.com (80.81.193.115) 35.045 ms 35.007 ms ge-1-1-0.pat1.the.yahoo.com (195.66.224.129) 36.152 ms
5 ge-3-1-0.pat1.tc2.yahoo.com (66.196.65.10) 56.152 ms 56.113 ms ae8.pat2.nyc.yahoo.com (66.196.65.15) 114.818 ms
6 ae8.pat1.nyc.yahoo.com (66.196.65.61) 116.043 ms 116.549 ms 109.760 ms
7 ae-7.pat2.che.yahoo.com (216.115.100.137) 152.694 ms ae-4.pat2.che.yahoo.com (216.115.101.145) 144.904 ms ae-8.pat1.dcp.yahoo.com (216.115.101.157) 125.097 ms
8 ae-4.pat1.che.yahoo.com (216.115.101.153) 158.345 ms ae-5.pat2.dnx.yahoo.com (216.115.96.55) 169.387 ms 169.961 ms
9 ae-8.pat2.dnx.yahoo.com (216.115.96.121) 169.089 ms ae-8.pat1.gqb.yahoo.com (216.115.96.122) 191.450 ms ae-5.pat1.dnx.yahoo.com (216.115.96.34) 187.648 ms
10 et-0-0-0.msr1.gq1.yahoo.com (66.196.67.97) 200.725 ms ae-8.pat2.gqb.yahoo.com (216.115.96.204) 195.425 ms ae-8.pat1.gqb.yahoo.com (216.115.96.122) 189.649 ms
11 et-0-0-0.clr2-a-gdc.gq1.yahoo.com (67.195.37.73) 179.742 ms et-19-1-0.msr1.gq1.yahoo.com (66.196.67.99) 198.461 ms et-18-1-0.msr2.gq1.yahoo.com (66.196.67.115) 200.761 ms
12 et-18-25.fab4-1-gdc.gq1.yahoo.com (98.137.31.178) 189.048 ms et-19-1-0.clr1-a-gdc.gq1.yahoo.com (67.195.37.95) 187.519 ms et-1-0-0.clr2-a-gdc.gq1.yahoo.com (67.195.37.97) 192.202 ms
13 po-10.bas2-7-prd.gq1.yahoo.com (206.190.32.31) 199.250 ms et-18-25.fab2-1-gdc.gq1.yahoo.com (98.137.31.170) 191.283 ms et-17-1.fab6-1-gdc.gq1.yahoo.com (98.137.31.184) 182.214 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *[/FONT] [/FONT]

#16

I’m pretty sure “auto” should be the default setting which probably means…

  • You’ve circled around to the beginning and the MTU setting shouldn’t be your issue
  • If you still see the problem in the future, you probably should consider something else.

IMO,
TSU

#17

While MTU doesn’t appear to be causing problems, the random disconnects (as shown in the journalctl output) are problematic. The service provider should be able to assist with this. Otherwise some packet inspection may be necessary to drill a bit deeper into the problem.

#18

On 2015-09-16 20:36, Ionel wrote:
>
> CONTINUATION

A comment.

Next time, just upload the log to susepaste.org or similar site, for a
limited time, then post the link here :slight_smile:

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#19

Sorry for spamming with data, i was just in a hurry to get the data posted before the thing stops working again …

I’m pretty sure “auto” should be the default setting which probably means…

  • You’ve circled around to the beginning and the MTU setting shouldn’t be your issue
  • If you still see the problem in the future, you probably should consider something else.

You might think it’s so but :

  • manually disconnecting and reconnecting with “auto” (ad nauseam) does not yield a working connection;
  • manually disconnecting and reconnecting with a different MTU each time will eventually lead to a working connection (for a while).

So it might no be the MTU but then what else ?

deano_ferrari

While MTU doesn’t appear to be causing problems, the random disconnects (as shown in the journalctl output) are problematic. The service provider should be able to assist with this. Otherwise some packet inspection may be necessary to drill a bit deeper into the problem.

I did random manual disconnects/reconnects.
Do you mean these or other ones, done by the system itself ?

PS
Nevermind the ISP … they don’t know how to solve it …
Last time i’ve had a broken cable somewhere in the ISP BOX (my network card lights were off).
Since my wife was using the PC, and she is not technically inclined, she did report to the ISP that there “was no signal”.
Needless to say, the “ISP person” instructed her to double click the “2 monitor icon” …
Wife did not know where the icon was … operator said in the lower right screen corner … where a clock lies …
Wife said there is only black space …
Operator was what ?
(We had Windows on the box, but the taskbar was vertical, on the left screen edge … and a black wallpaper …)
…
The whole thing took half an hour of WTF’s to finally decide to send a crew to investigate …

The crew had a blinking led signal tester … they had no idea what networking was about … they changed the cable tho …

Now, if all that happened WITH a Windows box …

So, if i can get help here, it will be REAL help. My ISP will just say it’s not his problem since i don’t use Windows and i have absolutely no way to prove that i’m not at fault.
Actually, my feeling is that my OS settings or software bugs are at fault so the ISP can’t help.

#20

Well, that’s confusing to me as to why that works.

I did random manual disconnects/reconnects.
Do you mean these or other ones, done by the system itself ?

Yes, I was assuming that the disconnects were unintentional, since that is what I thought you were trying to capture amongst other things.