Community discussions

 
msatter
Member Candidate
Member Candidate
Posts: 133
Joined: Tue Feb 18, 2014 1:56 am
Reputation: 1
Location: Netherlands

Re: v6.39rc [release candidate] is released

Fri Feb 03, 2017 1:19 am

Chupaka wrote:
msatter wrote:
but not in script until I do a print again.

indices were never meant to be used without 'print'. correct form is the following:
:put [/ip ipsec remote-peers get [find where something=blabla] remote-address];


Thanks, however in that part there seems nothing can be found to hook with "find where" so I looked again into printing. I am now issuing now "/ip ipsec remote-peers print value-list;" before the line.
 
pe1chl
Forum Guru
Forum Guru
Posts: 2140
Joined: Mon Jun 08, 2015 12:09 pm
Reputation: 31

Re: v6.39rc [release candidate] is released

Fri Feb 03, 2017 1:27 am

BartoszP wrote:
pe1chl wrote:
This is normal when you do not pay special attention to the firewall.
The IPsec config is only a shortcut to IPsec to setup a Peer and Policy for GRE traffic, but as long as the...
So, make sure your firewall entries are correct. Like:
add action=accept chain=input ipsec-policy=in,ipsec protocol=gre

I do not understand. It is obvious that there should be proper firewall set of rules to pass GRE and IPSec connection but what is such firewall rule for? How it deals with password?
I assume that I am assigning IPs to secured connection so I assume that addresses are assigned not to pure GRE but to IPSec over GRE so if there is no matching password pair then the IPSec should not be established = no traffic from side to side.
I'm expecting sending data over encrypted tunnel not over simple GRE which carries IPSec traffic.
More, if I have no such rule then there should be no chance to make secured connection so traffic should be blocked.

You expect a lot, but it does not work like that!
IPsec policies define what traffic is encrypted and all traffic that does not match the policies is simply sent unencrypted.
As the policies are dynamically generated (first a phase1 association with the peer as defined in the tunnel interface setup and
then a phase2 policy generated from there), in case the IPsec is not defined at both ends there simply is no encryption.
Many examples for using firewall entries for tunnel over IPsec for MikroTik are simply incorrect. E.g. for GRE/IPsec they list
that protocol 47 is to be allowed, for L2TP/IPsec they list that UDP port 1702 is to be allowed. That is simply wrong, the
extra qualifier ipsec-policy=in,ipsec as mentioned above should be present for those allow rules or else unencrypted traffic
for that protocol will be allowed as well! When you would not allow plain incoming GRE traffic the connection would not
be established. And when you are very worried about sending unencrypted traffic, probably you should also use output
rules to drop GRE traffic when not ipsec-policy=out,ipsec ...
 
colanderman
newbie
Posts: 31
Joined: Wed Oct 28, 2015 6:21 am
Reputation: 3

Re: v6.39rc [release candidate] is released

Fri Feb 03, 2017 2:06 am

strods wrote:
colanderman - Before you connect to router go to Tools/Clear Cache on Winbox loader and try to test this afterwards.

Oh sorry! I mean in webfig, not winbox.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 7619
Joined: Mon Jun 19, 2006 11:15 pm
Reputation: 35
Location: Home Network Ltd., Minsk, Belarus
Contact:

Re: v6.39rc [release candidate] is released

Fri Feb 03, 2017 2:26 pm

msatter wrote:
Chupaka wrote:
msatter wrote:
but not in script until I do a print again.

indices were never meant to be used without 'print'. correct form is the following:
:put [/ip ipsec remote-peers get [find where something=blabla] remote-address];


Thanks, however in that part there seems nothing can be found to hook with "find where" so I looked again into printing. I am now issuing now "/ip ipsec remote-peers print value-list;" before the line.

If there's only one peer, then just use [find], without 'where' part
Russian-speaking forum: http://forum.mikrotik.by. Welcome :)

For every complex problem, there is a solution that is simple, neat, and wrong.

¡ɹǝ|SOɹǝʇnoɹ ʞıʇoɹʞıW ɯ‚|

MikroTik. Your life. Your routing.
 
parham
just joined
Posts: 10
Joined: Mon Feb 16, 2015 12:35 am
Reputation: 0

Re: v6.39rc [release candidate] is released

Fri Feb 03, 2017 3:16 pm

In iPad Safari terminal tab seems ok but won't bring the keyboard up. with out the keyboard can't do anything.
 
msatter
Member Candidate
Member Candidate
Posts: 133
Joined: Tue Feb 18, 2014 1:56 am
Reputation: 1
Location: Netherlands

Re: v6.39rc [release candidate] is released

Fri Feb 03, 2017 3:32 pm

Chupaka wrote:
msatter wrote:
Chupaka wrote:
msatter wrote:
but not in script until I do a print again.

indices were never meant to be used without 'print'. correct form is the following:
:put [/ip ipsec remote-peers get [find where something=blabla] remote-address];


Thanks, however in that part there seems nothing can be found to hook with "find where" so I looked again into printing. I am now issuing now "/ip ipsec remote-peers print value-list;" before the line.

If there's only one peer, then just use [find], without 'where' part


Indeed that works and there is a problem is when the first IPSEC connect did not work and you had to reconnect. Then there are more connections active of which the invalid ones will timeout eventually. Only one remote-dynamic-address isn't working and I get than an error that the template is invalid.

So I get then as message "invalid internal item number" so I will stick with the "print value-list" and then I can check each line.
:put /ip ipsec remote-peers> :put [/ip ipsec remote-peers get [find] remote-address ];
invalid internal item number


Thanks again for the help on this.
 
BartoszP
Forum Veteran
Forum Veteran
Posts: 826
Joined: Mon Jun 16, 2014 1:13 pm
Reputation: 60
Location: Poland, 43-300

Re: v6.39rc [release candidate] is released

Fri Feb 03, 2017 6:28 pm

pe1chl wrote:
...You expect a lot, but it does not work like that!....
IPsec policies define what traffic is encrypted and all traffic that does not match the policies is simply sent unencrypted. ....


Thank you for long explanation but I expect, seems that I am wrong at this point, that If I specify passwords, the tunnel will not pass traffic if there is no match of password for both ends. Traffic should not be carried without encryption despite the method of generating policies.
It is safer to feed my Reputation than bears in the ZOO.
 
pe1chl
Forum Guru
Forum Guru
Posts: 2140
Joined: Mon Jun 08, 2015 12:09 pm
Reputation: 31

Re: v6.39rc [release candidate] is released

Fri Feb 03, 2017 7:55 pm

With the proper firewall entries at both ends that would be true.
Put this in your input chain at both sides BEFORE the Established/Related entry.
/ip firewall filter
add action=reject chain=input comment="reject unprotected GRE" ipsec-policy=in,none protocol=gre reject-with=icmp-admin-prohibited
 
w32pamela
newbie
Posts: 49
Joined: Fri Jul 12, 2013 4:22 pm
Reputation: 2

Re: v6.39rc [release candidate] is released

Sat Feb 04, 2017 5:56 pm

colanderman wrote:
strods wrote:
colanderman - Before you connect to router go to Tools/Clear Cache on Winbox loader and try to test this afterwards.

Oh sorry! I mean in webfig, not winbox.

Just to echo colanderman, Frequency Mode, Country & Antenna Gain are missing from webfig Wireless details in Advanced Mode. This problem is present in v6.38 and continues in v6.39RC. If I open Winbox and go to wireless advanced mode before I open Webfig then they appear.

The Terminal button does not bring up a functional terminal window in Chrome, Firefox, or IE with Windows 10. All I get is white window without a cursor.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 661
Joined: Wed Jul 16, 2014 7:22 am
Reputation: 23
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Tue Feb 07, 2017 11:58 am

Version 6.39rc26 has been released.

Changes since previous version:
*) dhcp - do not listen on IPv4/IPv6 client to IPv6 MLD packets;
*) email - check for errors during SMTP exchange process;
*) hotspot - added access to HTTP headers using $(http-header-name);
*) ike1 - added more Radius accounting attributes - "event-timestamp", "acct-session-id", "acct-authentic", "acct-session-time";
*) ipsec - do not require "sa-dst-address" if "action=none" or "action=discard";
*) ipsec - fixed "mode-cfg" verbose export;
*) log - added tr069 topic;
*) tr069-client - added traceroute diagnostics support;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
There is no shame in not knowing something:
http://wiki.mikrotik.com/wiki/Tips_and_ ... f_RouterOS
 
me9
just joined
Posts: 2
Joined: Tue Feb 07, 2017 1:39 pm
Reputation: 0

Re: v6.39rc [release candidate] is released

Tue Feb 07, 2017 2:06 pm

Version 6.39rc26 has been released.
Hi.
rb750gr3
Image
Image
 
anuser
Frequent Visitor
Frequent Visitor
Posts: 77
Joined: Sat Nov 29, 2014 8:27 pm
Reputation: 3

Re: v6.39rc [release candidate] is released

Wed Feb 08, 2017 1:24 pm

- WAP AC 6.39rc26
- users reported that their clients get disconnected randomely
- I watched caps,info logging and found concurrent "disconnected, group key timeout" messages for multiple clients running on 2.4Ghz,
i.e. 5 clients (e.g. with different MAC addresses starting with: 3CE072, F48E92, E0DB10, 64CC2E,5CF7:E6) get dropped at once in this case. I do not know whether this is the reason for this problem...

- Note: This seems to be only on WAP AC devices with serial number starting with 711E06..... (with MAC address starting with 6C:3B:6B) I bought 10 of those last week. On older devices with serial number 65710/69A50/6CBA06 no problems have been reported so far.
 
uldis
MikroTik Support
MikroTik Support
Posts: 3127
Joined: Mon May 31, 2004 2:55 pm
Reputation: 24

Re: v6.39rc [release candidate] is released

Wed Feb 08, 2017 2:20 pm

anuser wrote:
- WAP AC 6.39rc26
- users reported that their clients get disconnected randomely
- I watched caps,info logging and found concurrent "disconnected, group key timeout" messages for multiple clients running on 2.4Ghz,
i.e. 5 clients (e.g. with different MAC addresses starting with: 3CE072, F48E92, E0DB10, 64CC2E,5CF7:E6) get dropped at once in this case. I do not know whether this is the reason for this problem...

- Note: This seems to be only on WAP AC devices with serial number starting with 711E06..... (with MAC address starting with 6C:3B:6B) I bought 10 of those last week. On older devices with serial number 65710/69A50/6CBA06 no problems have been reported so far.


Could you please write to support@mikrotik.com with the exact SN that experience this problem?
Also if possible maybe you could make a support output file on the wAP ac when this problem happens?
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 661
Joined: Wed Jul 16, 2014 7:22 am
Reputation: 23
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Thu Feb 09, 2017 3:03 pm

Version 6.39rc27 has been released.

Changes since previous version:
*) dhcp-client - added "script" option which executes script on state changes (CLI only);
*) firewall - do not allow to set "time" parameter to 0s for "limit" option;
*) ike2 - always replace empty TSi with configured address if it is available;
*) ipsec - fixed "/ip ipsec policy group export verbose";
*) lte - fixed "/interface lte info X once";
*) ppp-client - added support for Datacard 750UL and DWR-730;
*) snmp - added SSID to CAPsMAN registration table;
*) snmp - improved response speed when multiple requests are received within short period of time;
*) userman - allow access to User Manager users page only through "/user" URL;
*) webfig - improved field layout;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
There is no shame in not knowing something:
http://wiki.mikrotik.com/wiki/Tips_and_ ... f_RouterOS
 
andriys
Forum Veteran
Forum Veteran
Posts: 700
Joined: Thu Nov 24, 2011 2:59 pm
Reputation: 23
Location: Kharkiv, Ukraine

Re: v6.39rc [release candidate] is released

Thu Feb 09, 2017 4:18 pm

strods wrote:
*) dhcp-client - added "script" option which executes script on state changes (CLI only);

Yay!!!
 
alexjhart
Member Candidate
Member Candidate
Posts: 155
Joined: Thu Jan 20, 2011 9:03 pm
Reputation: 8

Re: v6.39rc [release candidate] is released

Fri Feb 10, 2017 2:08 am

strods wrote:
*) dhcp-client - added "script" option which executes script on state changes (CLI only);

cool. now I can react to lease instead of scheduling script to do ddns, address-lists, etc. ? :)

strods wrote:
*) snmp - added SSID to CAPsMAN registration table;


Didn't know this was in the works. Looked through release notes. Happy to see it though!
Looks like minor bug though:
`/caps-man registration-table print oid` reports 1.3.6.1.4.1.14988.1.1.1.4.1...
but snmpwalk shows that it is really 1.3.6.1.4.1.14988.1.1.1.5.1...
-----
Alex Hart

The Brothers WISP
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6573
Joined: Thu Mar 31, 2005 3:33 pm
Reputation: 19
Location: Riga, Latvia
Contact:

Re: v6.39rc [release candidate] is released

Fri Feb 10, 2017 12:07 pm

Thank you very much for the report about capsman oid values.
 
User avatar
jaxx
just joined
Posts: 11
Joined: Thu Jun 25, 2009 5:16 pm
Reputation: 0
Location: Paris, France
Contact:

Re: v6.39rc [release candidate] is released

Fri Feb 10, 2017 7:46 pm

Hi everyone,

I don't post that often, but since 6.38 (now .1 ) (I believe, as I don't recall having the issue before) my CRS is acting very bad, actually, waking me up at night sometimes.
It manages to restart on it's own, but crashes hard enough to leave the remote side of an SFP+ in a bad state (Mellanox cards get over it fine, but I have an Intel Dual AF DA card that never manages to reset itself, (even an ifdown&&rmmod&&modprobe&&ifup doesn't do a thing, needing a warm reboot of the server))... Since this switch is core of my home network, including my ISPs GPON access on a vlan, the good old unbreakable (besides it's PSU) RB1100AH doesn't get along that much neither, sticking DHCP in a "searching" state until I renew manually.
In contrast, when I reboot the switch intentionally, from the CLI or Winbox: everything connected device reacts perfectly fine

I see in the changelog stability improvements for MMIPS, any chance you fixed some stuff on MIPSBE as well ?
Are RCes safe enough to give it a try (afterall it's "just" home, not my real workplace)
Or, what downgrade paths can I go through? seeing many changes on 6.38.x is it even possible ?

Supout.rif doesn't seem to give anything, and it's generated after the crash anyways, but I hooked up a console port and got some non consistent stack traces:

grabserial with timestamping:
# grabserial -T -b 115200 -d /dev/ttyUSB0 -v
Opening serial port /dev/ttyUSB0
115200:8N1:xonxoff=0:rtscts=0
Printing absolute timing information for each line
Use Control-C to stop...


[18:14:36.570195 0.000002] -=< Watchdog IRQ >=-
[18:14:36.593493 0.031310] Call Trace:
[18:14:36.593796 0.000305] <4>{c3ee1ae0} dump_stack+0x8/0x30
[18:14:36.594533 0.000736] <4>{c3ee1ba8} 0xc32742d8 [music_dog@0xc3274000]
[18:14:36.595548 0.001016] <4>{c3ee1bc0} handle_irq_event_percpu+0x64/0x25c
[18:14:36.596584 0.001036] <4>{c3ee1c00} handle_irq_event+0x38/0x68
[18:14:36.597481 0.000897] <4>{c3ee1c18} handle_level_irq+0xc8/0xe8
[18:14:36.598352 0.000871] <4>{c3ee1c30} generic_handle_irq+0x28/0x44
[18:14:36.599264 0.000912] <4>{c3ee1c48} do_IRQ+0xb0/0xc0
[18:14:36.599940 0.000676] <4>{c3ee1c60} music_irq_dispatch+0x50/0x7c
[18:14:36.600867 0.000927] <4>{c3ee1c88} handle_irq_event_percpu+0x64/0x25c
[18:14:36.601928 0.001061] <4>{c3ee1cc8} handle_percpu_irq+0x54/0x84
[18:14:36.602837 0.000909] <4>{c3ee1ce8} generic_handle_irq+0x28/0x44
[18:14:36.603763 0.000927] <4>{c3ee1d00} do_IRQ+0xb0/0xc0
[18:14:36.604461 0.000697] <4>{c3ee1d18} ret_from_irq+0x0/0x4
[18:14:36.605211 0.000750] <4>more trace (sp:c3ee1d80):
[18:14:36.605854 0.000643] <4>{c3ee1d80} addrlist_get_list+0x128/0x1f4 [packet_hook@0xc3000000]
[18:14:36.607333 0.001479] <4>{c3ee1dc0} 0xc24f0118 [music_gmac@0xc24f0000]
[18:14:36.608369 0.001036] <4>{c3ee1de8} 0xc24f0560 [music_gmac@0xc24f0000]
[18:14:36.609411 0.001042] <4>{c3ee1e28} 0xc24f2688 [music_gmac@0xc24f0000]
[18:14:36.610452 0.001041] <4>{c3ee1e68} process_one_work+0x2dc/0x484
[18:14:36.611412 0.000960] <4>{c3ee1ea0} worker_thread+0x23c/0x3e0
[18:14:36.612329 0.000917] <4>{c3ee1ee0} kthread+0x88/0x90
[18:14:36.613784 0.001455] <4>{c3ee1f18} kernel_thread_helper+0x10/0x18
[18:14:36.619372 0.005588] <4>
[18:14:39.089481 2.470104]
[18:14:39.089613 0.000136]
[18:14:39.089665 0.000053] RouterBOOT booter 3.22
[18:14:39.090193 0.000528]
[18:14:39.090243 0.000050] CRS226-24G-2S+
[18:14:39.092686 0.002442]
[18:14:39.092739 0.000054] CPU frequency: 400 MHz
[18:14:39.095527 0.002787]   Memory size:  64 MiB
[18:14:39.100394 0.004867]     NAND size: 128 MiB
[18:14:39.209472 0.109074]
[18:14:39.209592 0.000124] Press any key within 2 seconds to enter setup..
[18:14:41.241416 2.031820]
[18:14:41.241529 0.000118] loading kernel from nand... OK
[18:14:43.523657 2.282122] setting up elf image... OK
[18:14:43.664576 0.140921] jumping to kernel code
[18:14:47.950500 4.285923] Starting...
[18:14:59.544603 11.594102] Starting services...
[18:15:16.490655 16.946053]



[18:15:16.493766 0.003115] mtk-core-switch Login: -=< Watchdog IRQ >=-
[18:37:36.215519 1339.721749] Call Trace:
[18:37:36.218042 0.002527] <4>{c3ee1ad8} dump_stack+0x8/0x30
[18:37:36.221096 0.003054] <4>{c3ee1ba0} 0xc32882d8 [music_dog@0xc3288000]
[18:37:36.224452 0.003357] <4>{c3ee1bb8} handle_irq_event_percpu+0x64/0x25c
[18:37:36.229146 0.004694] <4>{c3ee1bf8} handle_irq_event+0x38/0x68
[18:37:36.232361 0.003215] <4>{c3ee1c10} handle_level_irq+0xc8/0xe8
[18:37:36.235556 0.003194] <4>{c3ee1c28} generic_handle_irq+0x28/0x44
[18:37:36.241172 0.005617] <4>{c3ee1c40} do_IRQ+0xb0/0xc0
[18:37:36.243154 0.001982] <4>{c3ee1c58} music_irq_dispatch+0x50/0x7c
[18:37:36.246397 0.003242] <4>{c3ee1c80} handle_irq_event_percpu+0x64/0x25c
[18:37:36.252114 0.005717] <4>{c3ee1cc0} handle_percpu_irq+0x54/0x84
[18:37:36.255332 0.003219] <4>{c3ee1ce0} generic_handle_irq+0x28/0x44
[18:37:36.257564 0.002232] <4>{c3ee1cf8} do_IRQ+0xb0/0xc0
[18:37:36.260583 0.003018] <4>{c3ee1d10} ret_from_irq+0x0/0x4
[18:37:36.266012 0.005429] <4>more trace (sp:c3ee1da8):
[18:37:36.267971 0.001959] <4>{c3ee1da8} 0xc339853c [music_gmac@0xc3398000]
[18:37:36.271336 0.003365] <4>{c3ee1de8} 0xc339853c [music_gmac@0xc3398000]
[18:37:36.277050 0.005714] <4>{c3ee1e28} 0xc339a688 [music_gmac@0xc3398000]
[18:37:36.280422 0.003372] <4>{c3ee1e68} process_one_work+0x2dc/0x484
[18:37:36.285009 0.004588] <4>{c3ee1ea0} worker_thread+0x23c/0x3e0
[18:37:36.288212 0.003203] <4>{c3ee1ee0} kthread+0x88/0x90
[18:37:36.291237 0.003025] <4>{c3ee1f18} kernel_thread_helper+0x10/0x18
[18:37:36.296519 0.005282] <4>
[18:37:38.768090 2.471566]
[18:37:38.768223 0.000137]
[18:37:38.768275 0.000053] RouterBOOT booter 3.22
[18:37:38.768736 0.000461]
[18:37:38.768782 0.000046] CRS226-24G-2S+
[18:37:38.771277 0.002494]
[18:37:38.771333 0.000057] CPU frequency: 400 MHz
[18:37:38.773122 0.001789]   Memory size:  64 MiB
[18:37:38.777983 0.004860]     NAND size: 128 MiB
[18:37:38.887068 0.109081]
[18:37:38.887186 0.000123] Press any key within 2 seconds to enter setup..
[18:37:40.919999 2.032808]
[18:37:40.920113 0.000119] loading kernel from nand... OK
[18:37:43.202189 2.282072] setting up elf image... OK
[18:37:43.342161 0.139971] jumping to kernel code
[18:37:47.629077 4.286916] Starting...
[18:37:59.209126 11.580047] Starting services...
[18:38:16.450197 17.241073]


I sense the CPU gets hogged up quite easily, but as much as I can say, I've not used anything that might be out of a purely hardware switch-chip managed configuration (besides giving it an IP and the LCD), the cpu is generally under low load, including at night when I have ~200Mbs of internet traffic going through it twice (ISP>CRS>RB>CRS>SFP attached server)

Well, merely a bottle in the sea, hoping I'm not the only one seeing odd things :)
Anyway of making kernel related messages and crashes more verbose on the console ?

Thanks,
JaXX


For the curious: here's the dmesg of the server with the Intel Card when the switch crash-reboots on it's own: I've updated kernel from old 3.x to a 4.9 with the exact same phenomenon
(An Intel Dual AF-DA in a Proliant Micro Server Gen3)
[Sun Feb  5 09:46:53 2017] ------------[ cut here ]------------
[Sun Feb  5 09:46:53 2017] WARNING: CPU: 0 PID: 0 at /home/zumbi/linux-4.9.2/net/sched/sch_generic.c:316 dev_watchdog+0x220/0x230
[Sun Feb  5 09:46:53 2017] NETDEV WATCHDOG: eth1 (ixgbe): transmit queue 1 timed out
[Sun Feb  5 09:46:53 2017] Modules linked in: tun rfcomm bnep parport_pc bluetooth ppdev lp rfkill parport xt_multiport iptable_filter ip_tables x_tables fuse nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc bridge 8021q garp mrp stp llc loop amd64_edac_mod amdkfd edac_mce_amd edac_core kvm_amd radeon kvm ttm irqbypass pcspkr k10temp drm_kms_helper evdev drm i2c_algo_bit tpm_infineon acpi_cpufreq tpm_tis button tpm_tis_core sp5100_tco tpm i2c_piix4 shpchp ext4 crc16 jbd2 fscrypto mbcache dm_mod raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic md_mod hid_generic usbhid hid sr_mod cdrom sg sd_mod ata_generic ohci_pci tg3 pata_atiixp libphy ixgbe ahci libahci libata ehci_pci ohci_hcd dca ptp pps_core mdio ehci_hcd scsi_mod fjes usbcore usb_common
[Sun Feb  5 09:46:53 2017] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.0-0.bpo.1-amd64 #1 Debian 4.9.2-2~bpo8+1
[Sun Feb  5 09:46:53 2017] Hardware name: HP ProLiant MicroServer, BIOS O41     07/29/2011
[Sun Feb  5 09:46:53 2017]  0000000000000000 ffffffffbe32a1f5 ffff97969fc03e38 0000000000000000
[Sun Feb  5 09:46:53 2017]  ffffffffbe077884 0000000000000001 ffff97969fc03e90 ffff9796960e0000
[Sun Feb  5 09:46:53 2017]  0000000000000000 ffff979696ada740 0000000000000020 ffffffffbe0778ff
[Sun Feb  5 09:46:53 2017] Call Trace:
[Sun Feb  5 09:46:53 2017]  <IRQ>
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe32a1f5>] ? dump_stack+0x5c/0x77
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe077884>] ? __warn+0xc4/0xe0
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe0778ff>] ? warn_slowpath_fmt+0x5f/0x80
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe51fc30>] ? dev_watchdog+0x220/0x230
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe51fa10>] ? dev_deactivate_queue.constprop.27+0x60/0x60
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe0e6210>] ? call_timer_fn+0x30/0x130
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe0e7085>] ? run_timer_softirq+0x215/0x4b0
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe333434>] ? timerqueue_add+0x54/0xa0
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe0e82c8>] ? enqueue_hrtimer+0x38/0x80
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe5fcce6>] ? __do_softirq+0x106/0x292
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe07db08>] ? irq_exit+0x98/0xa0
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe5fcaee>] ? smp_apic_timer_interrupt+0x3e/0x50
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe5fbe02>] ? apic_timer_interrupt+0x82/0x90
[Sun Feb  5 09:46:53 2017]  <EOI>
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe5f9a22>] ? native_safe_halt+0x2/0x10
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe5f9748>] ? default_idle+0x18/0xd0
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe02fb48>] ? amd_e400_idle+0x58/0xd0
[Sun Feb  5 09:46:53 2017]  [<ffffffffbe0bc070>] ? cpu_startup_entry+0x1f0/0x260
[Sun Feb  5 09:46:53 2017]  [<ffffffffbed49f84>] ? start_kernel+0x46d/0x48d
[Sun Feb  5 09:46:53 2017]  [<ffffffffbed49120>] ? early_idt_handler_array+0x120/0x120
[Sun Feb  5 09:46:53 2017]  [<ffffffffbed495b9>] ? x86_64_start_kernel+0x152/0x176
[Sun Feb  5 09:46:53 2017] ---[ end trace 1b654a01d52cecd3 ]---
[Sun Feb  5 09:46:53 2017] ixgbe 0000:02:00.0 eth1: initiating reset due to tx timeout
[Sun Feb  5 09:46:53 2017] ixgbe 0000:02:00.0 eth1: Reset adapter
[Sun Feb  5 09:46:53 2017] ixgbe 0000:02:00.0 eth1: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[Sun Feb  5 09:46:53 2017] ixgbe 0000:02:00.0 eth1: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[Sun Feb  5 09:46:56 2017] ixgbe 0000:02:00.0 eth1: detected SFP+: 0
[Sun Feb  5 09:46:58 2017] ixgbe 0000:02:00.0 eth1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[Sun Feb  5 09:47:08 2017] ixgbe 0000:02:00.0 eth1: initiating reset due to tx timeout
[Sun Feb  5 09:47:08 2017] ixgbe 0000:02:00.0 eth1: Reset adapter
[Sun Feb  5 09:47:08 2017] ixgbe 0000:02:00.0 eth1: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[Sun Feb  5 09:47:08 2017] ixgbe 0000:02:00.0 eth1: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[Sun Feb  5 09:47:11 2017] ixgbe 0000:02:00.0 eth1: detected SFP+: 0
[Sun Feb  5 09:47:13 2017] ixgbe 0000:02:00.0 eth1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[Sun Feb  5 09:47:23 2017] ixgbe 0000:02:00.0 eth1: initiating reset due to tx timeout
[Sun Feb  5 09:47:23 2017] ixgbe 0000:02:00.0 eth1: Reset adapter
[Sun Feb  5 09:47:23 2017] ixgbe 0000:02:00.0 eth1: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[Sun Feb  5 09:47:23 2017] ixgbe 0000:02:00.0 eth1: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[Sun Feb  5 09:47:26 2017] ixgbe 0000:02:00.0 eth1: detected SFP+: 0
[Sun Feb  5 09:47:28 2017] ixgbe 0000:02:00.0 eth1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[Sun Feb  5 09:47:38 2017] ixgbe 0000:02:00.0 eth1: initiating reset due to tx timeout
[Sun Feb  5 09:47:38 2017] ixgbe 0000:02:00.0 eth1: Reset adapter
[Sun Feb  5 09:47:38 2017] ixgbe 0000:02:00.0 eth1: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[Sun Feb  5 09:47:38 2017] ixgbe 0000:02:00.0 eth1: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[Sun Feb  5 09:47:41 2017] ixgbe 0000:02:00.0 eth1: detected SFP+: 0

 
alexjhart
Member Candidate
Member Candidate
Posts: 155
Joined: Thu Jan 20, 2011 9:03 pm
Reputation: 8

Re: v6.39rc [release candidate] is released

Fri Feb 10, 2017 9:14 pm

sergejs wrote:
Thank you very much for the report about capsman oid values.


Happy to help :)
-----
Alex Hart

The Brothers WISP
 
gtj
Member Candidate
Member Candidate
Posts: 112
Joined: Thu Apr 30, 2015 2:52 am
Reputation: 10
Location: Colorado US

Re: v6.39rc [release candidate] is released

Sat Feb 11, 2017 9:30 pm

Whose ever idea it was to add a "Terminal" button to the top of the WebFig pages deserves a BIG PAY RAISE!
 
pe1chl
Forum Guru
Forum Guru
Posts: 2140
Joined: Mon Jun 08, 2015 12:09 pm
Reputation: 31

Re: v6.39rc [release candidate] is released

Sat Feb 11, 2017 11:11 pm

gtj wrote:
Whose ever idea it was to add a "Terminal" button to the top of the WebFig pages deserves a BIG PAY RAISE!

And even more important (the terminal button was already in the left menu): finally the Quickset interface is hidden once you
no longer need it, no more risk to disturb the whole config by clicking a wrong button on the startpage! Hooray!
 
gtj
Member Candidate
Member Candidate
Posts: 112
Joined: Thu Apr 30, 2015 2:52 am
Reputation: 10
Location: Colorado US

Re: v6.39rc [release candidate] is released

Sun Feb 12, 2017 6:50 pm

pe1chl wrote:
(the terminal button was already in the left menu)


To be honest the left menu makes me NUTS because the items can be in different places even on 2 identical devices. Maybe it has something to do with the order packages are installed but IPv6 and PPP seem to be the biggest offenders. Sometimes IPv6 is above IP, sometimes below and on my ccr, it's between Tools and Radius.
 
pe1chl
Forum Guru
Forum Guru
Posts: 2140
Joined: Mon Jun 08, 2015 12:09 pm
Reputation: 31

Re: v6.39rc [release candidate] is released

Sun Feb 12, 2017 9:27 pm

Interesting, I have not seen that problem. IPv6 is in a strange position (not just below IP) but it does not vary for me.
Maybe it depends on the browser or the way the system was installed.
 
dalil
just joined
Posts: 1
Joined: Mon Feb 13, 2017 3:11 pm
Reputation: 0
Contact:

Re: v6.39rc [release candidate] is released

Mon Feb 13, 2017 3:17 pm

And on the new-style "only 16MB flash" models it is even more difficult
 
msatter
Member Candidate
Member Candidate
Posts: 133
Joined: Tue Feb 18, 2014 1:56 am
Reputation: 1
Location: Netherlands

Re: v6.39rc [release candidate] is released

Thu Feb 16, 2017 11:10 am

I am still on RC25 and read that the DHCP-Client has got script fields. Is this also available on up/down of IPv6?

The Wiki is updated with variables for DHCP-IPv6: http://wiki.mikrotik.com/index.php?titl ... 062#Script

It is possible to add a script that will be executed when a prefix or an address is acquired and applied or expires and is removed using DHCP client. There are separated sets of variables that will have the value set by the client depending on prefix or address status change as the client can acquire both and each of them can have a different effect on the router configuration.

Available variables for dhcp-client

pd-valid - value - 1 or 0 - if prefix is acquired and it is applied or not
pd-prefix - value ipv6/num (ipv6 prefix with mask) - the prefix inself
na-valid - value - 1 or 0 - if address is acquired and it is applied or not
na-address - value - ipv6 address - the address

Thanks for working on the Wiki to keep it up to date and it great to use to implement/lookup things and a must read before posting in the forum.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 661
Joined: Wed Jul 16, 2014 7:22 am
Reputation: 23
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Fri Feb 17, 2017 2:32 pm

Version 6.39rc33 has been released.

Changes since previous version:
!) winbox - minimal required version is v3.11;
*) capsman - added support for static virtual interfaces on CAP;
*) chr - fixed problem when transmit speed was reduced by interface queues;
*) defconf - fixed Groove 52 ac band settings;
*) dhcp-client - added "script" option which executes script on state changes;
*) dhcpv4-server - added "lease-hostname" script parameter;
*) dhcpv6-server - require "address-pool" to be specified;
*) export - do not show "read-only" IRQ entries;
*) gps - added "fix-quality" and "horizontal-dilution" parameters;
*) ike1 - fixed unnecessary Radius accounting requests;
*) ike1 - fixed "xauth" Radius login;
*) ike2 - update peer identity after successful EAP authentication;
*) irq - properly detect all IRQ entries;
*) log - added "gps" topic;
*) log - make SNMP logs more compact;
*) lte - buffer AT events while info command is active;
*) ppp-client - added support for Datacard 750UL and DWR-730;
*) snmp - "No Such Instance" error message is replaced with "No Such Object";
*) snmp - fixed "/tool snmp-get" crash on session timeout;
*) snmp - fixed CAPsMAN registration table OID print;
*) snmp - fixed situation when SNMP could not read "/system health" values after reboot;
*) snmp - improved response speed when multiple requests are received within short period of time;
*) tile - added initial support for NVMe SSD disk drives;
*) tr069-client - fixed "traceroute" parameter IDs;
*) userman - show warning when no users are selected for CSV file generation;
*) winbox - added GPS menu;
*) winbox - allow to not specify certificate in IPSec peer settings;
*) winbox - allow unhide SNMP passwords;
*) winbox - do not hide "power-cycle-after" option;
*) winbox - do not show empty LTE fields in Info menu;
*) winbox - hide advertise tab in Hotspot user profile configuration if "transparent-proxy" is not enabled;
*) winbox - properly name CAP Interface on new interface creation;
*) winbox - properly show BGP communities in routing filters table filter;
*) wireless - added Egypt 5.8 country settings;
*) wireless - fixed scan tool stuck in background;
*) wireless - improved compatibility with Intel 2200BG wireless card;
*) x86 - added support for NVMe SSD disk drives;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
There is no shame in not knowing something:
http://wiki.mikrotik.com/wiki/Tips_and_ ... f_RouterOS
 
MayestroPW
just joined
Posts: 17
Joined: Wed Oct 26, 2016 3:28 pm
Reputation: 0

Re: v6.39rc [release candidate] is released

Fri Feb 17, 2017 3:22 pm

capsman - added support for static virtual interfaces on CAP;


What it means?
 
andriys
Forum Veteran
Forum Veteran
Posts: 700
Joined: Thu Nov 24, 2011 2:59 pm
Reputation: 23
Location: Kharkiv, Ukraine

Re: v6.39rc [release candidate] is released

Fri Feb 17, 2017 3:39 pm

MayestroPW wrote:
capsman - added support for static virtual interfaces on CAP;
What it means?

As I understand, now you should be able to create child (virtual) interfaces under the physical interface that's being managed by CAPsMAN. I have not tried it myself yet, though.
 
MayestroPW
just joined
Posts: 17
Joined: Wed Oct 26, 2016 3:28 pm
Reputation: 0

Re: v6.39rc [release candidate] is released

Fri Feb 17, 2017 4:03 pm

As I understand, now you should be able to create child (virtual) interfaces under the physical interface that's being managed by CAPsMAN. I have not tried it myself yet, though.


That function was already
 
andriys
Forum Veteran
Forum Veteran
Posts: 700
Joined: Thu Nov 24, 2011 2:59 pm
Reputation: 23
Location: Kharkiv, Ukraine

Re: v6.39rc [release candidate] is released

Fri Feb 17, 2017 4:16 pm

MayestroPW wrote:
As I understand, now you should be able to create child (virtual) interfaces under the physical interface that's being managed by CAPsMAN. I have not tried it myself yet, though.
That function was already

Nope. It was possible to added slave interface on CAPsMAN (controller), but you could not add slave interface locally on a CAP (managed board) itself. It appears to be possible now.
 
MayestroPW
just joined
Posts: 17
Joined: Wed Oct 26, 2016 3:28 pm
Reputation: 0

Re: v6.39rc [release candidate] is released

Fri Feb 17, 2017 5:03 pm

andriys wrote:
Nope. It was possible to added slave interface on CAPsMAN (controller), but you could not add slave interface locally on a CAP (managed board) itself. It appears to be possible now.


When you connect CAP to CAPsMAN virtual interface on CAP becomes disabled. I just tested it, and it works same as 6.38.1. So it's not it, but would be awesome if it was that ;)
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6573
Joined: Thu Mar 31, 2005 3:33 pm
Reputation: 19
Location: Riga, Latvia
Contact:

Re: v6.39rc [release candidate] is released

Fri Feb 17, 2017 5:15 pm

MayestroPW wrote:
capsman - added support for static virtual interfaces on CAP;


What it means?


CAP supports static interfaces instead of dynamic ones, they do not disappear after reboot and count number is not changed all the time (recognised by mac-address).
 
td32
just joined
Posts: 17
Joined: Fri Nov 18, 2016 6:55 am
Reputation: 0

Re: v6.39rc [release candidate] is released

Fri Feb 17, 2017 7:19 pm

So it seams you don't have to do the copy caps setting to a new one just to set a custom name and make the cap static. nice!
Edit:
mm perhaps i didn't understand it right
what i wrote up can already be done by adding a cap manually.
 
alexjhart
Member Candidate
Member Candidate
Posts: 155
Joined: Thu Jan 20, 2011 9:03 pm
Reputation: 8

Re: v6.39rc [release candidate] is released

Fri Feb 17, 2017 9:08 pm

strods wrote:
Version 6.39rc33 has been released.

Changes since previous version:
...
*) snmp - fixed CAPsMAN registration table OID print;
...


I'm still getting the same incorrect output.
-----
Alex Hart

The Brothers WISP
 
korniza
just joined
Posts: 19
Joined: Fri Jan 06, 2012 5:05 pm
Reputation: 0

Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 7:35 pm

Help people!
I have a script that was reading snmp individual mac address from capsman registration table. After upgrade I can not read any of them.
What is the SNMP oid to get all the wireless clients MAC on capsman (not the count)???!
 
alexjhart
Member Candidate
Member Candidate
Posts: 155
Joined: Thu Jan 20, 2011 9:03 pm
Reputation: 8

Re: RE: Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 7:41 pm

korniza wrote:
Help people!
I have a script that was reading snmp individual mac address from capsman registration table. After upgrade I can not read any of them.
What is the SNMP oid to get all the wireless clients MAC on capsman (not the count)???!

I posted above (ignore the minor bug they're working on)
`/caps-man registration-table print oid` reports 1.3.6.1.4.1.14988.1.1.1.4.1...
but snmpwalk shows that it is really 1.3.6.1.4.1.14988.1.1.1.5.1...

So if you walk that, you'll see stats for all registered capsman clients, including mac address. Does that make sense?
-----
Alex Hart

The Brothers WISP
 
korniza
just joined
Posts: 19
Joined: Fri Jan 06, 2012 5:05 pm
Reputation: 0

Re: RE: Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 7:47 pm

alexjhart wrote:
korniza wrote:
Help people!
I have a script that was reading snmp individual mac address from capsman registration table. After upgrade I can not read any of them.
What is the SNMP oid to get all the wireless clients MAC on capsman (not the count)???!

I posted above (ignore the minor bug they're working on)
`/caps-man registration-table print oid` reports 1.3.6.1.4.1.14988.1.1.1.4.1...
but snmpwalk shows that it is really 1.3.6.1.4.1.14988.1.1.1.5.1...

So if you walk that, you'll see stats for all registered capsman clients, including mac address. Does that make sense?


I get the following which does not have any MAC address of the clients :?

 snmpwalk -c public -v 2c 192.168.10.1 1.3.6.1.4.1.14988.1.1.1.5.1
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.0.4.32.239.134.9.195 = Timeticks: (140225400) 16 days, 5:30:54.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.40.16.123.35.106.44.202 = Timeticks: (114602300) 13 days, 6:20:23.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.44.240.238.73.164.89.204 = Timeticks: (101436600) 11 days, 17:46:06.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.60.51.0.51.170.194.202 = Timeticks: (151901200) 17 days, 13:56:52.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.72.238.12.124.113.215.201 = Timeticks: (290717300) 33 days, 15:32:53.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.92.207.127.1.138.227.193 = Timeticks: (160445600) 18 days, 13:40:56.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.92.207.127.129.10.170.195 = Timeticks: (160445300) 18 days, 13:40:53.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.148.16.62.205.37.201.204 = Timeticks: (304600) 0:50:46.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.164.119.51.168.68.54.194 = Timeticks: (160439000) 18 days, 13:39:50.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.164.119.51.239.164.100.193 = Timeticks: (3174200) 8:49:02.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.168.129.149.141.101.106.195 = Timeticks: (160424800) 18 days, 13:37:28.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.1.85.60.200 = Timeticks: (26533200) 3 days, 1:42:12.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.2.156.36.201 = Timeticks: (290776200) 33 days, 15:42:42.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.3.112.103.201 = Timeticks: (290739400) 33 days, 15:36:34.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.5.105.150.202 = Timeticks: (131831600) 15 days, 6:11:56.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.238.34.128.108.26.145.206 = Timeticks: (271971200) 31 days, 11:28:32.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.0.4.32.239.134.9.195 = Counter32: 5821244
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.40.16.123.35.106.44.202 = Counter32: 73790913
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.44.240.238.73.164.89.204 = Counter32: 14501780
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.60.51.0.51.170.194.202 = Counter32: 3251847
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.72.238.12.124.113.215.201 = Counter32: 428737
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.92.207.127.1.138.227.193 = Counter32: 135337
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.92.207.127.129.10.170.195 = Counter32: 480132
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.148.16.62.205.37.201.204 = Counter32: 2090
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.164.119.51.168.68.54.194 = Counter32: 68642196
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.164.119.51.239.164.100.193 = Counter32: 498267
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.168.129.149.141.101.106.195 = Counter32: 72654044
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.1.85.60.200 = Counter32: 47798728
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.2.156.36.201 = Counter32: 230505304
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.3.112.103.201 = Counter32: 11839456
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.5.105.150.202 = Counter32: 11044643
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.238.34.128.108.26.145.206 = Counter32: 2126093
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.0.4.32.239.134.9.195 = Counter32: 1536484
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.40.16.123.35.106.44.202 = Counter32: 1608283769
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.44.240.238.73.164.89.204 = Counter32: 1464379
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.60.51.0.51.170.194.202 = Counter32: 3173338763
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.72.238.12.124.113.215.201 = Counter32: 829923
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.92.207.127.1.138.227.193 = Counter32: 104828
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.92.207.127.129.10.170.195 = Counter32: 511559
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.148.16.62.205.37.201.204 = Counter32: 4048
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.164.119.51.168.68.54.194 = Counter32: 6079397
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.164.119.51.239.164.100.193 = Counter32: 170935
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.168.129.149.141.101.106.195 = Counter32: 5243963
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.1.85.60.200 = Counter32: 1952933251
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.2.156.36.201 = Counter32: 908878507
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.3.112.103.201 = Counter32: 2161636
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.5.105.150.202 = Counter32: 541918651
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.238.34.128.108.26.145.206 = Counter32: 5897834
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.0.4.32.239.134.9.195 = Counter32: 17605
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.40.16.123.35.106.44.202 = Counter32: 1127441
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.44.240.238.73.164.89.204 = Counter32: 11616
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.60.51.0.51.170.194.202 = Counter32: 35534
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.72.238.12.124.113.215.201 = Counter32: 7080
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.92.207.127.1.138.227.193 = Counter32: 1268
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.92.207.127.129.10.170.195 = Counter32: 7985
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.148.16.62.205.37.201.204 = Counter32: 32
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.164.119.51.168.68.54.194 = Counter32: 64529
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.164.119.51.239.164.100.193 = Counter32: 1744
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.168.129.149.141.101.106.195 = Counter32: 61812
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.1.85.60.200 = Counter32: 878525
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.2.156.36.201 = Counter32: 4235450
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.3.112.103.201 = Counter32: 87886
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.5.105.150.202 = Counter32: 177603
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.238.34.128.108.26.145.206 = Counter32: 26254
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.0.4.32.239.134.9.195 = Counter32: 18520
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.40.16.123.35.106.44.202 = Counter32: 1360940
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.44.240.238.73.164.89.204 = Counter32: 12007
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.60.51.0.51.170.194.202 = Counter32: 5942883
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.72.238.12.124.113.215.201 = Counter32: 8389
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.92.207.127.1.138.227.193 = Counter32: 1323
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.92.207.127.129.10.170.195 = Counter32: 8088
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.148.16.62.205.37.201.204 = Counter32: 48
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.164.119.51.168.68.54.194 = Counter32: 49427
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.164.119.51.239.164.100.193 = Counter32: 1304
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.168.129.149.141.101.106.195 = Counter32: 64913
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.1.85.60.200 = Counter32: 4306854
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.2.156.36.201 = Counter32: 9719647
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.3.112.103.201 = Counter32: 33413
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.5.105.150.202 = Counter32: 3597021
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.238.34.128.108.26.145.206 = Counter32: 81421
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.0.4.32.239.134.9.195 = Gauge32: 120000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.40.16.123.35.106.44.202 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.44.240.238.73.164.89.204 = Gauge32: 104000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.60.51.0.51.170.194.202 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.72.238.12.124.113.215.201 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.92.207.127.1.138.227.193 = Gauge32: 48000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.92.207.127.129.10.170.195 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.148.16.62.205.37.201.204 = Gauge32: 26000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.164.119.51.168.68.54.194 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.164.119.51.239.164.100.193 = Gauge32: 58500000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.168.129.149.141.101.106.195 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.1.85.60.200 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.2.156.36.201 = Gauge32: 57700000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.3.112.103.201 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.5.105.150.202 = Gauge32: 108000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.238.34.128.108.26.145.206 = Gauge32: 270000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.0.4.32.239.134.9.195 = Gauge32: 54000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.40.16.123.35.106.44.202 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.44.240.238.73.164.89.204 = Gauge32: 130000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.60.51.0.51.170.194.202 = Gauge32: 81000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.72.238.12.124.113.215.201 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.92.207.127.1.138.227.193 = Gauge32: 48000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.92.207.127.129.10.170.195 = Gauge32: 18000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.148.16.62.205.37.201.204 = Gauge32: 135000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.164.119.51.168.68.54.194 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.164.119.51.239.164.100.193 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.168.129.149.141.101.106.195 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.1.85.60.200 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.2.156.36.201 = Gauge32: 52000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.3.112.103.201 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.5.105.150.202 = Gauge32: 27000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.238.34.128.108.26.145.206 = Gauge32: 243000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.0.4.32.239.134.9.195 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.40.16.123.35.106.44.202 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.44.240.238.73.164.89.204 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.60.51.0.51.170.194.202 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.72.238.12.124.113.215.201 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.92.207.127.1.138.227.193 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.92.207.127.129.10.170.195 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.148.16.62.205.37.201.204 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.164.119.51.168.68.54.194 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.164.119.51.239.164.100.193 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.168.129.149.141.101.106.195 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.1.85.60.200 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.2.156.36.201 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.3.112.103.201 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.5.105.150.202 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.238.34.128.108.26.145.206 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.0.4.32.239.134.9.195 = INTEGER: -60
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.40.16.123.35.106.44.202 = INTEGER: -39
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.44.240.238.73.164.89.204 = INTEGER: -65
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.60.51.0.51.170.194.202 = INTEGER: -49
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.72.238.12.124.113.215.201 = INTEGER: -66
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.92.207.127.1.138.227.193 = INTEGER: -69
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.92.207.127.129.10.170.195 = INTEGER: -55
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.148.16.62.205.37.201.204 = INTEGER: -66
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.164.119.51.168.68.54.194 = INTEGER: -59
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.164.119.51.239.164.100.193 = INTEGER: -41
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.168.129.149.141.101.106.195 = INTEGER: -44
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.1.85.60.200 = INTEGER: -61
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.2.156.36.201 = INTEGER: -57
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.3.112.103.201 = INTEGER: -51
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.5.105.150.202 = INTEGER: -55
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.238.34.128.108.26.145.206 = INTEGER: -62
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.0.4.32.239.134.9.195 = INTEGER: 4607184
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.40.16.123.35.106.44.202 = INTEGER: 4596448
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.44.240.238.73.164.89.204 = INTEGER: 4596072
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.60.51.0.51.170.194.202 = INTEGER: 4597208
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.72.238.12.124.113.215.201 = INTEGER: 4664576
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.92.207.127.1.138.227.193 = INTEGER: 4602992
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.92.207.127.129.10.170.195 = INTEGER: 4600792
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.148.16.62.205.37.201.204 = INTEGER: 4596960
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.164.119.51.168.68.54.194 = INTEGER: 4619216
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.164.119.51.239.164.100.193 = INTEGER: 4584736
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.168.129.149.141.101.106.195 = INTEGER: 4544520
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.1.85.60.200 = INTEGER: 4601120
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.2.156.36.201 = INTEGER: 4607384
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.3.112.103.201 = INTEGER: 4664208
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.5.105.150.202 = INTEGER: 4538888
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.238.34.128.108.26.145.206 = INTEGER: 4542200


looking around I see that THERE IS NO oid for MAC address as there was before! Mikrotik fixed wrong entry issue removing the MAC entry? :(
/caps-man registration-table print oid
 0 uptime=.1.3.6.1.4.1.14988.1.1.1.4.1.3.176.197.84.2.156.36.201 tx-bytes=.1.3.6.1.4.1.14988.1.1.1.4.1.4.176.197.84.2.156.36.201 rx-bytes=.1.3.6.1.4.1.14988.1.1.1.4.1.5.176.197.84.2.156.36.201
   tx-packets=.1.3.6.1.4.1.14988.1.1.1.4.1.6.176.197.84.2.156.36.201 rx-packets=.1.3.6.1.4.1.14988.1.1.1.4.1.7.176.197.84.2.156.36.201 tx-rate=.1.3.6.1.4.1.14988.1.1.1.4.1.8.176.197.84.2.156.36.201
   rx-rate=.1.3.6.1.4.1.14988.1.1.1.4.1.9.176.197.84.2.156.36.201 tx-signal=.1.3.6.1.4.1.14988.1.1.1.4.1.10.176.197.84.2.156.36.201 rx-signal=.1.3.6.1.4.1.14988.1.1.1.4.1.11.176.197.84.2.156.36.201
   ssid=.1.3.6.1.4.1.14988.1.1.1.4.1.12.176.197.84.2.156.36.201
 
alexjhart
Member Candidate
Member Candidate
Posts: 155
Joined: Thu Jan 20, 2011 9:03 pm
Reputation: 8

Re: RE: Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 8:04 pm

korniza wrote:
alexjhart wrote:
korniza wrote:
Help people!
I have a script that was reading snmp individual mac address from capsman registration table. After upgrade I can not read any of them.
What is the SNMP oid to get all the wireless clients MAC on capsman (not the count)???!

I posted above (ignore the minor bug they're working on)
`/caps-man registration-table print oid` reports 1.3.6.1.4.1.14988.1.1.1.4.1...
but snmpwalk shows that it is really 1.3.6.1.4.1.14988.1.1.1.5.1...

So if you walk that, you'll see stats for all registered capsman clients, including mac address. Does that make sense?


I get the following which does not have any MAC address of the clients :?

 snmpwalk -c public -v 2c 192.168.10.1 1.3.6.1.4.1.14988.1.1.1.5.1
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.0.4.32.239.134.9.195 = Timeticks: (140225400) 16 days, 5:30:54.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.40.16.123.35.106.44.202 = Timeticks: (114602300) 13 days, 6:20:23.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.44.240.238.73.164.89.204 = Timeticks: (101436600) 11 days, 17:46:06.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.60.51.0.51.170.194.202 = Timeticks: (151901200) 17 days, 13:56:52.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.72.238.12.124.113.215.201 = Timeticks: (290717300) 33 days, 15:32:53.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.92.207.127.1.138.227.193 = Timeticks: (160445600) 18 days, 13:40:56.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.92.207.127.129.10.170.195 = Timeticks: (160445300) 18 days, 13:40:53.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.148.16.62.205.37.201.204 = Timeticks: (304600) 0:50:46.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.164.119.51.168.68.54.194 = Timeticks: (160439000) 18 days, 13:39:50.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.164.119.51.239.164.100.193 = Timeticks: (3174200) 8:49:02.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.168.129.149.141.101.106.195 = Timeticks: (160424800) 18 days, 13:37:28.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.1.85.60.200 = Timeticks: (26533200) 3 days, 1:42:12.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.2.156.36.201 = Timeticks: (290776200) 33 days, 15:42:42.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.3.112.103.201 = Timeticks: (290739400) 33 days, 15:36:34.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.5.105.150.202 = Timeticks: (131831600) 15 days, 6:11:56.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.238.34.128.108.26.145.206 = Timeticks: (271971200) 31 days, 11:28:32.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.0.4.32.239.134.9.195 = Counter32: 5821244
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.40.16.123.35.106.44.202 = Counter32: 73790913
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.44.240.238.73.164.89.204 = Counter32: 14501780
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.60.51.0.51.170.194.202 = Counter32: 3251847
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.72.238.12.124.113.215.201 = Counter32: 428737
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.92.207.127.1.138.227.193 = Counter32: 135337
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.92.207.127.129.10.170.195 = Counter32: 480132
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.148.16.62.205.37.201.204 = Counter32: 2090
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.164.119.51.168.68.54.194 = Counter32: 68642196
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.164.119.51.239.164.100.193 = Counter32: 498267
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.168.129.149.141.101.106.195 = Counter32: 72654044
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.1.85.60.200 = Counter32: 47798728
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.2.156.36.201 = Counter32: 230505304
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.3.112.103.201 = Counter32: 11839456
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.5.105.150.202 = Counter32: 11044643
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.238.34.128.108.26.145.206 = Counter32: 2126093
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.0.4.32.239.134.9.195 = Counter32: 1536484
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.40.16.123.35.106.44.202 = Counter32: 1608283769
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.44.240.238.73.164.89.204 = Counter32: 1464379
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.60.51.0.51.170.194.202 = Counter32: 3173338763
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.72.238.12.124.113.215.201 = Counter32: 829923
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.92.207.127.1.138.227.193 = Counter32: 104828
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.92.207.127.129.10.170.195 = Counter32: 511559
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.148.16.62.205.37.201.204 = Counter32: 4048
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.164.119.51.168.68.54.194 = Counter32: 6079397
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.164.119.51.239.164.100.193 = Counter32: 170935
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.168.129.149.141.101.106.195 = Counter32: 5243963
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.1.85.60.200 = Counter32: 1952933251
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.2.156.36.201 = Counter32: 908878507
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.3.112.103.201 = Counter32: 2161636
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.5.105.150.202 = Counter32: 541918651
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.238.34.128.108.26.145.206 = Counter32: 5897834
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.0.4.32.239.134.9.195 = Counter32: 17605
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.40.16.123.35.106.44.202 = Counter32: 1127441
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.44.240.238.73.164.89.204 = Counter32: 11616
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.60.51.0.51.170.194.202 = Counter32: 35534
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.72.238.12.124.113.215.201 = Counter32: 7080
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.92.207.127.1.138.227.193 = Counter32: 1268
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.92.207.127.129.10.170.195 = Counter32: 7985
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.148.16.62.205.37.201.204 = Counter32: 32
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.164.119.51.168.68.54.194 = Counter32: 64529
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.164.119.51.239.164.100.193 = Counter32: 1744
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.168.129.149.141.101.106.195 = Counter32: 61812
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.1.85.60.200 = Counter32: 878525
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.2.156.36.201 = Counter32: 4235450
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.3.112.103.201 = Counter32: 87886
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.5.105.150.202 = Counter32: 177603
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.238.34.128.108.26.145.206 = Counter32: 26254
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.0.4.32.239.134.9.195 = Counter32: 18520
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.40.16.123.35.106.44.202 = Counter32: 1360940
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.44.240.238.73.164.89.204 = Counter32: 12007
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.60.51.0.51.170.194.202 = Counter32: 5942883
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.72.238.12.124.113.215.201 = Counter32: 8389
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.92.207.127.1.138.227.193 = Counter32: 1323
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.92.207.127.129.10.170.195 = Counter32: 8088
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.148.16.62.205.37.201.204 = Counter32: 48
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.164.119.51.168.68.54.194 = Counter32: 49427
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.164.119.51.239.164.100.193 = Counter32: 1304
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.168.129.149.141.101.106.195 = Counter32: 64913
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.1.85.60.200 = Counter32: 4306854
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.2.156.36.201 = Counter32: 9719647
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.3.112.103.201 = Counter32: 33413
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.5.105.150.202 = Counter32: 3597021
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.238.34.128.108.26.145.206 = Counter32: 81421
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.0.4.32.239.134.9.195 = Gauge32: 120000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.40.16.123.35.106.44.202 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.44.240.238.73.164.89.204 = Gauge32: 104000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.60.51.0.51.170.194.202 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.72.238.12.124.113.215.201 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.92.207.127.1.138.227.193 = Gauge32: 48000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.92.207.127.129.10.170.195 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.148.16.62.205.37.201.204 = Gauge32: 26000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.164.119.51.168.68.54.194 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.164.119.51.239.164.100.193 = Gauge32: 58500000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.168.129.149.141.101.106.195 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.1.85.60.200 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.2.156.36.201 = Gauge32: 57700000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.3.112.103.201 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.5.105.150.202 = Gauge32: 108000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.238.34.128.108.26.145.206 = Gauge32: 270000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.0.4.32.239.134.9.195 = Gauge32: 54000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.40.16.123.35.106.44.202 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.44.240.238.73.164.89.204 = Gauge32: 130000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.60.51.0.51.170.194.202 = Gauge32: 81000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.72.238.12.124.113.215.201 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.92.207.127.1.138.227.193 = Gauge32: 48000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.92.207.127.129.10.170.195 = Gauge32: 18000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.148.16.62.205.37.201.204 = Gauge32: 135000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.164.119.51.168.68.54.194 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.164.119.51.239.164.100.193 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.168.129.149.141.101.106.195 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.1.85.60.200 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.2.156.36.201 = Gauge32: 52000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.3.112.103.201 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.5.105.150.202 = Gauge32: 27000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.238.34.128.108.26.145.206 = Gauge32: 243000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.0.4.32.239.134.9.195 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.40.16.123.35.106.44.202 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.44.240.238.73.164.89.204 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.60.51.0.51.170.194.202 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.72.238.12.124.113.215.201 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.92.207.127.1.138.227.193 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.92.207.127.129.10.170.195 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.148.16.62.205.37.201.204 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.164.119.51.168.68.54.194 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.164.119.51.239.164.100.193 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.168.129.149.141.101.106.195 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.1.85.60.200 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.2.156.36.201 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.3.112.103.201 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.5.105.150.202 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.238.34.128.108.26.145.206 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.0.4.32.239.134.9.195 = INTEGER: -60
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.40.16.123.35.106.44.202 = INTEGER: -39
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.44.240.238.73.164.89.204 = INTEGER: -65
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.60.51.0.51.170.194.202 = INTEGER: -49
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.72.238.12.124.113.215.201 = INTEGER: -66
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.92.207.127.1.138.227.193 = INTEGER: -69
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.92.207.127.129.10.170.195 = INTEGER: -55
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.148.16.62.205.37.201.204 = INTEGER: -66
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.164.119.51.168.68.54.194 = INTEGER: -59
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.164.119.51.239.164.100.193 = INTEGER: -41
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.168.129.149.141.101.106.195 = INTEGER: -44
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.1.85.60.200 = INTEGER: -61
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.2.156.36.201 = INTEGER: -57
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.3.112.103.201 = INTEGER: -51
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.5.105.150.202 = INTEGER: -55
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.238.34.128.108.26.145.206 = INTEGER: -62
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.0.4.32.239.134.9.195 = INTEGER: 4607184
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.40.16.123.35.106.44.202 = INTEGER: 4596448
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.44.240.238.73.164.89.204 = INTEGER: 4596072
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.60.51.0.51.170.194.202 = INTEGER: 4597208
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.72.238.12.124.113.215.201 = INTEGER: 4664576
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.92.207.127.1.138.227.193 = INTEGER: 4602992
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.92.207.127.129.10.170.195 = INTEGER: 4600792
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.148.16.62.205.37.201.204 = INTEGER: 4596960
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.164.119.51.168.68.54.194 = INTEGER: 4619216
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.164.119.51.239.164.100.193 = INTEGER: 4584736
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.168.129.149.141.101.106.195 = INTEGER: 4544520
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.1.85.60.200 = INTEGER: 4601120
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.2.156.36.201 = INTEGER: 4607384
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.3.112.103.201 = INTEGER: 4664208
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.5.105.150.202 = INTEGER: 4538888
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.238.34.128.108.26.145.206 = INTEGER: 4542200


looking around I see that THERE IS NO oid for MAC address as there was before! Mikrotik fixed wrong entry issue removing the MAC entry? :(
/caps-man registration-table print oid
 0 uptime=.1.3.6.1.4.1.14988.1.1.1.4.1.3.176.197.84.2.156.36.201 tx-bytes=.1.3.6.1.4.1.14988.1.1.1.4.1.4.176.197.84.2.156.36.201 rx-bytes=.1.3.6.1.4.1.14988.1.1.1.4.1.5.176.197.84.2.156.36.201
   tx-packets=.1.3.6.1.4.1.14988.1.1.1.4.1.6.176.197.84.2.156.36.201 rx-packets=.1.3.6.1.4.1.14988.1.1.1.4.1.7.176.197.84.2.156.36.201 tx-rate=.1.3.6.1.4.1.14988.1.1.1.4.1.8.176.197.84.2.156.36.201
   rx-rate=.1.3.6.1.4.1.14988.1.1.1.4.1.9.176.197.84.2.156.36.201 tx-signal=.1.3.6.1.4.1.14988.1.1.1.4.1.10.176.197.84.2.156.36.201 rx-signal=.1.3.6.1.4.1.14988.1.1.1.4.1.11.176.197.84.2.156.36.201
   ssid=.1.3.6.1.4.1.14988.1.1.1.4.1.12.176.197.84.2.156.36.201


Well, look at that. Not only did they not fix the misprint of oid, they did in fact remove mac from the tree. I'm guessing someone just removed they wrong thing by accident. They'll need to fix that clearly.

In the meantime, I am able to get the mac-address values in rc31 for entries there using a mikrotik script (your original issue?). For example:
> foreach client in=[/caps-man registration-table find] do={put [/caps-man registration-table get $client mac-address]}
-----
Alex Hart

The Brothers WISP
 
alexjhart
Member Candidate
Member Candidate
Posts: 155
Joined: Thu Jan 20, 2011 9:03 pm
Reputation: 8

Re: RE: Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 8:19 pm

alexjhart wrote:
Well, look at that. Not only did they not fix the misprint of oid, they did in fact remove mac from the tree. I'm guessing someone just removed they wrong thing by accident. They'll need to fix that clearly.


I could have sworn it was in there, but I downgraded to the last release (rc27) and still didn't see mac listed in oid tree. So either that changed in an earlier version (perhaps unintentionally) or this just needs to be a feature request. It's gotta be in there in the future though, right?
-----
Alex Hart

The Brothers WISP
 
korniza
just joined
Posts: 19
Joined: Fri Jan 06, 2012 5:05 pm
Reputation: 0

Re: RE: Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 8:31 pm

alexjhart wrote:
alexjhart wrote:
Well, look at that. Not only did they not fix the misprint of oid, they did in fact remove mac from the tree. I'm guessing someone just removed they wrong thing by accident. They'll need to fix that clearly.


I could have sworn it was in there, but I downgraded to the last release (rc27) and still didn't see mac listed in oid tree. So either that changed in an earlier version (perhaps unintentionally) or this just needs to be a feature request. It's gotta be in there in the future though, right?


I do not know if there was on rc27 because I jumped to the latest (6.39rc33) from the 6.38. I hope to be fixed fast as the script I use to get mac address is a geo-location script that reports users availability on the network. fingers crossed!
 
alexjhart
Member Candidate
Member Candidate
Posts: 155
Joined: Thu Jan 20, 2011 9:03 pm
Reputation: 8

Re: RE: Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 8:42 pm

korniza wrote:
alexjhart wrote:
alexjhart wrote:
Well, look at that. Not only did they not fix the misprint of oid, they did in fact remove mac from the tree. I'm guessing someone just removed they wrong thing by accident. They'll need to fix that clearly.


I could have sworn it was in there, but I downgraded to the last release (rc27) and still didn't see mac listed in oid tree. So either that changed in an earlier version (perhaps unintentionally) or this just needs to be a feature request. It's gotta be in there in the future though, right?


I do not know if there was on rc27 because I jumped to the latest (6.39rc33) from the 6.38. I hope to be fixed fast as the script I use to get mac address is a geo-location script that reports users availability on the network. fingers crossed!


Yeah, I also jumped from 6.38rc to 6.39rc, so could have been lost in an earlier version. If we both thought it was there, maybe it was? Either way, I've asked in my ticket they make sure to add it.
-----
Alex Hart

The Brothers WISP
 
korniza
just joined
Posts: 19
Joined: Fri Jan 06, 2012 5:05 pm
Reputation: 0

Re: RE: Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 8:43 pm

alexjhart wrote:
alexjhart wrote:
Well, look at that. Not only did they not fix the misprint of oid, they did in fact remove mac from the tree. I'm guessing someone just removed they wrong thing by accident. They'll need to fix that clearly.


I could have sworn it was in there, but I downgraded to the last release (rc27) and still didn't see mac listed in oid tree. So either that changed in an earlier version (perhaps unintentionally) or this just needs to be a feature request. It's gotta be in there in the future though, right?

6.38.1 is a good version to downgrade and get back mac address oid. I just did it and all are back to normal
 
alexjhart
Member Candidate
Member Candidate
Posts: 155
Joined: Thu Jan 20, 2011 9:03 pm
Reputation: 8

Re: RE: Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 8:44 pm

korniza wrote:
6.38.1 is a good version to downgrade and get back mac address oid. I just did it and all are back to normal

Thanks for taking the time and effort to confirm that. Odds are in our favor they will add that back in then :)
-----
Alex Hart

The Brothers WISP
 
korniza
just joined
Posts: 19
Joined: Fri Jan 06, 2012 5:05 pm
Reputation: 0

Re: RE: Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 8:52 pm

alexjhart wrote:
korniza wrote:
6.38.1 is a good version to downgrade and get back mac address oid. I just did it and all are back to normal

Thanks for taking the time and effort to confirm that. Odds are in our favor they will add that back in then :)

I hope for a quick fix as I had mentioned the wrong oid months ago on viewtopic.php?f=13&t=107522
Till then still they have wrong output on oid on console that snmp-walk. And now they broke it. Shall we will wait months to get back the previous functionality and get matched oid? Hoping for the best....
 
expert
newbie
Posts: 45
Joined: Sun Dec 04, 2016 2:22 pm
Reputation: 0

Re: v6.39rc [release candidate] is released

Sat Feb 18, 2017 10:17 pm

Is the RSTP problem (which I reported here viewtopic.php?f=21&t=116951&start=50#p582781 ) fixed?
 
Zorro
Long time Member
Long time Member
Posts: 667
Joined: Wed Apr 16, 2014 2:43 pm
Reputation: 17

Re: v6.39rc [release candidate] is released

Sun Feb 19, 2017 9:42 pm

noticed that last RC's of 639 both upgrade and Boot-Up MUCH faster than before.
not big deal, but not bad thing either.
 
mducharme
Member Candidate
Member Candidate
Posts: 224
Joined: Tue Jul 19, 2016 6:45 pm
Reputation: 10

Re: v6.39rc [release candidate] is released

Sun Feb 19, 2017 11:32 pm

Hello,

If you can fix in an upcoming RC - in the TR-069 data model, the MAC address for Ethernet interfaces seems to be missing. I can still see the MAC addresses for the wireless interfaces, but they are gone for the Ethernet interfaces. I have many other stats, ex. byte counts for all ethernet interfaces, but no MAC addresses. This looks like a strange oversight. It is useful for us to collect the MAC address of our managed devices, particularly the ether1 interface, so I would really like to have this data.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 661
Joined: Wed Jul 16, 2014 7:22 am
Reputation: 23
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Mon Feb 20, 2017 11:29 am

OIDs for CAPsMAN will be fixed in next rc release. MAC-Address parameter is removed since it was already available and this was a duplicate entry,
There is no shame in not knowing something:
http://wiki.mikrotik.com/wiki/Tips_and_ ... f_RouterOS
 
VASCO108
just joined
Posts: 2
Joined: Mon Feb 20, 2017 4:20 pm
Reputation: 0

Re: v6.39rc [release candidate] is released

Mon Feb 20, 2017 4:48 pm

Hi everyone

I have 10g ports on my router and graphs look like this:
Image

I am using version: 6.38.1
3G everything looks good, after exceeding this value, it begins to fall apart.
What could be the reason?
I will add that any problems with the link no :) The cacti looks normal.

ps: I apologize in advance for my English :(
 
alexjhart
Member Candidate
Member Candidate
Posts: 155
Joined: Thu Jan 20, 2011 9:03 pm
Reputation: 8

Re: RE: Re: v6.39rc [release candidate] is released

Mon Feb 20, 2017 6:06 pm

VASCO108 wrote:
Hi everyone

I have 10g ports on my router and graphs look like this:
Image

I am using version: 6.38.1
3G everything looks good, after exceeding this value, it begins to fall apart.
What could be the reason?
I will add that any problems with the link no :) The cacti looks normal.

ps: I apologize in advance for my English :(

Looks like a 32 vs 64 bit counter rollover problem. Lots of info if you do a Google search on that. Here is one example:
https://www.google.com/amp/s/gorthx.wor ... -like/amp/
-----
Alex Hart

The Brothers WISP

Who is online

Users browsing this forum: No registered users and 6 guests