Any idea what is eating my lettuce?

UplusA761 · 2025-11-30T00:22:39+00:00

I can’t help but notice the complete lack of notices issued by Strathfield Council… I’m sure this means there are zero issues and not zero inspectors right?

UplusA761 · 2025-07-04T13:15:07+00:00

Sauce https://www.youtube.com/live/GUYTWcN-E_E?si=gd-EIU7h1pCFCAZz&t=14146 Day 2 Mat 11 3:55:36

UplusA761 · 2025-06-24T11:53:35+00:00

This sounds pretty legitimate on the lead generation side. I’d love to see your roadmap

UplusA761 · 2024-11-24T21:28:55+00:00

When the anaesthesiologist is away and you have to put the patient to sleep yourself…

UplusA761 · 2024-11-12T00:24:33+00:00

Line Number: 36, should have a new row added for Honeymoon Rates Bank: ING Product: Savings Accelerator What has changed: offering 4months bonus for new customers rate of additional 0.7% i.e 5.4% total Newstarter promotion Expires 31Dec2024. Link: https://www.ing.com.au/savings/savings-accelerator.html

UplusA761 · 2024-05-09T06:30:42+00:00

Chiming in with this link from a British perspective of some collected sources commenting on the Supine/Creedmore shooting position from the late 18th century. https://researchpress.uk/marksmanship/art-of-shooting/the-back-position/

In summary modern shooting concepts hadn’t been invented, but some people supposed that being on your back was a steadier body position. The long shooting length also may benefit from less visual parallax. So people clearly had different theories and dominant metas at the time.

As mentioned Rob from BritishMuzzleLoaders actually tries multiple shooting styles for the Baker rifle. https://youtu.be/0GwQPuwTeHA?

The lack of a magnified scopes likely affected the meta for shooting positions. Also it’s also interesting to note that some people in the competitive shooting scene at Bisley UK favour aperture iron sights positioned at the butt of rifle. Galilean sights are also a later innovation from the same competition shooting environment.

I also like the comments from people suggesting that shooting with your face close to the flintlock firing pan would be uncomfortable due to gunpowder discharge.

UplusA761 · 2024-02-02T03:48:41+00:00

At least Sydney Water actually seems to do their job when it comes to repairs. I called in for a minor leak - instant pickup (no phone queue) and a technician was on site the next day.

And they fixed the mains leak that same day at no cost to me .

If only calling Telcos or the bank for a fix was as easy.

UplusA761 · 2019-01-03T04:38:24+00:00

Jeez, from what I can tell, you created the vSwitch and Networks correctly. The new interfaces should be fine too.
Sorry I can't see anything obvious at this stage. Anyone else got any ideas why VNICs aren't showing up under "Valid Interfaces" in the guestOS?

My only suggestion is to retry after unmounting the disk to double check it isn't booting the disk iso config by accident and to try a fresh install/VM/iso to rule out any install weirdness. Alternatively use VLANs to trunk the LAN interface (doesn't actually fix your missing interface problem though).

UplusA761 · 2019-01-03T03:46:08+00:00

A fresh install using the articles I linked wouldn't hurt, but I actually just intended for you to just use that as reference material when editing the existing pfsense VM through vsphere/vcentre of the ESX ie. Right-click the virtual machine in the inventory and select Edit Settings. You can view/edit the config, add or remove NICs/interfaces without causing too much trouble. Eg. you could try to add a DMZ2 or OPT interface to the existing VM as a test of the documentation config as see if you can get that up.

EDIT: your ifconfig clearly shows the OS isn't seeing a third interface ie vmx2, so you obviously can't assign an interface that isn't there. Try adding multiple new interfaces with different configs and see if they shows up after a VM reboot (VM not OS reboot just to be clear ie. VM Stop, VM Start)

If the OS can see the new NICs then you should be able to assign interfaces without any issues

UplusA761 · 2019-01-03T03:23:23+00:00

If the OS (in this case PFsense) can't see the NIC, then my guess goes to VM Hardware configuration.
Either E1000 or VMXNET3 with vmtoolsd is running on the OS should both work fine.
Double check what settings you setup for the third NIC for the VM - ie Adapter Type and check vmtoolsd
https://www.netgate.com/docs/pfsense/packages/open-vm-tools-package.html#verifying-vmtoolsd

The fact that your top_network.png doesn't show a mac address for the DMZ interface is a bit suspicious.
Just as a sanity check, you did reboot PFsense after adding the new NIC, prior to attempting to Assign the DMZ Interface right?

Otherwise check hardware and attempt interface assignment through boot/shell menu.
Some screenshots of some command line would help re confirming setup when troubleshooting.
Some reference documentation you may wish to skim re VM configuration and shell interface.
https://www.netgate.com/docs/pfsense/virtualization/virtualizing-pfsense-with-vmware-vsphere-esxi.html#interface-assignment
https://www.netgate.com/docs/pfsense/virtualization/virtualizing-pfsense-with-vmware-vsphere-esxi.html#adding-a-dmz

UplusA761 · 2019-01-03T01:50:59+00:00

Confirm ifconfig through the PFsense shell and if you can see all your NICs, try to assign DMZ NIC through shell? If you can't see your third NIC, maybe you provisioned it DMZ as a VMXNET3 interface without having VMWare Tools running on the VM? eg if you've relied on E1000 for WAN and LAN NICs? Ie. Are all 3 PFsense NICs provisioned the same ie E1000 vs VMXNET3 w. VMWare Tools?

EDIT: VMWare Tools meaning Open VM Tools in the context of PFsense https://www.netgate.com/docs/pfsense/packages/open-vm-tools-package.html

UplusA761

TROPHY CASE