That's the issue of the price of one's time. In some countries, the price of LHG5 equals to one hour of technician's work, in others it may equal to one month of technician's work.the only situation that I don't get timeout and the problem gets solve, is by disabling other clients on ISP radio device. So they suggest me to buy one more radio and make a PTP connection, but it cost a lot of price, I believe the problem is solvable so it's not worth to pay that much money for that, however, it's an option.
The voltage you gave is the AC one at the wall outlet, but there's an adaptor which makes 24 or alike DC from it, and this is what I was interested in.about cable and voltage, the cable length is 25 meter and voltage is 220-240
Have you/they tried to change the MAC address of your LHG 5?They say they already send a ticket to Mikrotik support team with needed config files, and they already did every suggestion that support team suggested but those didn't work.
Which seems to be related, other vendors may be prohibitively expensive or embargoed. And they don't support NV2 of course.The price is about 1 month of my brother income, So it's a lot.
...
the bad news is the Mikrotik is only brand which is accepted by my country ISPs.
If replacement of the whole device hasn't helped, it seems logical that replacing a MAC address will not help either.They already have connected me to another radio but problem still exist, we also tested both protocol, 802.11 and nv2, on both of ISP radios, but it didn't change anything. The solution that is mentioned before, also worked on the new destination radio(Disabling other clients). About changing MAC, they(ISP) said that they already had this problem with one of their customers and problem fixed by changing connection into PTP, So it means even changing MAC may not solve the problem.
ISP says because your connection is PTMP, we can't put on risk our security and give permissions to you, there is 3 other clients connected to destination radio. they say if I was PTP, they could give radios permission. ISP already made a ticket with Supout.files attached to it. Support team couldn't solve the problem yet. My situation is something like this:I do not understand because you are taking care of it,
who you do not even have all the permissions to read access and modify the configuration of the devices,
rather than requiring your ISP to take care of it.
This situation is absurd for me and, only for me of course, the hypothesis is that the ISP is nothing more than a guy who, without authorization, gives the connection "without putting much effort"...
The engine in my car don't work. Here's a picture of my seat. please help...
You told me that there is no way without full export, also you said that I have to change ISP and ask for a refund. both of these are impossible for me. We did everything we can to fix the problem. It's so frustrating to use the internet with that problem so I had to ask for help again. I'm ready to share any detail that I can see, also I'm ready to give access to my AP through Anydesk or Teamviewer.Ahhh, sorry, we wayt another YEAR for the no-reply...
On screenshot you are logged as admin....So ISP asked me to research about it.
They are ready to set any configuration I say to solve this problem because they have no idea what's the reason of this.
Thus I decided to ask you for help, I can provide any detail you want to solve this problem.
Those are my router's screenshots not AP, why I don't have to share my details when I can?On screenshot you are logged as admin....So ISP asked me to research about it.
They are ready to set any configuration I say to solve this problem because they have no idea what's the reason of this.
Thus I decided to ask you for help, I can provide any detail you want to solve this problem.
Any detail?
Full export...
The ISP doesn't do that. It has already shared those with Mikrotik support and they couldn't solve it. I wonder if there is a way to get extended logs.Ask the ISP to share the config of AP and CPE, on forum, so everyone can see if are problems.
If you do this already last year, probably the problem is gone already one year ago...
What am I supposed to do then?Log can be helpful for some problem, like 1% of the problems...
Starlink? In Iran? Not really likely in this decade...4) Change ISP, for example Starlink
RSTP (or any other flavor of STP) blocks forwarding of traffic on interfaces that just came online for a while, until a time during which an STP BPDU should arrive expires, to prevent L2 loops. So theoretically, if the wireless interface was going down briefly now and then, following each such event the forwarding would be interrupted for some time. But this time should be several times longer than 3-4 seconds, and you should see the wireless interface to be going down and up again even if the actual issue is at the "base station" at the ISP side.I've heard some people say there is something wrong with RSTP, how RSTP can cause problems in the PtMP network?
The second problem got solved by ISP specialist, but first problem still exist, I get weird and illogical latency spikes every few minutes.Finally, they gave me the Write access to my AP. I'm still unable to make Supout.rif
Thanks to the topic below, I just changed RSTP to STP and everything seems solved.
viewtopic.php?f=7&t=175574
I still have a few problems and need help with those.
1. I get some weird ping spikes.
2. I want to have access to my AP without turning my WAN port into LAN port on my Router.
What do you need?Again, picture without explanation is useless.
Now I'm doing it too so you understand what it means:
The solution to the problem is obvious, it's in the image, you can not see that???
The ping in Winbox, is ISP's AP MAC Address, the 192.168.2.1 is my home router which my PC has connected to it through LAN cable, and 95.80.184.185 is ISP's DNS address. Also the ping from my router to my CPE is <1 as well.For example, if the CPE have 192.168.3.1, what have you ARP pinged?, and the IP 192.168.2.1 what is?
Just for example.....
Do you have any suggestions for testing? Like what things should we try on the ISP network or AP?Ok, at this point, if the CPE can ping the AP consistently at 1ms, the problem is the rest of the provider's network ...
I agree with @rextended that it's the ISP who should solve this, however if you try /tool traceroute x.x.x.x rather than plain :ping x.x.x.x, it should show you at which network hop the jitter begins.Do you have any suggestions for testing? Like what things should we try on the ISP network or AP?