About DensyoV

zax · ‎09-22-2023

This works for individual switches, but for stacks I get "'errors': ['This endpoint is not supported for switches in switch stack' Can't see the relevance the Layer 3 should be defined in 1 place?

FFT · ‎10-04-2022

I am having a very similar issue. "Roamed from "AP 1" then unexpectedly disassociated, but the client had a successful connection to SSID "**********" for a minute on "AP 2", and then the client roamed to "AP 2". 802.11 REASON (CODE 2) Invalid authentication" What is your advice on how to tune the radios? Do you want overlap or do you want them to not overlap much? Thank you for the help!

ww · ‎05-03-2022

Its now possible to select a secondary concentrator

NandoG · ‎04-12-2021

What about smart devices that only connect at 2.4Ghz? I have a fan that only will connect to a 2.4. I have not been able to connect to my new Z3 AP as the device probably see the 2 bands and gets confused. Any solutions to this issue?

DanielP9 · ‎03-08-2021

Hi, Thanks for your suggestion, I have configured it as: On the MX64 I have a LAN port with: Native VLAN1 (default) Allowed VLANs: 1,2,20,30,40 On the D-Link port at the other end of the cable I have: Tagged VLANs: 2,20,30,40 Untagged VLANs: 1 PVID: 1 Is this correct?

hasnorMD · ‎03-07-2021

@DensyoV I don't see any spoofs under air marshal page. Anyway, I upgraded the s/w from 26.x.x to 27.x.x just now.

cmr · ‎03-05-2021

It can't go out through the MX at HQ if the MX WAN port is connected to the MPLS, you'd need it to be a LAN port. However if it is a LAN port then Auto-VPN cannot form as that needs to be WAN port to WAN port. Therefore you either need an MPLS with internet (this could be provided by having the MPLS terminated on an HQ L3 switch, the WAN port of the MX connected there along with another device that presents internet access to the MPLS) or you need the HQ MX in concentrator mode.

DensyoV · ‎03-04-2021

Hi, yes, that is the error you get when you add multiple destination subnets separated by commas. You will need to create a separate rule for each destination.

jpcaid · ‎03-04-2021

Hi Rafael How did you fix this in the end? i read about dreytek vpn client can fix the constant disconnect.

DensyoV · ‎03-03-2021

Hi, The MX is definitely dropping all inbound traffic by default unless you configure 1:1 NAT, 1:Many NAT or port forwarding. However, it doesn't really have any control of the incoming traffic, it is up to your service provider if they can block certain traffic from reaching your MX.

Diniguez · ‎03-02-2021

So is not possible to have a single static route in the ISR and make it work for both VLANs?

M_berget · ‎02-24-2021

Traffic was blocked on the Azure firewall.

DensyoV · ‎01-04-2021

hi, there is no option to change the speed/duplex setting of the AP port. it auto-negotiates at 1 Gig.

CSampson · ‎12-09-2020

Thanks for the advice. I will give this a try and let you know.

DensyoV · ‎08-26-2020

Hi, I believe the clients will be authorized only for the duration configured. In this case, after 30 mins the clients will have to re-authenticate unless the group policy is still applied.

DensyoV · ‎08-23-2020

Hi, you can whitelist the device for testing to confirm if there is any security filtering enabled that is blocking the traffic. If it works properly when whitelisted, review your layer 3, content filtering and layer 7 FW rule configuration making sure it is not blocking outlook traffic. Lastly, as suggested you can take the Wireshark packet capture.

Tadpole86 · ‎08-20-2020

I can see that this is a single device having issues connecting. Have you tried updateding the client NIC driver?

Mamba123 · ‎08-03-2020

Hi, Phil, Thanks for your message. I spoke with the ISP and he confirmed that we got a wrong SIM card where the VPN functionality is not enabled. Now they want to send me another card. Thank you.

dkdon · ‎06-12-2020

Thanks. It has good technical information. Wish the parameters were not blurred in images as that can have answer to my question. Guess I have to try it out myself and capture the wire logs. 🤞

big-net · ‎06-03-2020

Finally, it was a problem with our internet provider. Everythings works fine now.

Mamba123 · ‎05-03-2020

Hi, Thank you for your message. We have successfully implemented what is described there, but it still does not work. I have now opened a TAC case. The recommendation from TAC was to restart MR and update to the 26.7 version. Neither has improved. Max

Jsmittz · ‎04-20-2020

Update: Device is connected today without issue, without having changed any configurations.

Namgyu · ‎04-19-2020

Thanks for the fast answer, @DensyoV . I will suggest this to Make a Wish.

RaphaelL · ‎03-05-2020

Sorry , I was out of the office. This org seems to be on n238. I have access to a lot of shards also, I tested on n216 and it is working. I think I'm going to open a case about it.

damienleick · ‎03-05-2020

What are your Firmware version on MX / MS / MR There is some probleme for communication between wireless devices and wired device with the MX 14.50 firmware

DensyoV

Community Record

Badges