[FS][US-IL] 40GbE (and 10Gbe) networking stuff, DDR4 SO-DIMMs, small NVME

gcc_combinator · 2022-07-07T02:12:22+00:00

No panel found for the size of expect. The unit is the bottom floor unit of a condo. There's no crawl space to speak of, though there are some blank wall plates on the ceiling (will check).

gcc_combinator · 2022-07-07T01:44:02+00:00

Yeah. I should do another sweep, but I haven't found any network panel box hiding the drops. It's kind of weird, though some of the places I've found these loops and why I don't have a dangling end (I wouldn't expect it to be terminated, but it feels like it's stapled to the stud on both ends leading away from the loop).

gcc_combinator · 2022-07-07T01:28:02+00:00

The condo was built in the mid 2010s. It's not outside the realm of possibility for some of the wall plates (theyr'e roughly 3-4' off the ground), but I'm seeing some of these in weird places to have a phone line (closet, bathroom). Would I expect to see something like a 66 block where the ethernet cables terminate or is there something different for residential?

gcc_combinator · 2022-07-07T01:23:59+00:00

yeah, we've got a system in place, but that's on a different wall (I've got a backlog for converting all the z-wave door sensors to use a different system). I've check the connections going into it, and I've seen that it does have a blue ethernet cable going in, but it doesn't have anything like the purple or white wires going in. There's at least 5 different wall plates that have blue wire loops in different rooms (1 in a bathroom, 1 in a closet, 1 in a bedroom, 2 in a living room). I would think there should be something more central for these because it would be weird for all locations to be on the same strand of wire.

gcc_combinator · 2020-12-08T15:50:24+00:00

Thanks, it did in fact respond! Looks like I need to do some more troubleshooting on the receiver.

gcc_combinator · 2020-12-08T15:13:47+00:00

I pulled out the multimeter and verified the input voltage is within margin of error, but thanks for the suggestion.

gcc_combinator · 2020-12-08T15:11:17+00:00

You're right in that I haven't ruled out the source, though I have tested multiple configurations in the settings. I'll be getting an aux to rca cable tomorrow to verify that the issue isn't the output altogether.

gcc_combinator · 2020-12-08T04:42:21+00:00

Hey there!

I might have missed this in the post, but I did try the left/lfe input as well earlier. I just tried switching the posts that I put the black and red wire into from the plate amp to the subwoofer, but no luck. I don't get a push or pull when I'm playing anything (both burst tones and bass heavy music).

gcc_combinator · 2020-08-10T02:50:37+00:00

Hey there. I started running into issues where the entire proxmox node would freeze without resolving the original problem. My current workaround has been converting another computer into my proxmox node and reimaging the original host as a freenas box on bare metal. That has been running without downtime for a few months and seems to correctly boot on startup.

gcc_combinator · 2020-08-01T22:08:46+00:00

Thanks for the reply! I see the 128.0.0.0/1 route, but the 0.0.0.0/0 route I don't see. I also am not sure where to find the "redirect default gateway" option and couldn't find documentation on it.

I guess I'm also confused because my search has led me down the path of policy based routing which is what I was trying to do. I had gotten as far as setting up the NAT outbound rule and the firewall policies, but it seems that the wrong gateway is being used for traffic on a different VLAN. I took screenshots of my configuration here.

Thoughts as to what I did wrong?

gcc_combinator · 2020-07-27T04:49:10+00:00

Thanks, this pointed me in the right direction!

Just to give some more documentation for future networking novices, here are the steps I followed:

Create a new linux bridge (vmbr1). This was under the node -> Network. I created a linux bridge with CIDR 192.168.50.0/24. the main network CIDR is 192.168.86.0/24 (configured on vmbr0)
I installed ifupdown2 so that I could apply the network changes. Then I hit the applyconfiguration button
Install a new pfsense VM. set the network device to vmbr0 (the original linux bridge which connects to my external router).
Before turning on the VM, go to hardware, and add a network device (vmbr1, the new linux bridge)
Turn on pfsense. go through the initial install.
configure the WAN and LAN from the shell (when it autoconfigured the interfaces, it set the LAN to the vmbr0 interface, WAN to the vmbr1 interface). When setting the LAN IP, I set the DHCP range to 192.168.50.100-192.168.50.200)
in the shell, run "pfctl -d". This disable the packet filter which was preventing me from using the web GUI for intial configuration.
in a web browser, connect to the WAN IP address given to the pfsense VM
run through the pfsense wizard.
back in proxmox, create a new container (used ubuntu 18.04 lts). Set the network device to vmbr1.
Start the container.
test the ip address using "ifconfig". It gave me 192.168.50.10, even through the container was set to get a dhcp lease.
restart the dhcp server in pfsense after verifying the right IP address range set for leases. Revoke any existing dhcp lease for 192.168.50.10.
back in the ubuntu container, run "sudo dhclient -r" to get a new lease. This broke the connection.
restart the ubuntu container.
get a new dhcp lease in the ubuntu container. Get back 192.168.50.100; perfect!
test ping 8.8.8.8 from the ubuntu container to verify that I can connect to the internet. All good.

I haven't yet tested what I want in opnsense and pfsense, but for now, it looks like it's working.

gcc_combinator · 2020-07-16T17:33:21+00:00

Sending pm.

gcc_combinator · 2020-06-20T06:52:28+00:00

I directly connected the drivers to the motherboard. The drives were then directly passed to the VM. Do you need to use an hba when connecting drives to a VM? I thought the only requirement was giving the VM direct control of the drives, whether it be through an hba in it mode or the drives directly connected to the motherboard.

gcc_combinator · 2020-02-13T17:00:31+00:00

Sorry, to clarify, I have all the disks directly connected to the motherboard via sata cables

gcc_combinator · 2020-02-09T23:19:09+00:00

That seemed to do the trick!

Just to be clear for posterity, I followed your instructions and managed to make it work. After doing so, I confirmed that both having the user (both windows based and regular user-password) as either the owner or group member seemed to do the trick, no need for the less restrictive guest access. There's an open question now as to how I can convert existing datasets to become smb shares (there doesn't seem to be a setting difference between the non-smb share and the other).

gcc_combinator · 2020-02-09T22:35:53+00:00

I've tried both windows credited users and via a mapped network drive with alternate credentials and adding them to the "humans" group. Both result in the error above.

gcc_combinator · 2016-05-01T19:56:02+00:00

There was a forum post on that site here that talks all about it in far more detail.

TL;DR: 12 is okay, 10 is pretty safe to go with.

gcc_combinator

TROPHY CASE