Search results

Well, this is embarrassing. gpw928 - you are right that I'm not using the default .conf file. For whatever reason when I used the two restrict lines above and restarted ntp it locked up and I had to quit the ssh session. I'll try it again and see but omitting those lines doesn't seem to...

You guys are going to think I'm outta my mind. FreeBDSD v13.3, using the base-included NTP, ntpd 4.2.8p16-a (1). /etc/ntp.conf tos minclock 5 maxclock 8 pool clock.isc.org iburst pool time.nist.gov iburst # allow unrestricted access from the localhost restrict 10.0.0.1/24 nomodify notrap #...

Thank you!

I'm particularly interested in the "Slot #" heading. Is the slot # = SATA or SAS port number on the mobo? Could you show me all the CLI commands you use for this so I can create a similar spreadsheet entry? Identifying which drive tossed an error can be challenging sometimes. Thanks.

What CLI command did you use to get that wonderful output?

Good discussion. I've picked up some tips, thank you. My routine: Backup my Windows 10 data files to my FreeBSD NAS box using cwrsync on Windows. The NAS box is running zfs in raidz3 so I'm not terribly worried about losing the zpool. I do this fairly often. The NAS box has 8, 12TB drives in...

I've been reading extensively about VNET jails (using bridge & epair). I've learned quite a bit. There is one line about this in the handbook which is flat out wrong. "With the bridge created, it will be necessary to attach it to the em0 interface by executing the following command:" (emphasis...

I had to change that rc.conf line to: ifconfig_genet0="DHCP" to get it to work consistently.

He is not doing it in a jail. Then you stand alone (by my extensive reading) in making that claim. I have read much of what eternal_noob has written. I'll try rereading it. There is something about an RPi4B that I haven't figure out yet...

So my understanding is correct. A jail uses the host's kernel and it is misleading to claim otherwise. Thank you.

I'm perplexed. Maybe I'm misunderstanding what you are saying here. In the handbook I found these statements: "Jails do not have a kernel. They run on the host’s kernel." Also, I can't tell you how many blogs, tutorials and how-tos there are which reiterate this - "jails run on the host's...

I don't see why that would work. Jails all share the host kernel.

I've finally made some progress. The Promiscuous Mode was one component of the problem with Virtualbox. It needs to be set to "Allow All". I was only "Allowing VMs". The second issue was my misunderstanding how the if_bridge interface works in relation to its members. The physical interface's...

Yes with zero effect. I've tried so many combinations that I became lost. I'll make sure to try it again but hold out little hope that it will work. But of course I'll report back if it makes a difference now.

I've been struggling with this since early December 2023 with no success. Virtualbox running on a Windows 10 machine. FreeBSD 14.0 guest running inside Virtualbox. I set up a VNET jail. Trying many incantations and how-tos I found (many are simply wrong), I can ping outside the jail as far as...

Sigh... Another handbook to read when I have time. Thanks.

Yes, fehQlibs required. Easily compiled and linked-to for the ucspi-ssl compile. Are there licensing issues to consider? Help me with the version numbering schema. The port version is 0.99b. The authors' version is 0.12.3. Isn't 0.99b > 0.12.3? That is one place where my dissonance lies.

Let me ponder it. Several years back you asked me if I could take over as the spamdyke port maintainer and it looked too daunting, largely because I don't understand how ports are maintained or how their version numbers are changed and why, etc. In the meantime I'll see if I can build a new...

Unfortunately I have neither the skill nor the knowledge about how to take over as the maintainer. I'm just a hobbyist (no CS background).

Best I can tell there has always been a disconnect between the FreeBSD ports version of ucspi-ssl and the version from the author(s). There was another thread here that touched on the discrepancy and the OP said he was ultimately successful in getting the non-port version compiled, mentioning...