edit: or check your your virtual machine ( as i suspect it could be) try to set other type of interface.

I can confirm that 5.0 doesn't work on Hyper-V while 4.x works.

Regarding changing interface type. There are only two:
- legacy network adapter - emulates network device, uses drivers included in linux kernel
- network adapter - requires special drivers and uses vmbus for communication (much, much faster)

Kamil

if you are completely sure, send supout.rif file as i asked in my previous post.

Hyper-V (legacy network adapter)
4.XX - all OK
5.0 beta - network card ether1 detected, I can assign IP addr, but all packets (in/out through this ether1) unreachable.

if you can, create supout.rif file from version that it is not working with. (even maybe rc5) and send it to support@mikrotik.com, so we can check what is happening (or not) and fix this. Just add full explanation on what the problem is to the e-mail also.
edit: or check your your virtual machine ( as i suspect it could be) try to set other type of interface.

I send extended mail to support without supout.rif - I can not save it without network.
PS: I use ONLY "legacy network adapter".
I try it on 2 Hyper-V server (HP, DELL) with different hardware nic's.

I send extended mail to support without supout.rif - I can not save it without network.

make supout.rif on 5.x, downgrade do 4.x , send to MT Team

Traffic show stats only for Tx, strange because at other side shows ok, first is AP bridge second is station wds.
AP: At the same time:

Routers are freezing constantly if using NV2 or NV2 NSTREME instead classic NSTREME. This is happening on every of 48 x86 machines on the network. RBs working ok. Tried to disable multi-cpu=no on machines which have single core and to reduce hw-retries to lower values, for example to 10 but nothing. If bandwidth through links becomes in full load, routers disconnect from links and it is not possible anything but power unplugging and reswitching on. We use 5GHz-A, 40MHz channel.

NSTREME working perfectly on 4.13 and 5.0RC4 and pre-RC5.

enable watchdog with automatic supout and send file to mikrotik if you want to help fix this

problem dude 4 beta 1
os 5 RC 4

any chance to support pppoe option 82 in rc5 ? http://forum.mikrotik.com/viewtopic.php?f=2&t=42698

petro23,

what exactly is the problem, please explain in more detail.

Thank you.

At inclusion of control by means of the program dude it is sharp down throughput of a communication channel and increase ping between points by radio with 4 мс to 12 мс.

and what about CPU load?

dudle on
rb 433 - cpu 60- 75 %
rb 411 - cpu 45- 60%
rb 800 - cpu 25- 40 %
rb 600 - cpu 75 - 80 %
rate 56 Mb


dudle off
rb 433 - cpu 56- 63 %
rb 411 - cpu 40- 50 %
rb 800 - cpu 25- 38 %
rb 600 - cpu 50 - 57 %
rate 56 Mb

brdge + WDS no route no nat

rb 800
http://178.49.144.5:12111/graphs/

rb 600
http://178.49.144.6/graphs/

Hello,
I have issue with traffic flow in rc4, in rc3 works fine, does anyone have problems with traffic flow and rc4?
Flow stop after some time, incorrect flow, not complete and so on...
Thanks

*) added hotspot html variable "host-ip";

What's this for and what does it do?

*) added hotspot html variable "host-ip";

What's this for and what does it do?

It shows you the IP address which is equivalent of the "Address" variable of the Hostpot/Hosts table.

hi,

i have a great problem with rc4 and rc5pre.
i think the ssh daemon is crashing.

after reboot or restarting the ssh service under "ip service dis ssh ; ip service en ssh",
it works for 10 seconds and then the port is closed, you can see this with tcptraceroute on port 22
then i have done a downgrade to rc3 and ssh works but there dont work my firewall rules,
it has accepted all packets - very evil.

now i have beta6 and all works fine.

is there some problems known ?

hi,

i have a great problem with rc4 and rc5pre.
i think the ssh daemon is crashing.

after reboot or restarting the ssh service under "ip service dis ssh ; ip service en ssh",
it works for 10 seconds and then the port is closed, you can see this with tcptraceroute on port 22
then i have done a downgrade to rc3 and ssh works but there dont work my firewall rules,
it has accepted all packets - very evil.

now i have beta6 and all works fine.

is there some problems known ?

please check your email - we sent you a new test release which has fixes to ssh. Please report back after testing that.

hi,

i have a great problem with rc4 and rc5pre.
i think the ssh daemon is crashing.

after reboot or restarting the ssh service under "ip service dis ssh ; ip service en ssh",
it works for 10 seconds and then the port is closed, you can see this with tcptraceroute on port 22
then i have done a downgrade to rc3 and ssh works but there dont work my firewall rules,
it has accepted all packets - very evil.

now i have beta6 and all works fine.

is there some problems known ?

please check your email - we sent you a new test release which has fixes to ssh. Please report back after testing that.

i have installed the new version.
all works fine -> SSH works and all firewall rules are work

thx

RC4 - Working with Mangle - there seems to be a bug with WinBox that moves the Mangle rules to the top automagically. Which is wrong of course.

RC3 and RC4 doesn't work for us. The router RB433UAH has an UMTS Connection on USB port. It's a Huwai/Vodafone K4505. The router reboots if watchdog is enabled or stops working on both the UMTS and lan interface. There is no informative entries in the log about this failures. I will send a supot file to the support.

Please try the newly released on the download page RC5

and please tell us with which version it is totally working for you with this configuraion.

Thank you.