30 May
2017
30 May
'17
7:55 a.m.
I'm sorry, Ronen, I'm not an expert with MikroTik. I have no
actual experience with one. (I do own one but I've never put
it into service.)
I don't think you should downgrade the firmware back to the old
version. I really doubt that was the cause of any of the problems
you are experiencing.
I don't think you should go back to routing through old amprgw
because it's going to go away in a few days (I don't yet know
exactly when) and you would be disconnected as a result.
The strange things going on with your router are not causing problems
for anyone, so don't feel that you need to shut down because of them.
It would be nice if you could find the cause and fix it but it is not
urgent.
Please don't give up. It's mostly working.
- Brian
On Tue, May 30, 2017 at 11:41:03AM +0000, R P wrote:
> Dear Brian (and all other experts )
>
> I really dont know where the problem is
>
> I have shut down the router for two hours and indeed no errors appeared
>
> I dont notice any connection problem so from my point of view no problem that i
can search for
>
> The only two changes i have done the last few days were
>
> 1) routing my outbound traffic to the new GW address (that required creating
additional tunnel to the new address )
>
> 2) upgrading the router firmware from 6.34.4 to 6.39.1
>
> I will try first to return the system to route only to old AMPRGW and later try
to downgrade the firmware to what it was before (6.34.4)
>
> I have no NAT enabled (i thought it was NAT related) and have no 169.228.66.251
address definition beside in the tunnel definition as "tunnel remote address"
and the 192.168.1.180 is my router local net IP and the "tunnel local address"
>
> I have keep alive in the tunnel turned on and it is every 10 seconds so if there is a
correlation between the error rate and the keep alive maybe its a clue (is keep alive
mechanism is only headers ?) i will change it to see if the errors will drop so maybe i
have a clue
>
> I have made yesterday a firewall rule to catch every outbound traffic with
169.228.66.251 source address and even no one packet was logged for the whole night
>
> definitely it is for me a "school" ....
>
>
> Im open for any suggestions ...
>
> If I give up (not so quick) and the situation will stay as it is it hope you will not
be angry with me as my gateway makes some noise in the up-going stream path
>
> Regards
>
> Ronen - 4Z4ZQ
>
>
>
>
> ________________________________
>
> I have no explanation for why these things are occuring.
> - Brian
>
>
>