Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
ohai.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A cozy, fast and secure Mastodon server where everyone is welcome. Run by the folks at ohai.is.

Administered by:

Server stats:

1.9K
active users

ohai.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-nightly.2025-03-25

#OPNsense

5 posts5 participants0 posts today
Replied in thread
Public
Kevin Karhan :verified:

@fusl @mnalis @0xF21D

I do that with #pfSense & #OPNsense (depending on the exact network in question) and have it merge multiple sources that get cached.

In total, I do may out the 30 DNS servers and whilst I have #IPv4only, I have everything ready for #DualStack (#IPv4 + #IPv6) once my ISP stops keeing it's thumbs um their ass...

List of useful things. Contribute to greyhat-academy/lists.d development by creating an account on GitHub.
GitHublists.d/dns.servers.list.tsv at main · greyhat-academy/lists.dList of useful things. Contribute to greyhat-academy/lists.d development by creating an account on GitHub.
#sarcasm
Public
Justine Smithies
Well I finally got #HomeAssistant interfaced to my #OPNsense router and OMG ! I cannot believe that it provided a total of 119 entities for displaying information about my #FreeBSD router. Not that I'm going need anywhere near that.
At the moment I'm showing the following:

CPU's 0-3 temperatures
Memory used
Uptime since last boot
WAN PPPoE Status
OPNsense Integration Updates Available
WAN IN/OUT graphs
LAN IN/OUT graphs


https://github.com/travisghansen/hass-opnsense
OPNsense integration with Home Assistant. Contribute to travisghansen/hass-opnsense development by creating an account on GitHub.
GitHubGitHub - travisghansen/hass-opnsense: OPNsense integration with Home AssistantOPNsense integration with Home Assistant. Contribute to travisghansen/hass-opnsense development by creating an account on GitHub.
Public
Ben Tasker

New #blog post: Isolating our guest wifi network with VLANs and #opnsense

As the result of a wifi hardware change, our guest network ended up comingled with the LAN.

This post sets up a VLAN and configures OPNsense to use dedicated IPv4 and IPv6 subnets for it.

bentasker.co.uk/posts/blog/hou

www.bentasker.co.uk · Isolating our Guest Wireless Network in OPNSense
More from Ben Tasker
Public *
computing competence

Bericht KW12:

- Mo: 14 neue PCs mit #Windows11 aufgebaut, aktualisiert und installiert
- Di: #OPNsense Netzwerkberatung und Proof of Concept für LDAP/Reverse Proxy
- Mi: Benutzermigration der alten auf die 14 neuen #PCs
- Do: #TrueNAS SCALE Server als remote Ziel für Snapshots fertig gestellt. Diverse #3CX Updates und Tickets
- Fr: 3 neue PCs mit #Windows11

Highlight: Auch 14 Kleinrechner lassen sich mit dem #Fahrrad transportieren. Transwiz ist ein geiles Tool: forensit.com/move-computer.html

14 Kleinrechner in einem Fahrradanhänger
Public
sb arms & legs

I've got an old #cisco #ASA 5512-x laying around that I figured might come in handy some day.

My brother recently sent me an article to a fellow who got #opnSense running on it, and of course I had to bite.

It was almost too easy! I tracked down an ancient VGA to IDC connector, installed it on the motherboard, and then changed the BIOS around to boot from a thumbdrive. OpnSense installed without issue, and BAM I have a 7-port gigabit router with a #xeon processor, 8GB of DDR3 and a 128GB SSD.

I haven't tested yet, but supposedly these bad boys can push *almost* full line speed.

Not too bad for free! It appears these can be had online for under $50 all day long.

#SelfHosting#RecycledTech#WasteNotWantNot
Public
JulianCalaby

Cursed homelab update:

Server #2 is very sick with two semi-dead HDDs which is stretching it's RAID6 system disk to the limit. This has also taken out the OSD on that server, so everything is a little broken with Server #1 taking the brunt of the extra load.

Disk "F" died, by which I mean the SAS HBA gave up on it, locking up a bunch of threads in the kernel and userspace, but a reboot brought it back.

Then disk "H" dropped off the face of the earth, which means it's probably power as that what happened a couple of times when the homelab's hardware was more cursed.

The solution is to buy ~4-5 NAS class HDDs, replace disks "F" and "H", throw one in the spare bay in server #3, and use the last one as "bulk" storage on my gaming machine, freeing up 1-2 HDDs which can then get recycled into servers #1 and #2.

Beyond that, Server #2 has been running perfectly for the past month, which clearly means that the future is using low-power ITX motherboards as servers. (I really need some time to flesh out an idea for a poor-man's blade server which is perilously close to this.)

I've also configured OpnSense and Cilium to do some BGP magic and conjure up a private IP range (technically ~5+) for services in Kubernetes.

So now I just need to build a bridge to go from Terraform to Ansible so I can spin up the container in Terraform then configure the VMs and stuff to use it without Ansible needing to know the details in advance. (It's currently going the other way: Ansible knows the details, tells Terraform, then Terraform sets up the Kubernetes services to match)

#homelab#kubernetes#opnsense
ExploreLive feeds
About