techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

5.3K
active users

#networkengineer

1 post1 participant0 posts today

Training

Training Requirement: Freelance Trainer – CIS Extreme Wireless Network

Position: Freelance Trainer – CIS Extreme Wireless Network

Location: Remote | Duration: Project-Based/Part-Time

📩 Submit your CV: resumes@overturerede.zohorecruitmail.in

📞 Contact: +9582224661

👉 Apply Now: .
zurl.co/IeK73

#CIS
#ExtremeWireless
#WirelessNetworking
#NetworkEngineer
#WiFiSolutions
#TechInfrastructure
#ITNetworking
#CloudNetworking
#NetworkingExperts
#EnterpriseWiFi

Heeeeey #security #networkSecurity #networkEngineer humans/non-humans! I have a server open to the internet (definitely mentioned this before); currently I have that server connected to a dedicated NIC port on my firewall which is in a separate 'DMZ' (zone) and have rules to block outbound traffic from the 'DMZ' to my internal network. EDIT: Should make it clear the 'DMZ' zone and the regular network are all connected to the same firewall, just via different ports. Use the hardware you have and all that (although I'm not against daisy chaining and hiding the internal network behind another physical firewall if necessary in the future).

Let's say I wanted to add another server to the mix but don't necessarily want to start physically changing the network. Are there good primers on what sort of security risks I might be undertaking if I start using a 'DMZ' VLAN and add clients to the DMZ that way (without having them on a separate wired network that hooks in via the 'DMZ' port/nic on my firewall)? I assume, as a general rule, that utilizing a software solution vs. a hardware solution is always going to carry a separate set of risks, but I also know these software solutions tend to be pretty well tested. Assuming I don't just fuck up the VLAN configuration and firewall rules, am I basically worrying over nothing?

Running
#opnSense, for the record. Thank you!

We are doing a YouTube #shorts series to help #NetworkEngineer's who want to learn code using #python
Taking a small single script that prints an IP address, evolving it to a script that configures multiple interfaces over multiple devices.

In Part 4, we turn a #script that lists a static IP address for all Private Class C /24 ranges, into a a script that generates usable #configuration

youtube.com/shorts/8nMzLPcPXEs

Stay tuned for part 5, where we learn to create a better IP and VLAN scheme.