• 2 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • Seconded on Cockpit project w File Sharing.

    Probably not best practice, but it’s possible to install it on the PVE host itself since its ZFS manager and Identity manager plugins and other features fills some gaps in what Proxmox doesn’t do (or would have to drop to CLI to do).

    Also recommend RClone in a systemd can take care of various file movements, syncs and backup tasks you may need against the host, vdumps or SMB file shares.




  • I can see where you’re coming from, and agree, but ISPs in Australia providing services on the National Broadband Network NBN will almost always describe this as a modem router.

    It’s not uncommon, right or wrong, even Verisign USA describe a modem vs router thus: “The modem is responsible for sending and receiving signals from the ISP, while the router disperses the signal to devices on the network”

    So, this doesn’t exclusively modulate and demodulate (mo-dem) an analog to digital signal in this case, and 100% it doesn’t have the physical hardware to do so, but it is nonetheless required to negotiate (‘modulate’?) the internet connection with an ISP, albeit software-defined through digital PPP Ethernet protocols.

    All this is a bit off topic, but I hope the OP (or others) may better define the internet service needed, and may determine if this device may be suitable for their requirements.

    I’m glad it includes openwrt support for later down the track. It’s one of the few AX devices with such support and I chose it specifically for this reason!


  • Meets definition of a modem/router depending on what physical connection and protocols your ISP provides.

    My Ethernet WAN connects to the ISPs NTU (optical fibre network termination unit), but WAN is capable of negotiating PPPoE, PPTP or L2TP with PAP/CHAP. Can also Dual WAN, Port forward, NAT.

    The documentation is a little lacking. And no ADSL/VDSL etc. but it meets reqs for some.






  • Difficult to read the graph, but looks like you have less than 4GB ram. Depending what sort of OS and services are running (from above suggestions), this is likely the biggest issue.

    You haven’t mentioned which services you’re running, but 4GB might be enough perhaps for a basic OS with NAS file share services. But anything heavier, like running Container services will eat that up. You’d want at least 8GB.

    Note also that you may not have a dedicated graphics card? If you have integrated graphics, some ram is taken from System and shared with the GPU. If you’re just running command line, you might eke out a little more RAM for system by reducing the VRAM allocation in your BIOS. See: https://en.m.wikipedia.org/wiki/Shared_graphics_memory