1) The problem became again. Please fix
2) I did not received satisfaction in the last time. I expect, you'll return me money from previous time, and now again.
Beste antwoord door wizd3m
First of all, you are at risk for the Dirty CoW vulnerability using an older kernel. According to Debian GNU/Linux advisary any kernels older than the following are at risk:
- 3.16.36-1+deb8u2 for Debian 8
- 3.2.82-1 for Debian 7
- 4.7.8-1 for Debian unstable
So I advise you to upgrade your kernel before you experience any issue with Copy-on-Write. See https://dirtycow.ninja/
Furthermore. In your screenshots I cannot see where the server is located. And do you know for certain the issues do not arise on the remote network? The ping results are always from the outside in and not from your network to another place. As I would expect.
Then, In one of your posts you state the following:
physically problem locates between ethernet(or wifi) port inside YOUR DSL modem inside our apartment and your ipv4 gateway 184.108.40.206
That is a wrong assumption: 220.127.116.11 is NOT your gateway, but probably an IP adres of another customer. When you defined that IP adres as a gateway on your network (locally and remotely) than that could be the issue. Whenever that customer shuts down the modem, resets it or whatever, you will experience packetloss as the "gateway" is not reachable.
Depending on the service used by an ISP (PPPoE/PPPoA or whatever) a network could be defined very differently to a Local Network. ISPs usually depend on some kind of point-to-point protocol. Thus a gateway could be in the 10.x.x.x range, even when your public IP adres is like 82.x.x.x.
Another wrong assumption is that it is easy for an ISP to monitor 1 customer. Your modem is connected to a dslam which (for the sake of this argument) contains 200 customers. That dslam is connected to a single port on a switch on the ISP network. So all the network traffic for the 200 customers are on that one port. This also means that if there is packetloss on that port this should affect all 200 customers on the dslam including you. This also leads to the conclusion that it is not possible to monitor network traffic of 1 customer.
To conclude: As you did the assumption that 18.104.22.168 is your gateway and it is most likely that that IP adress has been assigned to another Tele2 customer, the issues you experience are (most probably) caused by you and not by Tele2.