*) console - fixed typo in web-proxy (passthru to passhtrough);
country: germany
ranges: 2402-2482/b,g,gn20,gn40(20dBm)
2417-2457/g-turbo(20dBm)
5170-5250/a,an20,an40,ac20,ac40,ac80,ac160(20dBm)/passive
5250-5330/a,an20,an40,ac20,ac40,ac80,ac160(23dBm)/dfs,passive
5490-5710/a,an20,an40,ac20,ac40,ac80,ac160(27dBm)/dfs,passive
5190-5310/a-turbo(20dBm)/dfs
5180-5300/a-turbo(20dBm)/dfs
5520-5680/a-turbo(27dBm)/dfs,passive
5510-5670/a-turbo(27dBm)/dfs,passive
902-927/b,g,g-turbo,gn20,gn40(30dBm)
Yes, this is now an expected behavior due to this exact reason.Is this an intended behavior as a consequence of fasttrack implementation on PPPoE interfaces or just a itsy bitsy bug?
[admin@RT1-YO2LOJ] >> :put [/ip firewall connection find where protocol=41]
(nothing returned)
[admin@RT1-YO2LOJ] >> :put [/ip firewall connection find where protocol=ipv6]
*d542
... wouldn't it be logical to disable fasttrack for connection that depend on mangle rules during connection set-up?
upgrade,RE: !) package - fixed wireless package status after upgrade to 6.37 (extra reboot after upgrade is necessary);
Are the two reboots necessary ? Or is the second reboot only required/needed if there is a 2'nd wireless package that shows up with a different version ?
North Idaho Tom Jones
RE: if you have 2 packages, rebootupgrade,RE: !) package - fixed wireless package status after upgrade to 6.37 (extra reboot after upgrade is necessary);
Are the two reboots necessary ? Or is the second reboot only required/needed if there is a 2'nd wireless package that shows up with a different version ?
North Idaho Tom Jones
if you have 2 packages, reboot.
I have been able to upgrade remote client/routers to 6.37.1 and also the 6.38rc.RE: !) package - fixed wireless package status after upgrade to 6.37 (extra reboot after upgrade is necessary);
IF two reboots are required does this mean we cannot upgrade a router remotely if our only access is via wlan?
No it is not necessary.I was asking something more like --- If there is no second package showing up, then is a 2nd reboot still necessary ?
Will I loose contact with wireless remote station (P2P bridge setup) if I manage it over the wireless link and 'download and install'? Will the remote station then reboot and not be visible to me any more, and need a 'local' reboot too?upgrade,RE: !) package - fixed wireless package status after upgrade to 6.37 (extra reboot after upgrade is necessary);
Are the two reboots necessary ? Or is the second reboot only required/needed if there is a 2'nd wireless package that shows up with a different version ?
North Idaho Tom Jones
if you have 2 packages, reboot.
exactly my question. sorry for the duplication (via my last post).RE: !) package - fixed wireless package status after upgrade to 6.37 (extra reboot after upgrade is necessary);
IF two reboots are required does this mean we cannot upgrade a router remotely if our only access is via wlan?
I have been having 100 percent good luck upgrading remote wireless clients to 6.37.1Will I loose contact with wireless remote station (P2P bridge setup) if I manage it over the wireless link and 'download and install'? Will the remote station then reboot and not be visible to me any more, and need a 'local' reboot too?upgrade,RE: !) package - fixed wireless package status after upgrade to 6.37 (extra reboot after upgrade is necessary);
Are the two reboots necessary ? Or is the second reboot only required/needed if there is a 2'nd wireless package that shows up with a different version ?
North Idaho Tom Jones
if you have 2 packages, reboot.
On my wired headend of the link, I upgraded to 6.37.1 without issue, and link is now up with on 6.36.3 on 'the other side' (that I can't easily manage other than over an established wireless link).
cheers,
Peter
This is a major issue for me as well! Please consider creating a 6.36.4 as bugfix-version because it is the lastest version supporting wireless-cm2.I have >50 devices with Intel(R) PRO/Wireless 2200BG and >40 older wireless IP-Cams which do not work wir current wireless-package. I'm also running a big camtsite-installation where the clients have thousands of different devices. I worry that some clients cannot use our wifi.Device: hAp lite
Problem with old legacy wireless devices (for example Intel(R) PRO/Wireless 2200BG) still persist in 6.37.1 and 6.38rc7 ... can`t connect to network with WPA or WPA2 encryption. without - all fine.
Always getting "extensive data loss".
After downgrading to 6.34.6 - all fine, wireless-cm2 package works perfecty!
great!kolorasta - This is already fixed in 6.38rc.
*) torch - fixed aggregate statistics appearance;
This is my default setting, and ich rechecked it, but i still cannot see this comment.notToNew - In Winbox go to Settings/Inline Comments
As i mentioned, I have this checked(activated) but still cannot see the comments in this window, other windows show the comments just as expected!notToNew:
Winbox SETTINGS / INLINE COMMENTS (above Safe Mode on your screen)
I had exactly this problem !!!I had the problem of add a new static DNS entry and then all connection (web, email, etc) redirect to the address.
This generate a big problem in a company with computers DNS cache's.
/ip dns
set allow-remote-requests=yes cache-size=10240KiB servers=\
8.8.8.8,8.8.4.4
add address=192.168.x.88 name=lala.lala.com
Thanks.
ch36mikrot - Most likely it was working all the time incorrectly. You might need to generate new, proper certificate:
!) ssl - fixed peer address/dns verification from certificate (affects sstp, fetch, capsman);
ik3umt - As it has been also with others, most likely FastTrack was not working in past. For example, you have PPPoE + FastTrack. You live happily and think that it is working but it is not because PPPoE does not support FastTrack. Now MikroTik adds support for PPPoE FastTrack, you upgrade device and think that everything is broken. It simply is what FastTrack does - skips firewall, queues, etc...
http://wiki.mikrotik.com/index.php?titl ... edirect=no
Does this version exist? I know 6.36.3. I would be interested in this aswell, as i cann't upgrade to 6.37 because of wireless-issues.However, I managed to downgrade to 6.36.4 ...
This is a known problem with new wireless-package. only old wireless-cm2 works with some legacy-devices.Old (2.3.6) android smart cannot connect via wifi, connect\disconnect in one second.
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n default-authentication=no \
default-forwarding=no disabled=no distance=indoors frequency=2442 mode=\
ap-bridge name=<INTERFACENAME> ssid="<SSSID>"
Did you find a fix? I have same Issue in different versions of hyper-v 2012r2 and 2016... Also tried upgrade and clear install...Killed my CHR at home. Unable to communicate with the router via IP. Cloud logon via console (hyper-v) but unable to list interfaces. Service timeout and the same thing with trying to create a supout.rif. Thank god for snapshots Rollback via snapshot took 10 seconds!
Tested again and if I do not logon I get this in Hyper-V console: Mikrotik Login: Info failed: std failure timeout (13)
Still unable to get a supout.rif. I can however export the entire machine and send it to support (after an upgrade). If imported to the a Windows Server 2012 R2 Hyper-V you can access the .vhdx file and read everything you like.
I'm going to e-mail support.
Edit:
[Ticket#2016100322001305]
I did get a reply from support and they said they are aware of the problem and will be fixed. For the moment the solution is 6.36.3Did you find a fix? I have same Issue in different versions of hyper-v 2012r2 and 2016... Also tried upgrade and clear install...Killed my CHR at home. Unable to communicate with the router via IP. Cloud logon via console (hyper-v) but unable to list interfaces. Service timeout and the same thing with trying to create a supout.rif. Thank god for snapshots Rollback via snapshot took 10 seconds!
Tested again and if I do not logon I get this in Hyper-V console: Mikrotik Login: Info failed: std failure timeout (13)
Still unable to get a supout.rif. I can however export the entire machine and send it to support (after an upgrade). If imported to the a Windows Server 2012 R2 Hyper-V you can access the .vhdx file and read everything you like.
I'm going to e-mail support.
Edit:
[Ticket#2016100322001305]
Did you have an empty SSID on one of the AP interfaces? The new wifi package can't handle those.After upgrade from 6.36.3 to 3.37.1 ui lost my WIFI-Configuration.
It just created the two main wifi-interfaces and lost all virtual interfaces.
I reverted back to 6.36.3, but even restoring the backup-file does not bring back my wifi-configuration.
I do have a export compact, so i manually _can_ restore the config,
but somehow I lost some trust in normal backup-files....
I checked the other config as well: only wifi is missing.
I checked it: no, all ssid's are set.Did you have an empty SSID on one of the AP interfaces? The new wifi package can't handle those.
interface=wlan1_wan
Killed my CHR at home. Unable to communicate with the router via IP. Cloud logon via console (hyper-v) but unable to list interfaces. Service timeout and the same thing with trying to create a supout.rif. Thank god for snapshots Rollback via snapshot took 10 seconds!
Tested again and if I do not logon I get this in Hyper-V console: Mikrotik Login: Info failed: std failure timeout (13)
Still unable to get a supout.rif. I can however export the entire machine and send it to support (after an upgrade). If imported to the a Windows Server 2012 R2 Hyper-V you can access the .vhdx file and read everything you like.
I'm going to e-mail support.
Edit:
[Ticket#2016100322001305]
I will wait for a version that works. Move to a diffrent hypervisor just for this do not seem to be a good idea if you ask meKilled my CHR at home. Unable to communicate with the router via IP. Cloud logon via console (hyper-v) but unable to list interfaces. Service timeout and the same thing with trying to create a supout.rif. Thank god for snapshots Rollback via snapshot took 10 seconds!
Tested again and if I do not logon I get this in Hyper-V console: Mikrotik Login: Info failed: std failure timeout (13)
Still unable to get a supout.rif. I can however export the entire machine and send it to support (after an upgrade). If imported to the a Windows Server 2012 R2 Hyper-V you can access the .vhdx file and read everything you like.
I'm going to e-mail support.
Edit:
[Ticket#2016100322001305]
I tested the 6.37.1 in CCR1036, RB2011, RB951G, RBwAP2 and x86 with XenServer, all good!, if you can try XenServer
the issue is not with DstNAT but with SrcNAT. check other NAT rules (with action=masquerade, probably)We are having all kinds of NAT issues with 3.37.1
We have a VoIP server behind a 1016 running 3.37.1 and have a Dest NAT rule from the public IP address to the VoIP servers IP address.
The Phones can register with no issue. But when you look in the VoIP server it say the phones are registering from the LAN address of the 1016 rather than the Public IP address of wherever the phones are connected.
We are also seeing this behavior with other types of traffic (Not just VoIP)
Has anyone else seen these issues?
It seams still unimplementedWhere can I configure LLDP, I cant find anything related to it in "/ip neighbor" or anywhere else.
19 for me, but this was even on 10, IIRCBTW: What is the limit of "to many" BGP advertisments to be shown? Just 40?
dude version 6.37.1!) winbox - now Winbox 3.6 is the minimum version that can connect to RouterOS;
The DFS is a feature that does not work as it should.Not an error. This is a feature.
[admin@MikroTik] > /interface vlan add name=vlan interface=ether1bond vlan-id=100
[admin@MikroTik] > /interface print
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU MAC-ADDRESS
0 R ether1bond ether 1500 12:34:56:78:90:77
1 R ether2bond ether 1500 12:34:56:78:90:79
2 R vlan vlan 1500 12:34:56:78:90:77
[admin@MikroTik] >
[admin@MikroTik] > /interface bonding add lacp-rate=1sec mode=802.3ad name=bond slaves=ether1bond,ether2bond transmit-hash-policy=layer-3-and-4
[admin@MikroTik] > /interface vlan add name=vlan interface=bond vlan-id=100
failure: could not set mtu
[admin@MikroTik] > /interface print
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU MAC-ADDRESS
0 RS ether1bond ether 1500 12:34:56:78:90:77
1 RS ether2bond ether 1500 12:34:56:78:90:79
2 R bond bond 1500 1500 12:34:56:78:90:77
3 vlan9 vlan 12:34:56:78:90:77
[admin@MikroTik] >
[admin@MikroTik] > /interface vlan add name=vlan interface=bond vlan-id=100 mtu=1496
[admin@MikroTik] > /interface print
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU MAC-ADDRESS
0 RS ether1bond ether 1500 F0:4D:A2:09:E9:77
1 RS ether2bond ether 1500 F0:4D:A2:09:E9:79
2 R bond bond 1500 1500 F0:4D:A2:09:E9:77
3 R vlan vlan 1496 1496 F0:4D:A2:09:E9:77
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU MAC-ADDRESS
0 RS ether1bond ether 1500 1598 9498 12:34:56:78:90:18
1 RS ether2bond ether 1500 1598 9498 12:34:56:78:90:19
2 R bond bond 1500 12:34:56:78:90:18
3 R vlan vlan 1500 12:34:56:78:90:18
Well THAT didn't go well... Upgraded a RB750G from v6.35.2 to v6.37.1 and:
- CPU usage spiked after the update and remained high on a router that normally never goes above 5% CPU load
- Firewall filter rules based on ConnTracking connection state lost that setting. Rather than connection-state=invalid or connection-state=established it showed connection-state=""
I promptly unplugged the external connection, downgraded to v6.34.6 restored my config from backup, and triple checked everything.
Thanks, now I understand why these checkboxes were cleared on one of my routers too...With 6.37.1 it's this.
add action=accept chain=forward comment="allow established connections" connection-state=""
add action=accept chain=forward comment="allow related connections" connection-state=""
add action=drop chain=forward comment="drop invalid connections" connection-state=""
Before upgrade to this version your sentence was correct but now it is not correct anymore .If your script has more permissions that scheduler then scheduler will not be able to execute the script.
I think the "fix" is to set more RAM (>300 MiB) and may be some more disk space for VM, but it's better do not upgrade. At least this time, something went wrong... =)Did you find a fix? I have same Issue in different versions of hyper-v 2012r2 and 2016... Also tried upgrade and clear install...Killed my CHR at home. Unable to communicate with the router via IP. Cloud logon via console (hyper-v) but unable to list interfaces. Service timeout and the same thing with trying to create a supout.rif. Thank god for snapshots Rollback via snapshot took 10 seconds!
Tested again and if I do not logon I get this in Hyper-V console: Mikrotik Login: Info failed: std failure timeout (13)
Still unable to get a supout.rif. I can however export the entire machine and send it to support (after an upgrade). If imported to the a Windows Server 2012 R2 Hyper-V you can access the .vhdx file and read everything you like.
I'm going to e-mail support.
Edit:
[Ticket#2016100322001305]
No it does not require such policies to run a script, unless script itself require such policies.Before upgrade to this version your sentence was correct but now it is not correct anymore .If your script has more permissions that scheduler then scheduler will not be able to execute the script.
Now any schedule SIMPLE script need those permissions to run . It is a bug
It has 1 GB of RAM and 1 GB of disk. The problem according to guesses is the use of synthetic network cards. Waiting fot fix still.I think the "fix" is to set more RAM (>300 MiB) and may be some more disk space for VM, but it's better do not upgrade. At least this time, something went wrong... =)Did you find a fix? I have same Issue in different versions of hyper-v 2012r2 and 2016... Also tried upgrade and clear install...Killed my CHR at home. Unable to communicate with the router via IP. Cloud logon via console (hyper-v) but unable to list interfaces. Service timeout and the same thing with trying to create a supout.rif. Thank god for snapshots Rollback via snapshot took 10 seconds!
Tested again and if I do not logon I get this in Hyper-V console: Mikrotik Login: Info failed: std failure timeout (13)
Still unable to get a supout.rif. I can however export the entire machine and send it to support (after an upgrade). If imported to the a Windows Server 2012 R2 Hyper-V you can access the .vhdx file and read everything you like.
I'm going to e-mail support.
Edit:
[Ticket#2016100322001305]
I faced that weird behaviour this night after upgrading one of our x86 routers: VLAN interface is here on bonding, but it's not working, and after disabling it it was impossible to enable it back ("error enabling VLAN - cannot set mtu" or something like that). The solution was just "/interface set bonding1 l2-mtu=1504". The bad thing is that you cannot change L2-MTU via WinBox (so it was not obvious that it IS changeable), and you cannot change l2-mtu via, for example, "/interface bond set" menu - you need to use exactly "/interface set"- Why can a VLAN be configured with 1500 MTU directly on a physical interface but not on a bonded interface on the CHR?
- Why can a VLAN be configured with 1500 MTU on a bonded interface on the RB1100AHx2?
[admin@Beta] > /interface
[admin@Beta] /interface> print where name=bonding1
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU
0 R bonding1 bond 1500 1500
[admin@Beta] /interface> set 0 l2mtu=1504
[admin@Beta] /interface> print where name=bonding1
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU
0 R bonding1 bond 1500 1500
I have multiple vlans under bonding and even under vrrp under bonding and I don't have the issue you describe with 6.37.1.okay, VLANs on Bonding are completely unusable in this version. the router rebooted, l2-mtu is back to 1500 and now I can't even change it:
this evening was a bit painful...Code: Select all[admin@Beta] > /interface [admin@Beta] /interface> print where name=bonding1 Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU 0 R bonding1 bond 1500 1500 [admin@Beta] /interface> set 0 l2mtu=1504 [admin@Beta] /interface> print where name=bonding1 Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU 0 R bonding1 bond 1500 1500
UPD: l2-mtu of bonding is unchangeable now on any actual version: 6.36.4, 6.37.1, 6.38rc24
Rolled back to 6.33. VLAN is working...
OK this helped thanks!jobo - Please use "Tool/Clear Cache" in Winbox loader before you connect to device. Then it should be back.
please check l2-mtu of ethernets in bonding. mine are empty - looks like it can be the reason:I have multiple vlans under bonding and even under vrrp under bonding and I don't have the issue you describe with 6.37.1.
L2MTU on the bonding interface is 1598
L2MTU on the VRRP interface is 1598
L2MTU on the VLAN interfaces is 1594
MTU is 1500 on all interfaces.
I don't recall when L2MTU stopped being 'editable'. I've never had to change it tbh.
[admin@TestPlace] > interface print where name~"(bonding1|ether6|ether7)"
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU MAC-ADDRESS
0 RS ether6 ether 1500 00:50:56:BE:1F:E4
1 RS ether7 ether 1500 00:50:56:BE:08:9C
2 R bonding1 bond 1500 1500 00:50:56:BE:1F:E4
[admin@TestPlace] >
[cha0s@****] > interface print where name~"(bonding1|ether1-|ether2)"
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU MAC-ADDRESS
0 RS ether1-switch1-port1 ether 1500 1598 4074 D4:CA:6D:**:**:**
1 RS ether2-switch2-port1 ether 1500 1598 4074 D4:CA:6D:**:**:**
2 R bonding1 bond 1500 1598 D4:CA:6D:**:**:**
[cha0s@MikroTik] > interface print where name~"(ether1|ether2)"
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU MAC-ADDRESS
0 R ether1-public ether 1500 00:50:56:84:58:2E
1 R ether2-lan ether 1500 00:50:56:84:78:D9
it's driver-dependent. here's my router in subject:I checked arm, mipsbe, ppc, tile and all show L2MTU properly. Probably an x86-only bug?
[x@y] > int print
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU
0 RS ether1 ether 1500
1 RS ether2 ether 1500
2 R ether3 ether 1500
3 R ether4 ether 1500
4 ether5 ether 1500 9014
5 R Core vlan 1500
6 R bonding1 bond 1500
Ok now I know that this is related to Network Adapters in Hyper-V on Windows Server 2012 R2 and possible older versions.Did you find a fix? I have same Issue in different versions of hyper-v 2012r2 and 2016... Also tried upgrade and clear install...Killed my CHR at home. Unable to communicate with the router via IP. Cloud logon via console (hyper-v) but unable to list interfaces. Service timeout and the same thing with trying to create a supout.rif. Thank god for snapshots Rollback via snapshot took 10 seconds!
Tested again and if I do not logon I get this in Hyper-V console: Mikrotik Login: Info failed: std failure timeout (13)
Still unable to get a supout.rif. I can however export the entire machine and send it to support (after an upgrade). If imported to the a Windows Server 2012 R2 Hyper-V you can access the .vhdx file and read everything you like.
I'm going to e-mail support.
Edit:
[Ticket#2016100322001305]
I'm try downgrade to 6.36.4, same results.Killed my CHR at home. Unable to communicate with the router via IP. Cloud logon via console (hyper-v) but unable to list interfaces. Service timeout and the same thing with trying to create a supout.rif. Thank god for snapshots Rollback via snapshot took 10 seconds!
Tested again and if I do not logon I get this in Hyper-V console: Mikrotik Login: Info failed: std failure timeout (13)
Still unable to get a supout.rif. I can however export the entire machine and send it to support (after an upgrade). If imported to the a Windows Server 2012 R2 Hyper-V you can access the .vhdx file and read everything you like.
I'm going to e-mail support.
Edit:
[Ticket#2016100322001305]
status: radar-detecting
channel: 5640/20-eC/an/DP (3440)
noise-floor: -111dBm
authenticated-clients: 0
current-tx-powers: 6Mbps:19(19/22),9Mbps:19(19/22),12Mbps:19(19/22),18Mbps:19(19/22),24Mbps:19(19/22),36Mbps:16(16/19),48Mbps:14(14/17),
54Mbps:13(13/16),HT20-0:19(19/22),HT20-1:18(18/21),HT20-2:17(17/20),HT20-3:17(17/20),HT20-4:16(16/19),HT20-5:14(14/17),
HT20-6:13(13/16),HT20-7:12(12/15),HT40-0:18(18/21),HT40-1:17(17/20),HT40-2:16(16/19),HT40-3:16(16/19),HT40-4:15(15/18),
HT40-5:13(13/16),HT40-6:12(12/15),HT40-7:11(11/14)
notify-external-fdb: no
This is related to using Network Adapters in Hyper-V on server 2012 R2. Tested on Windows 10 and that works with same setup.I'm try downgrade to 6.36.4, same results.Killed my CHR at home. Unable to communicate with the router via IP. Cloud logon via console (hyper-v) but unable to list interfaces. Service timeout and the same thing with trying to create a supout.rif. Thank god for snapshots Rollback via snapshot took 10 seconds!
Tested again and if I do not logon I get this in Hyper-V console: Mikrotik Login: Info failed: std failure timeout (13)
Still unable to get a supout.rif. I can however export the entire machine and send it to support (after an upgrade). If imported to the a Windows Server 2012 R2 Hyper-V you can access the .vhdx file and read everything you like.
I'm going to e-mail support.
Edit:
[Ticket#2016100322001305]
Latest stable version is 6.36.3 (on my hyper-v 2012 r2)
On the 6.36.4 changelog I see two thing, probably these are the reasons:
*) ethernet - added support for LAN9514 ethernet dongle;
*) ethernet - allow to force mtu value when actual-mtu is already the same;
Same problem, my old smartphone philips w732 could not connect to wifi router. On 6.36.4 works just fine. Is any fixes for this?This is a major issue for me as well! Please consider creating a 6.36.4 as bugfix-version because it is the lastest version supporting wireless-cm2.I have >50 devices with Intel(R) PRO/Wireless 2200BG and >40 older wireless IP-Cams which do not work wir current wireless-package. I'm also running a big camtsite-installation where the clients have thousands of different devices. I worry that some clients cannot use our wifi.Device: hAp lite
Problem with old legacy wireless devices (for example Intel(R) PRO/Wireless 2200BG) still persist in 6.37.1 and 6.38rc7 ... can`t connect to network with WPA or WPA2 encryption. without - all fine.
Always getting "extensive data loss".
After downgrading to 6.34.6 - all fine, wireless-cm2 package works perfecty!
Yes, this is the new "feature". If you use unencrypted wifi (clear the WPA-encryption), it works. (Thats why I moved to 6.36.4, and i'm happy that they support 6.36 as the last version with the old workung packet in the bugfix-branch. I hope they create a kind of an LTS-Version of this branch.)Same problem, my old smartphone philips w732 could not connect to wifi router. On 6.36.4 works just fine. Is any fixes for this?