Search results

Maybe the port maintainer (vermaden ) can enlighten us?

By Drew Gallatin, reproduced with permission. In Memoriam: Kenneth N. Smith I recently found out that Ken Smith (kensmith) recently passed away. Ken was on the RE team for many years, and was the lead RE for several releases around the FreeBSD 7 timeframe. I knew Ken when I was an...

Time on server is correct anyway.

This works perfectly fine: nat on $ext_if from !self to any -> $ext_if:0 rdr pass on $ext_if inet proto tcp from any to $ext_if port 61122 -> 172.16.110.22 port 22 rdr pass on $ext_if inet proto tcp from any to $ext_if port 9091 -> 192.168.2.1 Neither 172.16.110.22 nor 192.168.2.1 are on...

https://www.netbsd.org/community/

These colors are totally random. And they are again. End of point..

To wit: we are not going to close or lock 'the next XLibre thread', if and when that arrives. So long as it stays technical, manageable, within the rules, and informative. If not, it goes the way of the dodo, whoever posts (in) it. Plain and simple.

As explained here: https://forums.freebsd.org/threads/the-freebsd-forums-official-or-not.99667/page-2#post-723931

You are using words and phrases that are not applicable to a private forum. Freedom of speech does not exist in a private forum, because a private forum does not have a Constitution that guarantees freedom of speech. These forums have a set of rules that dictate what can, and cannot happen on...

Anyway, there it is, thanks for the feedback.

This one? https://web.archive.org/web/20250628213937/https://forums.freebsd.org/threads/so-long-xorg-thanks-for-all-the-fish-hello-xlibre.98054/

This is what is behind that link. Be cautious with 3rd party packages.

This goes against forum rule 7, sorry.

You're in a pager (more/less), type q.

sockstat -l4p53

scottro had it mostly right. The Forums started out not only because other forums failed or went away, but also because people at FreeBSD felt it needed its own community support beyond the mailing lists. This was at a time when mailing lists fell out of general use, and forums became more...

BTW, configuring each and every port and all of its dependencies is sheer madness. You'd only do that (and most of the time non-recursively) if you have a very small set of ports (say 10-20) with very specific non-standard settings. Doing a fully recursive configuration on even a small number...

This is how I have this scripted Process no configuration options for any ports at all -> do not call /usr/local/bin/poudriere options Process conditional configuration options for these ports only -> /usr/local/bin/poudriere options -n -C -j ${jail} -f /list/of/ports Process conditional...

I really advise anyone using blacklistd to check their /etc/blacklistd.conf for netmasks and to restart the service after fixing them. It is very likely that you're not blocking what you think you're blocking, and on a busy server this can actually happen on a pretty massive scale. If you want...

Ages ago, but this has been a consistent issue with blacklistd for me over the years, and I got caught by it again today. As a punt, I added netmasks to all addresses, including single IP addresses (so, added /32 to those). Problem gone. Every 1/* never I see in blacklistctl dump -na is...