Posts by kcallis

    The issue that I am having is that when I ssh into my omv server, there is an issue with the $TERM setting. The default $TERM is st-256color, but ssh doesn't seem to like the st-256color. For instance, if I make use of a curses application (for instance omv-firstaid), it fails to run. Even using less fails to work properly. So how can I change the $TERM definition?

    I was able to finally get access to my VLAN interface on my OMV4 machine. Just for clarification, I placed OMV4 on my Proxmox host, and initially I was having issue creating the VLAN interface, but recently was able to ssh into the VLAN interface. The problem that I am having is getting a static route out. I have tried using the web interface as well as command line and no bueno.



    ens18 --> 192.168.30.50 [VLAN30] # Primary OMV4 interface
    ens18.40 --> 192.168.40.50 {VLAN40] # Docker VLAN



    I am able to ssh to the interface with no problems. But when connected to OVM, if I attempt to ssh to a host on my network, the command hangs. Also, I am not able to ping any host on my network. Interestingly enough, I can apt-get update and upgrade, so I am able to resolve names. I also noticed that my docker0 (172.17.0.1) interface is down as well. Granted that I would rather my docker containers worked on the 192.168.40.0/23 network, but it would be nice if the docker0 interface bridge worked as well. I have setup ip forwarding and iptables:



    Bash
    root@fs-01:~# sysctl net.ipv4.conf.all.forwarding=1
    net.ipv4.conf.all.forwarding = 1
    root@fs-01:~# iptables -P FORWARD ACCEPT


    But still no change. Any suggestions would be greatly appreciated.

    I was able to finally get access to my VLAN interface on my OMV4 machine. Just for clarification, I placed OMV4 on my Proxmox host, and initially I was having issue creating the VLAN interface, but recently was able to ssh into the VLAN interface. The problem that I am having is getting a static route out. I have tried using the web interface as well as command line and no bueno.



    ens18 --> 192.168.30.50 [VLAN30] # Primary OMV4 interface
    ens18.40 --> 192.168.40.50 {VLAN40] # Docker VLAN



    I am able to ssh to the interface with no problems. But when connected to OVM, if I attempt to ssh to a host on my network, the command hangs. Also, I am not able to ping any host on my network. Interestingly enough, I can apt-get update and upgrade, so I am able to resolve names. I also noticed that my docker0 (172.17.0.1) interface is down as well. Granted that I would rather my docker containers worked on the 192.168.40.0/23 network, but it would be nice if the docker0 interface bridge worked as well. I have setup ip forwarding and iptables:



    Bash
    root@fs-01:~# sysctl net.ipv4.conf.all.forwarding=1
    net.ipv4.conf.all.forwarding = 1
    root@fs-01:~# iptables -P FORWARD ACCEPT

    But still no change. Any suggestions would be greatly appreciated.

    Although I am having some network issues, I did want to look at the above. I am running under OMV4, so I what should I be placing in my /etc/network/interface.d? I have been battling with getting my VLAN interface working correctly and I would like to make sure that I am not goig to lose my /etc/network/interface file with a reboot.

    I just ran across this thread. I just moved my OMV4 to my Proxmox server. What benefit comes with moving the current kernel to the proxmox kernel? I am not a developer type, just a user that is trying to get a grip on using virtualization.