Home Networking

11 readers

1 users here now

A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.

Rules

Please stay on topic.
Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
No affiliate links.
No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.

founded 1 year ago

MODERATORS

communick@selfhosted.forum

rglullis@communick.news

Is there a simple method for continuously testing my network as I add features? (alien.top)

submitted 1 year ago by I_EAT_THE_RICH@alien.top to c/homenetworking@selfhosted.forum

0 comments fedilink hide all child comments

I have a home setup that right now is pretty straight forward. I have a DMZ, and host a VPN and some other things but it's not SUPER complex. I am looking forward to adding more rules/VLANs, and subnetworks.

At work we employ TDD or test driven development, where we write the test that need to pass, and then code to that spec. Is there any way to do this with networking?

For example, I'd like a certain VLAN to allow access to network A, but not B. And perhaps one device uses a certain WAN gateway. There are many examples, but my goal is to kind of ensure that those rules aren't broken as I continue to add more. Perhaps I should just write tests to verify and run them after any change? What are these tests typically written in? If that is the case how do I ensure the test "acts" as a different device (in testing it's access)?

Maybe this isn't even necessary if I understand better approaches? Any advice is appreciated.

I'm currently using OPNSense.

no comments (yet)

sorted by: hot top controversial new old

there doesn't seem to be anything here