So it was a detox of a kind, OK. With this Covid and alike, I was scared you shifted to JuniperI needed to take a break, I found out that I was spending way too much time here.
Yes. This indicates that the media converter is not advertising the gigabit speed at its copper Ethernet side.for now I just wanted to be sure that the "Link Partner Advertising" is what the Mikrotik device is seeing from the node and that's why The options are grayed out.
Two possible explanations come to my mind:in my case i can't see ESP in the connection tracking , not sure why
The idea of sniffing is to see whether the throughput is limited by delays between packets or by losses and subsequent retransmissions. So you should sniff the test TCP session and then use Wireshark to look for anomalies.what do I have to sniff?
At both ends, use /ip firewall connection print detail where protocol~"esp" before and after doing the pppoe cycle, look for differences between "before" and "after" state.Any idea?
In previous 7.1rcX, adding verbose to the export used to make it work - have you tried that?Export started at oct/12/2021 10:40:20 by RouterOS 7.1rc4, and it's been stuck on this for 14 minutes so far
A post on the forum is not sufficient for this. You have to open a support ticket. Officially, it should even be raised via your reseller. But it can only succeed if the switch chip used supports such functionality.Developers need to read this post and respond plz
@iegg, please have a look at this post and tell me whether it helps remove some of that confusion.I really wish Mikrotik wouldn't have chosen the name bridge for the switch-like grouping of ports AND for the Layer 3 (CPU-Port) capabilities. It is very confusing.
So to contribute - if I remember right, I had this problem when CHR was at one end and RB1000AHx4 at the other one.Meanwhile I opened a case with Mikrotik and I sent this thread... let's see what happen