I haven’t seen anything specific to the format of these time tokens, but the firewall add-to-address-list timeout is documented here: http://wiki.mikrotik.com/wiki/Manual:IP … Properties…It seems to take the same format as any other similar duration-related input I’ve encountered:
a raw number is interpreted as seconds
You can specify a number as another duration with tokens:
s = seconds (default)
m = minutes
h = hours
d = days
w = weeks
A few aspects:
Tokens can combine be in any order
Whitespace is ignored
So these are all valid:
2s 2h 2w
1w2d3h4m5s
5s4m3h2d1w
Days and weeks just get added together. If you specify 1w8d, this is the same as 2w1d
The last value specified may be in h:m:s format or in h:m (omit seconds)
Interestingly, if you mix and match, they just get added:
“1d 2h 12:30” -> “1d 14:30:00”
Values larger than 536870911 seconds are stored and tracked but when displayed show as 0sec.
(248 days, 13:13:55)
The maximum value is 4294967295 seconds (which is the maximum 32-bit value)
This decodes to: 7101w3d6h28m15s as the largest value….
(7101 weeks is ~136 years counting for leap years, by the way)
Since WebSockets can run over a proxy server you could route any kind of binary traffic through them even in places that disallow non-web protocols or layer-7 inspect https traffic.
Wie viele Server braucht man bei Philips, um eine Glühbirne zu wechseln?
Apple macht das wohl ähnlich, hier dient ein AppleTV oder ein iPad als “Bridge zur Bridge”.
They’re at least honest — the icon of the cloud in the upper left prominently displays a “waiting” circle animation. I also notice the use of the word “looks” rather than “works” in the title, which is probably also accurate.
A bogon prefix is a route that should never appear in the Internet routing table. A packet routed over the public Internet (not including over VPNs or other tunnels) should never have a source address in a bogon range. These are commonly found as the source addresses of DDoS attacks.
The regular Bogon list is pretty static (last change in 2012), so I’ve listed the text version below. But the full Bogon list (including unused IPv4 space) is dynamic.
SFP+ interface compatibility settings with 1G links
For MikroTik devices with SFP+ interface that support both 10G and 1G link rate following settings are needed to be set on both linked devices for required interfaces. In order to get them working in 1G link rate.
auto-negotiation disabled
port speed 1G
FD
Devices which SFP+ ports support 1G links:
All SFP+ interfaces can be used in 1G mode if required:
Set the PCC selector from “both addresses and ports” to “both addresses”. This way communication from and to the same IP address always hashes the same and you don’t get broken connections.
The Wiert Corner - irregular stream of stuff 