On 4/19/23 13:31, Carlos E. R. wrote:
On 2023-04-19 21:37, Lew Wolfgang wrote:
On 4/19/23 12:06, Carlos E. R. wrote:
If the router change caused the problem, the culprit is the router, period. I don't have to test anything else, but I did.
It sure looks like it's the router somehow.
I know the answer to this question, but I'll ask it anyway. Do you have to use their router? Can you purchase and use your own? I know, probably not.
Regulation say yes, but the ISP does not publish the configuration needed, and it is complex. You have to reverse engineer it.
I wonder, since there's a regulation, if you could buy your own router then have your ISP come out and configure it for you?
In times of ADSL, I bought a router, and it had a menu to choose which ISP to configure for. So it was easy. I have not seen routers for fibre announcing this feature.
Did you ping the router from Legolas when it was directly connected?
Trying now. Good idea. [...] Yes, there are some losses, using WiFi.
Those Wifi losses seem a bit high, I'll have to try that here.
cer@Legolas:~> while sleep 1 ; do DATE=`date --iso=s` ; echo -n "$DATE " ; /usr/sbin/fping -c 100 --quiet router ; done 2023-04-19T22:02:46+02:00 router : xmt/rcv/%loss = 100/95/5%, min/avg/max = 2.73/5.06/30.4 2023-04-19T22:04:27+02:00 router : xmt/rcv/%loss = 100/97/3%, min/avg/max = 2.61/4.82/34.8 2023-04-19T22:06:08+02:00 router : xmt/rcv/%loss = 100/100/0%, min/avg/max = 2.15/7.35/112 2023-04-19T22:07:48+02:00 router : xmt/rcv/%loss = 100/100/0%, min/avg/max = 2.71/4.27/38.6 2023-04-19T22:09:29+02:00 ^Crouter : xmt/rcv/%loss = 2/2/0%, min/avg/max = 3.47/3.79/4.12 ^C cer@Legolas:~>
Small loses, AFAIK the problem is router ←→ SW2. Notice the strangeness that SW1 is in the middle, but pings from a machine connected on SW1 pinging the router seem not to be affected (recollection say they were affected when the technician looked).
Connecting the cable now. Nah, I have to also reset NM for the cable to work.
No loses:
cer@Legolas:~> while sleep 1 ; do DATE=`date --iso=s` ; echo -n "$DATE " ; /usr/sbin/fping -c 100 --quiet router ; done 2023-04-19T22:15:04+02:00 router : xmt/rcv/%loss = 100/100/0%, min/avg/max = 0.34/0.62/2.66 2023-04-19T22:16:44+02:00 router : xmt/rcv/%loss = 100/100/0%, min/avg/max = 0.32/0.62/7.95 2023-04-19T22:18:24+02:00 router : xmt/rcv/%loss = 100/100/0%, min/avg/max = 0.35/1.35/31.4 2023-04-19T22:20:04+02:00 ^Crouter : xmt/rcv/%loss = 2/2/0%, min/avg/max = 0.62/0.62/0.62 ^C cer@Legolas:~>
So could the problem be the connection between sw1 and sw2?
Did you try looking at the connection specifics with ethtool when Legolas was connected directly to the router? Was the connection full-duplex at the expected speed? I doubt if that's the problem, but I have seen surprises when using ethtool.
Ok, can try later, now it is connected on WiFi. [...] Legolas:~ # ethtool -I eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on master-slave cfg: preferred slave master-slave status: slave Port: Twisted Pair PHYAD: 0 Transceiver: external MDI-X: Unknown Supports Wake-on: pumbg Wake-on: d Link detected: yes Legolas:~ #
That all seems okay.
Can you replace sw1 with your own router/firewall?
sw1 is my own switch, 8 eth sockets. It is the router which I can not replace.
SW1 is my older switch; I had it on the computer room, eventually realized 8 mouths were not enough, so got another one with 16, and SW1 went downstairs, close to the router.
Ok, connecting now "Legolas" to SW1 and trying pinging the router. I have to wait 5 minutes.
1 2 router-----sw1------sw2-----telcontar \ \-----isengard \Legolas
No loses:
cer@Legolas:~> while sleep 1 ; do DATE=`date --iso=s` ; echo -n "$DATE " ; /usr/sbin/fping -c 100 --quiet router ; done 2023-04-19T22:24:52+02:00 router : xmt/rcv/%loss = 100/100/0%, min/avg/max = 2.97/4.58/29.8 2023-04-19T22:26:32+02:00 router : xmt/rcv/%loss = 100/100/0%, min/avg/max = 2.98/4.01/24.1 2023-04-19T22:28:12+02:00 router : xmt/rcv/%loss = 100/100/0%, min/avg/max = 2.92/4.41/28.6 2023-04-19T22:29:52+02:00 ^Crouter : xmt/rcv/%loss = 8/8/0%, min/avg/max = 3.01/3.38/3.81 ^C cer@Legolas:~>
The problems are only on machines on the computer room connected to SW2 and going to the router and internet.
Strange, it's a real mystery. Regards, Lew