Who's your cable supplier? Networking |
- Who's your cable supplier?
- PXE and 802.1x Wired
- Palo Alto NPS Radius Auth failing, cannot see anything in authd.log either!
- Firewall Pricing as a provider
- Cisco N9K BV / retimer ports?
- Anybody doing DPSK with Ruckus APs, ideally on Ruckus Cloud (rather than Smartzone/ZD)?
| Posted: 26 Jan 2022 09:01 PM PST Going to need a few thousand-foot boxes of CAT6 here in the near future for long runs, and have already heard enough horror stories of people getting CCA crap in legit looking boxes to not go on Amazon. And my local supplier went out of business. [link] [comments] |
| Posted: 26 Jan 2022 07:12 PM PST Hello all, I am new to the wired auth side of things (been using Clearpass for wireless auth for a while now) and I am running into a small issue. Here's some insight into our environment and what I am trying to accomplish. We have two VLANs: -Untrusted VLAN (any device that is not managed by us or is not receiving a cert to auth. SCCM servers are available for PXE imaging, but otherwise no internal access) -Trusted VLAN (staff/admin devices, using a cert to auth) Currently, we get a new device in and we connect it to the network, and the device is place on the untrusted VLAN using MAB as it is out of the box with no config or cert to auth or anything. We PXE boot and kick off the imaging process, which fails at the task in which it tries to join it to the domain (which is expected as we don't have DCs available on that VLAN yet). I really don't want to expose our DCs on this VLAN with the SCCM server, but I see no other option...We have several buildings so using a single spot for imaging is not ideal, neither is importing the MAC addresses of all our devices. Is there a way for Clearpass to identify a device that is PXE booting and I can assign a "PXE Machine" role to allow it onto the Trusted network in order to finish the imaging process and connect to AD? Or if there is another way that someone is using today, I am all ears. Thanks! [link] [comments] |
| Palo Alto NPS Radius Auth failing, cannot see anything in authd.log either! Posted: 26 Jan 2022 11:42 PM PST Guys, Trying to tshoot this, but when I run the test auth command with the radius profile and check tail follow authd.log I see nothing in it at all, I don't see the username I am testing at all in the authd.log. [link] [comments] |
| Firewall Pricing as a provider Posted: 26 Jan 2022 10:36 PM PST Hi guys, Could anyone help me understand as a provider of firewall. What are cost factors to be taken into account when doing pricing for businesses with clients having staffs over 20k using Palo Alto or cisco firewalls. Thanks :) [link] [comments] |
| Posted: 26 Jan 2022 09:27 PM PST Hi gang, Has anyone come across the term "BV port" or "retimer port" in Cisco Nexus switches? What's so special about them compare to normal ports? [link] [comments] |
| Anybody doing DPSK with Ruckus APs, ideally on Ruckus Cloud (rather than Smartzone/ZD)? Posted: 26 Jan 2022 04:51 PM PST I'm trying to do a deployment of a bunch of Ruckus APs on Ruckus Cloud in an MDU scenario (apartment building). Plan was to use DPSK and issue individual passwords for each customer/unit, with client isolation enabled. (We're offering "internet service," not "this is your personal LAN", so IDGAF about a customer's own interconnectivity.) Tried to enable DPSK network on a test device via Ruckus Cloud, and it just pinwheeled forever and never worked. Opened a ticket with support. Ruckus support came back and told me it's because we have to enable the internal DHCP service (on the AP), effectively turning it into a NAT router rather than working at L2 like most other enterprise APs on the planet. Sure enough, with the AP's internal DHCP turned on, it can host a DPSK SSID now. Worth mentioning: we have M510 APs, which have cellular capability in them. We are not trying to use the cellular, and don't care about it at all (if I could disable it entirely, I would). They were donated to my (non-profit) org, so it's what we have to work with. Support has not yet come back to me explaining if this quirk is something specific to all M-series APs, just the M510s, or if even R-series APs would have this requirement. I'm also not sure if it's something specific to Cloud, or if a Smartzone controller would still give the same result (AFAIK Ruckus Cloud basically is Smartzone but with some knobs removed so I am not sure here). I have not found any sort of user-facing documentation on this limitation, either, so I'm more than a little upset with Ruckus/Commscope at this point. It may force us to totally redesign the network for the project and is a massive pain in the ass. I'm mostly wondering if anybody else has dealt with this on Ruckus APs, especially if it works correctly on the R-series without requiring the internal DHCP. [link] [comments] |
| You are subscribed to email updates from Enterprise Networking Design, Support, and Discussion. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment