We already made some IPsec fixes in v6.18rc3 which is available for testing upon request.

I upgraded one Omnitik from ROSv6.12, firmware 3.10, to ROSv6.17, firmware 3.17, wireless-fp enabled. I'm noticing port flapping. Omnitik is through ether1 connected to RB493G, which has ROSv5.26, firmware 3.07.
Auto Negotiation is enabled. Tx/RX Flow Control is off. In Advertise (10M half, 10M full, 100M half, 100M full,...) everything is checked. These are the default Mikrotik settings.

Are there some problems in the communication between these ROS versions?

We already made some IPsec fixes in v6.18rc3 which is available for testing upon request.

We already made some IPsec fixes in v6.18rc3 which is available for testing upon request.

I am interested, since we have major issues with reproducible issues and what seems to be random issues with IPsec.

We already made some IPsec fixes in v6.18rc3 which is available for testing upon request.

I am interested, since we have major issues with reproducible issues and what seems to be random issues with IPsec.

We have now added it to the regular download page:
http://www.mikrotik.com/download

see the signal i am getting in V1.7 how can i read the bars????

If you paste something from clipboard, the "y" sometime is unexpected and broken the rest of the pasted commands.

<...>

One simple example: on my maintenance script at the boot, if new bios version are available are updated and system rebooted before script go further, at reboot script continue (because are scheduled at the boot and the bios is already updated).

I do not want reply because if i do that I show my script, and I do not want disclose it to any.

I do not want reply because if i do that I show my script, and I do not want disclose it to any.

Then just describe basically what is that script of yours supposed to do (no specifics or actual code), and why would you (realistically) want to not have the reset be the last thing in there.

One simple example: on my maintenance script at the boot, if new bios version are available are updated and system rebooted before script go further, at reboot script continue (because are scheduled at the boot and the bios is already updated).

Reboot, reset... whatever...

You can easily wrap your copy&paste script into a scheduler even that is 1s away, and the first thing it does is to remove itself. That way, you're executing everything, and not even leaving a trail. This includes reboots, and I'm pretty sure it would work for a reset as well.

e.g.

Code: Select all

/system scheduler add name="SETTER" interval=1s on-event={
/system scheduler remove "SETTER"

/system reboot

}

or more generally

Code: Select all

/system scheduler add name="SETTER" interval=1s on-event={
/system scheduler remove "SETTER"

#Your script here

}

Technically, there's also the "execute" command, which doesn't involve adding a self removing item, but it requires the script as a string, meaning it's less convenient for the most part.

Another example is "toip" for convert one "1.2.3.4/32" as string toip not work, and toipprefix not exist,
must be used again another fantasious method instead to have toip working as expected:
http://forum.mikrotik.com/viewtopic.php ... 85#p438947

The language used for Scripting are mikrotik proprietary and I'm not expecting anything more what I can do, but I ask just for fix ALREADY existent functions, not add new, like decimal numbers or read more than 4096 characters on file.

While upgrading from v6.15 to v6.17.
IP / DHCP Server - Leases list is all gone .. (Leases list is removed)

RB2011UAS / RB2011UiAS / RB750GL / RB450G was all the same problem

For me it is a serious problem.

Monday tomorrow, we hope not only no problems at suppliers.

You keep on this type of statistic?

Is like you do not read the change log, or better, you do not understand the change log.

Read again and you find why.

While upgrading from v6.15 to v6.17.
IP / DHCP Server - Leases list is all gone .. (Leases list is removed)

RB2011UAS / RB2011UiAS / RB750GL / RB450G was all the same problem

error creating backup file: could not read all configuration files

While upgrading from v6.15 to v6.17.
IP / DHCP Server - Leases list is all gone .. (Leases list is removed)

RB2011UAS / RB2011UiAS / RB750GL / RB450G was all the same problem

For me it is a serious problem.

Monday tomorrow, we hope not only no problems at suppliers.

Are present static leases or only dynamic?

Simply put back from backup. Yu have backup, right?

Technically, there's also the "execute" command

execute "/system reboot"

You keep on this type of statistic?

Is like you do not read the change log, or better, you do not understand the change log.

Read again and you find why.

I read again and once more. And I can't find why.
May be, can you specify the reason?

Technically, there's also the "execute" command

perfect!

Code: Select all

execute "/system reboot"

does not ask for confirmation! so, to skip confirmation, one should replace '$command' with 'execute "$command"'

Have the same problem on 435G. Additionally, the list disappeared after accidental power failure. And when I try to make a backup:

Code: Select all

error creating backup file: could not read all configuration files

Apply (restore) previous backup over the existing configuration, then try to make a new backup.
Or reset the configuration first, and then apply previous backup.
That worked in my case.

But still now transparent web proxy doesn't work in both 6.15 & 6.17

New feature?
Watchdog timer is disabled, but the router still reboots on watchdog timer.

But still now transparent web proxy doesn't work in both 6.15 & 6.17

what exactly doesn't work? what do you check, what do you expect to see and what results do you actually see?

In version 6.15 I was not able to configure transparent web-proxy to show this login page: http://www.samplecomponents.com/scripts ... ll?hittite

You keep on this type of statistic?

Is like you do not read the change log, or better, you do not understand the change log.

Read again and you find why.

I read again and once more. And I can't find why.
May be, can you specify the reason?

Saving time each 10 min (?) on board

New feature?
Watchdog timer is disabled, but the router still reboots on watchdog timer.
And it does not wait for 10 minutes, and may restart in 30 seconds.

New feature?
Watchdog timer is disabled, but the router still reboots on watchdog timer.
And it does not wait for 10 minutes, and may restart in 30 seconds.

So what? It is a bug or a feature?

In version 6.15 I was not able to configure transparent web-proxy to show this login page: http://www.samplecomponents.com/scripts ... ll?hittite

what were your steps to do that? we're not telepathists. what do you mean saying 'to show this page'? all pages were opening normally, and that only page didn't work?

/ip proxy
set cache-administrator=it@test.com cache-on-disk=yes enabled=\
    yes max-cache-size=none max-fresh-time=1w
/ip proxy access
add action=deny comment="block telnet & spam e-mail relaying" disabled=yes \
    dst-port=23-25
add action=deny comment=\
    "allow CONNECT only to SSL ports 443 [https] and 563 [snews]" dst-port=\
    !443,563 method=CONNECT

But still now transparent web proxy doesn't work in both 6.15 & 6.17

what exactly doesn't work? what do you check, what do you expect to see and what results do you actually see?

and what about your Mangle rule? does it count packets?

I already answered a few posts above

ping watchdog is enabled by setting an IP address. remove IP address - ping watchdog will be disabled. watchdog-timer is about hardware watchdog

Cool, on some routers disapeared configuration after update. Firmwares more and more worse from version to version.

We have found some issue in mips-be that could fix your issue, Rudy. Please wait until tomorrow until we have something to test.

We have found some issue in mips-be that could fix your issue, Rudy. Please wait until tomorrow until we have something to test.

Well, let's see. But for the 'dead' units it will be too late. They have to be send back I'm afraid. There is no way I can login to these. Winbox nor Telnet 'sees' the units anymore. (I'm referring 2 grooves now. They both worked and only passed away after the remote upgrade fm 6.15 toward 6.17).
I still have to test 2 SXT's I believe, they are on their way to me..

We have found some issue in mips-be that could fix your issue, Rudy. Please wait until tomorrow until we have something to test.

Well, let's see. But for the 'dead' units it will be too late. They have to be send back I'm afraid. There is no way I can login to these. Winbox nor Telnet 'sees' the units anymore. (I'm referring 2 grooves now. They both worked and only passed away after the remote upgrade fm 6.15 toward 6.17).
I still have to test 2 SXT's I believe, they are on their way to me..

Netinstall should be able to revive them. If not, maybe you have some other issue with them

I still upgrade all my devices with last 3.17/3.18 BIOS and RouterOS 6.17,
I'm doing that from the day is out,
NO ONE SINGLE PROBLEM,
I'm a WISP and I have updated/upgraded almost 400 mipsbe devices and 10 ppc (RB1xxx) without any problem.

I have near all models on production environment, from RB411 to QRT-5,
the only devices I do not have are mipsle and tilera models.

When you update/upgrade the board, can you add watchdog?

>>>...It is just not able to reach by any telnet or winbox session...<<<

And by MAC telnet on winbox -> AP -> ip/neighbors list?

>>>...It is just not able to reach by any telnet or winbox session...<<<

And by MAC telnet on winbox -> AP -> ip/neighbors list?

I tried from AP side; mac-ping... no reply, ping.... no reply, mac telnet... disconnected, telnet ... no reply,
Then we tried with laptop from ethernet end. (By technician that doesn't know as much as me...) But winbox doesn't even 'see' it. We tried to contact it to its default ethernet IP address (after setting laptop to manual IP in same network) but no reply neither.
Laptop was also not getting IP address from CPE dhcp-server on the lan.
But symbols and lights on devices do notice the connection.

Later on my desk tried all the same from the ethernet end, no way.... just no response whatsoever, even not after 20 mins. (sometimes we have troubled units that only come up after long, long time..)

I didn't try via neighbor list from AP's end when unit was still 'visible' in the reg list but not responding. Since a power cycle mostly helps with 'stalled' radios, the standard is to do a power cycle first. Usually it solves the issue, but now it just stayed completely inaccessible. Off course it was too late than for the neighbor method.

Changing profiles in quickset you get a warning that you could loose connectivity, no matter what i answer it just pops back to my original quickset profile.

Running Chromes and windows 7.