BWC Cybersecurity Overlord ✭✭✭
Reactions
Comments
-
Hi @djhurt1 I'am not sure if I can follow for 100%, but at the end it's quite simple. You assign to your Network Interface X5 the IP address 192.168.5.1/24 and that's the Default Gateway you publish via DHCP to your clients on that interface (automatic Interface prepopulation in regards to your other thread). Don't put the…
-
Hi @Micah and this is the part where it gets weird: Reset the passwords for any users who may have logged in to the device via the web interface. What do you mean, only the LocalDomain users or ActiveDirectory, LDAP and Radius as well? What does this even mean, are any credentials possibly compromised? This needs…
-
Hi @Halon5 please have a look at my reply over there: By adding the host directly on the SMA under Network -> Host Resolution I was always able to fix this OPSWAT problem. --Michael@BWC
-
Hi guys, 10.2.0.5-29sv got released, only .sig file so far. If you need to start from scratch with 10.x you're lost at the moment, because all other 10.x releases including the .ova Files for SMA 500v got vanished. Download speed is super slow, got some attention already or SNWL subscribed to the Junior Bandwidth package.…
-
Hi @djhurt1 Routing between X5 and X16 is automatcially done by the subnet (assigned to x5 and x16) routes, of course you need proper defaults routes on the clients pointing to your Firewall. Secondly you need to define the proper access rules from WLAN to LAN and vice versa. If it's not just that simple maybe you can…
-
Yeah, sometimes this crosses my mind as well, but I'll leave it to that :) --Michael@BWC
-
Holy smokes, I suspect another Backend bug here. Probably the Backend or the CC itself does not handle renaming properly. Seems to me that only an uninstall, rename and re-install is the only way to go. But that's to late for the objects you already deleted/lost. SNWL need to chime in here, sounds like a support case, mein…
-
Hi @Jürg first if of all, was your CC Account already migrated or is it a new account? Because I'am still stuck with 3.1.1? I think you have to decommision the unwanted Devices manually or wait until they get auto-decommisioned. --Michael@BWC
-
@Halon5 dunno, I did it solely on the SMA appliance via License sync. After allowing USofA in the GeoIP policy I was able to activate it on every SMA I deployed. --Michael@BWC
-
@Halon5 after allowing the USofA and hitting License sync a few times it got listed as licensed until early April. --Michael@BWC
-
Hi guys, I already have WAF licensed on my personal SMA and was able to activate the 60 day gift on a few machines already. But there are appliances (with valid support) which are stuck on "not licensed". One other thing I figured is the amount of signatures. My SMA shows 692 signatures, the freebie only 21 with a Status…
-
@Maxime Sure thing, 1.1.1.1 should be in the routes and of course in SSL VPN Access. Maybe a Tunnel All would be easier, depending on the number of hosts you wanna route via SSL VPN. --Michael@BWC
-
Hi @Maxime what is the pool of your SSL-VPN users, which addresses you're assigning them for their SSL-VPN session in the Device Profile? If it's not in the 10.10.xx.xx range you'll probably have your answer. If the NetExtender clients getting 10.10.x.x addresses assigned I would suspect it should work. --Michael@BWC
-
SNWL Germany sent a note to Partners a minute ago with the following options: Block access to the SMA via Firewall Shutdown the SMA Downgrade to 9.x (with manual configuration) No Mitigation, no propagation of GeoIP, MFA ... just keep everyone away from this thing. Lucky me I don't the SMA personally, but others my be…
-
SNWL pulled all 10.x Releases from MSW, making free space for the fixed firmware? 😎 At least no new deployments for everyone who lived under a rock for the last 10 days. --Michael@BWC