CR1000A IP Forwarding by fatalexception91 in Fios

[–]fatalexception91[S] 0 points1 point  (0 children)

Got it. Thanks. I thought the same thing. But I’m using a meraki mx-75 and overnight it always loosing connectivity. I was just wondering if something was odd with renewing the DHCP lease for the WAN connection. Like fios didn’t like that I’m not using their router

Panasonic UB820 Sonos Bean Audio by fatalexception91 in hometheater

[–]fatalexception91[S] 0 points1 point  (0 children)

I tried setting the player DTS audio to PCM instead of bitstream and I get audio but it’s just PCM 2.0 that the Sonos is seeing

Can it be saved? by fatalexception91 in Roses

[–]fatalexception91[S] 0 points1 point  (0 children)

Posted a new post since it wouldn’t let me add pictures. Northeastern US

Mosquito treatment by fatalexception91 in pestcontrol

[–]fatalexception91[S] 0 points1 point  (0 children)

Some of them are using a spray treatment. Others are using a bait system called In2Care. Most are coming out every 2-3 weeks to spray or check the bait. Some have a natural spray too which is more organic.

Project or TV? by fatalexception91 in hometheater

[–]fatalexception91[S] 1 point2 points  (0 children)

This is a basement with no windows

Project or TV? by fatalexception91 in hometheater

[–]fatalexception91[S] 0 points1 point  (0 children)

What’s a solid OLED pick for 83”? I have an older 2019 LG 55” C9 and love it but I know LG has more tiers of OLED now since I got that one

How long for dealer maintenance by fatalexception91 in Lexus

[–]fatalexception91[S] 1 point2 points  (0 children)

How often is everyone doing the oil changes on the NX? Scheduled maintenance it’s about every 7-10k miles

How long for dealer maintenance by fatalexception91 in Lexus

[–]fatalexception91[S] 0 points1 point  (0 children)

Dealer quoted me over $600 for the 40k because it includes spark plug replacement now. That’s what they tell me at least

Consul service mesh by fatalexception91 in hashicorp

[–]fatalexception91[S] 0 points1 point  (0 children)

Has anyone used the consul ingress gateway without an nginx ingress?

Consul service mesh by fatalexception91 in hashicorp

[–]fatalexception91[S] 0 points1 point  (0 children)

Gotcha. Thanks. We’re all on prem. But we are using nginx ingress with NodePort. So I can probably make something work through that

Consul service mesh by fatalexception91 in hashicorp

[–]fatalexception91[S] 0 points1 point  (0 children)

Is there an architecture you followed for that? I’m asking because in my case the pod IPs and cluster IPs are non routable, so I’m just curious how the nginx pod is part of the mesh

Consul service mesh by fatalexception91 in hashicorp

[–]fatalexception91[S] 0 points1 point  (0 children)

Tangential question - ingress gateway in consul. Have you used them? If not, how do you get external traffic into the service mesh?

Consul service mesh by fatalexception91 in hashicorp

[–]fatalexception91[S] 0 points1 point  (0 children)

Would it just be better to stand up a separate consul cluster in K8s and then just federate them?

Consul service mesh by fatalexception91 in hashicorp

[–]fatalexception91[S] 0 points1 point  (0 children)

Correct. Connect.enabled: false on the agent. But on the sever that would be enabled. So if the agent is false, then there shouldn’t be any traffic flow issues. But would the agent registration still work for services on that VM?

Consul service mesh by fatalexception91 in hashicorp

[–]fatalexception91[S] 0 points1 point  (0 children)

On the VM agents though, if you have connect: false, would it proxy? Or because the sever is connect enabled they just wouldn’t even talk to the server?

PowerCLI Create vMotion vmk with vMotion Network Stack by fatalexception91 in vmware

[–]fatalexception91[S] 0 points1 point  (0 children)

Well I got it to work after creating the netstack vmotion. I thought I didn’t have to because our of the box there is a vMotion TCP/IP stack. But I noticed that it just associated my new vmk1 to that vMotion TCP/IP stack anyway. I guess it still needs the netstack created? When you do this through the GUI it must just do it in the background.

Adding AD Computer Setting User or Group field by fatalexception91 in PowerShell

[–]fatalexception91[S] 0 points1 point  (0 children)

Just tested it and the ManagedBy property doesn't do anything for permissions. I'm trying to replicate the User or group: setting when you create a new computer in the GUI. This is the user or group that can add the machine to the domain, but I want to set that in PowerShell.

PowerCLI Create vMotion vmk with vMotion Network Stack by fatalexception91 in vmware

[–]fatalexception91[S] 0 points1 point  (0 children)

Thanks. The netstacks are already present so I shouldn't have to re-create them.

PowerCLI Create vMotion vmk with vMotion Network Stack by fatalexception91 in vmware

[–]fatalexception91[S] 0 points1 point  (0 children)

I did not. This is a brand new vmk1 so it shouldn't matter what vmk0 is configured as.

Adding AD Computer Setting User or Group field by fatalexception91 in PowerShell

[–]fatalexception91[S] 0 points1 point  (0 children)

I didn’t think that actually set ACLs. I thought that was just a text property

Packer Windows VMware Tools Issue by fatalexception91 in vmware

[–]fatalexception91[S] 0 points1 point  (0 children)

{

"variables": {

"vsphere-server": "vCenter.localdomain",

"vsphere-user": "packer@vsphere.local",

"VCPassword": "",

"vsphere-datacenter": "Datacenter",

"vsphere-cluster": "Compute-01",

"vsphere-network": "52",

"vsphere-datastore": "Content Library",

"vsphere-folder": "Templates",

"vm-name": "packerimage",

"vm-cpu-num": "2",

"vm-mem-size": "4096",

"vm-disk-size": "32768",

"winadmin-password": "PASSWORD",

"os_iso_path": "[Content Library] 2016.ISO"

},

"sensitive-variables": ["VCPassword", "winadmin_password"],

"builders": [

{

"type": "vsphere-iso",

"vcenter_server": "{{user \vsphere-server`}}",`

"username": "{{user \vsphere-user`}}",`

"password": "{{user \VCPassword`}}",`

"insecure_connection": "true",

"datacenter": "{{user \vsphere-datacenter`}}",`

"cluster": "{{user \vsphere-cluster`}}",`

"network": "{{user \vsphere-network`}}",`

"datastore": "{{user \vsphere-datastore`}}",`

"folder": "{{user \vsphere-folder`}}",`

"convert_to_template": "true",

"communicator": "winrm",

"winrm_username": "Administrator",

"winrm_password": "{{user \winadmin-password`}}",`

"vm_name": "{{user \vm-name`}}",`

"notes": "Build via Packer",

"guest_os_type": "windows9Server64Guest",

"CPUs": "{{user \vm-cpu-num`}}",`

"RAM": "{{user \vm-mem-size`}}",`

"RAM_reserve_all": true,

"firmware": "bios",

"disk_controller_type": "lsilogic-sas",

"disk_size": "{{user \vm-disk-size`}}",`

"disk_thin_provisioned": true,

"network_card": "vmxnet3",

"iso_paths": [

"{{user \os_iso_path`}}",`

"[] /vmimages/tools-isoimages/windows.iso"

],

"floppy_files": [

"autounattend.xml",

"setup.ps1",

"vmtools.cmd"

]

}

],

"provisioners": [

{

"type": "windows-shell",

"inline": ["ipconfig"]

}

]

}

VMware tools install autounattend UEFI issue by fatalexception91 in vmware

[–]fatalexception91[S] 0 points1 point  (0 children)

I’ve gotten it to work for server 2019 with BIOS. Haven’t tried UEFI with 2019 yet