Search results

your most obvious step here is to set the host IP and gateway as static, reboot and test

Ideally, the raid controller should pass the drives directly through to the operating system for ZFS (aka IT-Mode or HBA-Mode). Unfortunately I don't think the LSI 9260 supports IT-Mode so the best you would be able to do is JBOD mode but in this case you may run into integrity issues as ZFS...

My route info looks slightly different to yours default via 192.168.1.1 dev vmbr0 proto kernel onlink 192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.250 try ip route replace to default via 192.168.1.1 dev vmbr0 proto kernel onlink and see if that gives the host internet access

I run pfSense on a number of proxmox hosts and it runs very reliably on various hardware although none the same as yours. However, I tend to run them as 'default' - i.e machine type=i440fx and Bios=SeaBIOS, have you tried this?

The host probably has no route - it's usual to give the host a static IP and gateway what does ip route show?

Is the gateway device (ISP modem?) not directly attached to the switch?

It's quite possible to run multiple networks for VM's and containers, you may not have even needed to buy a new NIC and VLAN capable switch but then it does mean that you have the capability some physical and well as logical network isolation. If your home network is say - 192.168.100.0/24...

Is the new switch dumb or managed? If it's managed, does the switch register the mac-address of the proxmox host? you probably have at least three devices on the network a) gateway b) proxmox c) your laptop/desktop are they all connected to the same switch? can c ping a and b? can b ping c...

It would seem to me that assigning the WAN port to vmbrx and then configuring that as not-VLAN-aware would cause the VLAN information to be dropped from the packets - don't know for sure but would cost nothing to try :)

I would suggest you try post-up iptables -t nat -A POSTROUTING -s 10.0.0.0/24 -o vmbr0 -j MASQUERADE If you're still having issues after that, I would suggest you forget about bonding as I doubt you will see much benefit and it just adds complication

No, I mean paired together for redundancy and/or bandwidth optimisation - aka link aggregation

Are the ports bonded on the switch?

True, I've heard reports that there are malware tools that do this rendering the drive and data completely inaccessible.

Do you have a USB/Sata docking station? would give you another option to test the drives. Have to say I've never heard of anything 'killing' drives like this and I've worked in IT for a very long time.

On a normal install, there isn't a default webpage on http or https so there's something strange here - do you have a VM running Apache on the same IP? can you open an ssh terminal to Proxmox?

Although there are three network ports on your system, only the two that are close together are actually network ports, the other one is an IPMI port for remote management of the server. You need to establish the correct network settings to use. The live UBUNTU OS will automatically join your...

If you select DHCP when creating the container then the DHCP supplied DNS Server and Domain are set correctly - you can verify by running cat /var/lib/dhcp/dhclient.eth0.leases inside your container to see the supplied DHCP options

useful info, thanks :cool:

So the sophos firewall is running OpenVPN and your remote system is running the client software? None of your LAN clients (including the node) are aware of the VPN but only the node is not reachable from outside via the VPN link Is the node IP address on the same interface as the VM's - i.e...

you need to provide more information before anyone can help you please share /etc/network/interfaces and /etc/pve/qemu-server/<id>.conf where <id> is the id of the VM that is working