Profile Details

Toggle Sidebar
Recent updates
  • Stassen
    Stassen replied to a discussion, Docker (HOW-TO)

    Reading this post, still running in a issue with network bridges. All tips from Nick and Marcel are in place except additional routing.

    My situation: Base host is ClearOs 7 up-to-date which also runs virtualbox 6. Within Virtualbox I have multiple ClearOS images running, all for a different purpose. This way I can experiment and backup each individual machine. Very Handy in my opinion.

    Currently experimenting with docker in a ClearOS guest (via Virtualbox) which is hosted on Clearos. Everything in the guest is working as desired and the docker app (home-assistant) is running without clear problems but without a bridge to the guest machine (and therefor not accessable in house via the local network).

    Goal is to access a service via 192.168.1.60:8123 which runs inside the docker

    My current output

    [root@HomeAssistant ~]# ifconfig
    docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0
    inet6 fe80::42:c6ff:fe13:a913 prefixlen 64 scopeid 0x20<link>
    ether 02:42:c6:13:a9:13 txqueuelen 0 (Ethernet)
    RX packets 1 bytes 76 (76.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 3 bytes 266 (266.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.60 netmask 255.255.255.0 broadcast 192.168.1.255
    inet6 fe80::a00:27ff:fe38:23b5 prefixlen 64 scopeid 0x20<link>
    ether 08:00:27:38:23:b5 txqueuelen 1000 (Ethernet)
    RX packets 464269 bytes 53550456 (51.0 MiB)
    RX errors 0 dropped 64688 overruns 0 frame 0
    TX packets 1824 bytes 218623 (213.4 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 1000 (Local Loopback)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    /etc/sysconfig/network-scripts/ifcfg-docker0

    DEVICE=docker0
    TYPE="Bridge"
    ONBOOT="yes"
    USERCTL="no"
    BOOTPROTO="none"


    #/etc/sysconfig/docker-network
    # DOCKER_NETWORK_OPTIONS=

    [root@homeassistant ~]# docker network list
    NETWORK ID NAME DRIVER SCOPE
    6ffb64e7a8f5 bridge bridge local
    7fd540cf9587 host host local
    c2b714bc3985 none null local

    [root@homeassistant ~]# docker inspect 6ffb64e7a8f5 7fd540cf9587 c2b714bc3985
    [
    {
    "Name": "bridge",
    "Id": "6ffb64e7a8f50f7a07609cae340a0d5637de46b7e63ed3b9aaf5d16ebe93feaa",
    "Created": "2019-09-05T09:21:35.492594968-04:00",
    "Scope": "local",
    "Driver": "bridge",
    "EnableIPv6": false,
    "IPAM": {
    "Driver": "default",
    "Options": null,
    "Config": [
    {
    "Subnet": "172.17.0.0/16",
    "Gateway": "172.17.0.1"
    }
    ]
    },
    "Internal": false,
    "Attachable": false,
    "Containers": {},
    "Options": {
    "com.docker.network.bridge.default_bridge": "true",
    "com.docker.network.bridge.enable_icc": "true",
    "com.docker.network.bridge.enable_ip_masquerade": "true",
    "com.docker.network.bridge.host_binding_ipv4": "0.0.0.0",
    "com.docker.network.bridge.name": "docker0",
    "com.docker.network.driver.mtu": "1500"
    },
    "Labels": {}
    },
    {
    "Name": "host",
    "Id": "7fd540cf95871450915b183027f6a19cc536eb2389f55519657798a18b8ab0e2",
    "Created": "2019-09-05T07:50:55.669692505-04:00",
    "Scope": "local",
    "Driver": "host",
    "EnableIPv6": false,
    "IPAM": {
    "Driver": "default",
    "Options": null,
    "Config": []
    },
    "Internal": false,
    "Attachable": false,
    "Containers": {
    "8f1baedbf1dfb865bb66b9f63b99da049c936681fdf9bc7ad288778257e40668": {
    "Name": "home-assistant",
    "EndpointID": "d506bed287d16ac981b68adfff57a9d768f6dccb56bd46f089db71ceeb117047",
    "MacAddress": "",
    "IPv4Address": "",
    "IPv6Address": ""
    }
    },
    "Options": {},
    "Labels": {}
    },
    {
    "Name": "none",
    "Id": "c2b714bc3985468e254dd07f36d65fbb54a486265004bdd3cf22a50adc8025a1",
    "Created": "2019-09-05T07:50:55.645840665-04:00",
    "Scope": "local",
    "Driver": "null",
    "EnableIPv6": false,
    "IPAM": {
    "Driver": "default",
    "Options": null,
    "Config": []
    },
    "Internal": false,
    "Attachable": false,
    "Containers": {},
    "Options": {},
    "Labels": {}
    }
    ]

    Any idea what is causing this ?

  • Nick Howitt wrote:

    To me the most likely solution to work is to create the transmission user as a regular user. It gives you transition issues as any file/folder currently owned by transmission will need to be changed to the new regular user. I don't know if this will work as an approach and would need someone to test. I used to have a regular user as I used transmission before it was packaged as an app, but that was back in the 6.x days and I did not use it with a flexshare. I hardly use transmission so I am not in a position to test.


    I did follow your advise in respect of creating a normal user and use that for running transmission. That works fine, but I still have to "chmod 771 /var/flexshare/shares/vol2/" otherwise the services will have insufficient authorisation...

  • Nick Howitt wrote:

    It depends on what the problem is. You can try enabling "Third Party App Access" in the Flexshare webconfig. Alternatively you can disable the nightly update of permissions by changing the value of FlexshareSecurityPermissions to "off" in /etc/clearos/flexshare.conf.


    Nick

    Third Party App Access can only be set to "read only" access and therefor I'm not sure if that resolves the issue.

    I'm most likely not the first person that wants:
    - Flexshare permission check/repair process out of the box
    - And still give 3rd party programs permanent access to the specific user folder on the specific flexshare.

    What is the best solution in that situation? It is wel possible that the Directory is in use when the flexshare permission is being checked

  • Flexshare rights are corrected via Cron...

    chmod 777 /var/flexshare/shares/vol2/Downloads
    chmod 771 /var/flexshare/shares/vol2/

    Remains only for the day...

    So every day I need to execute these corrections (which of course can be scheduled also) before using transmission...

    What is the proper way to solve this ?

  • Just re-installed my server and Transmission was causing an authorisation issue on the flexshare download location, although reading everything available. Finally checked the rights of the directory above the download directory and changed that with chmod 771 /var/flexshare/shares/vol2/Downloads...

    That was the solution of my issue. So don't forget to check more than only the download location rights. Running Transmission with the standard default user transmission

  • Network card settings changed from LAN to External and added gateway to it.

    Problem resolved

    See attachment

  • Server can't connect to Internet after network card update

    Just finished the upgrade to Clearos 7 which was prepared on a different hardware platform (to reduce the downtime of my shares used by the family). Everything is configured as a stand-alone server and works great but...

    I do have a perfect network connection to the server and no connection issues. From this new server I can ping everything within the local domain 192.x.x.x but all external traffic to and from the new server is has become a problem after the hardware swap (which has a different NIC)

    After moving the prepared harddisk to the destination hardware, I ofcourse had to adapt the network settings which I did via the graphical interface. After a reboot everything worked as expected, but I just found out that I lost the possibility to connect to the internet directly, which did work fine before with the other Hardware...

    Can't see something strange and I did not update any network config manually,

    Network.conf

    # Network mode
    MODE="trustedstandalone"

    # Network interface roles
    EXTIF=""
    LANIF="enp1s0f0"
    DMZIF=""
    HOTIF=""

    # Domain and Internet Hostname
    DEFAULT_DOMAIN="server.home.net"
    INTERNET_HOSTNAME="stassen.dyndns.dk"

    # Extra LANS
    EXTRALANS=""

    # ISP Maximum Speeds

    /etc/sysconfig/network-scripts/ifcfg-enp1s0f0

    DEVICE=enp1s0f0
    TYPE="Ethernet"
    ONBOOT="yes"
    USERCTL="no"
    BOOTPROTO="static"
    IPADDR="192.168.1.2"
    NETMASK="255.255.255.0"

    # ls /etc/sysconfig/network-scripts/ifcfg*

    /etc/sysconfig/network-scripts/ifcfg-enp1s0f0 /etc/sysconfig/network-scripts/ifcfg-lo

    Example of the issue

    root# ping 192.168.1.1
    PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.400 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.342 ms
    64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.339 ms
    64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.348 ms
    ^C
    --- 192.168.1.1 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3000ms
    rtt min/avg/max/mdev = 0.339/0.357/0.400/0.028 ms
    You have new mail in /var/spool/mail/root
    root# ping 8.8.8.8
    connect: Network is unreachable


    Any hints/tips/checks are welcome ....

  • Stassen
    Stassen replied to a discussion, Parted 3TB disk

    Ok...

    I seem to see a difference in output..

    Parted was done in Clearos 7 while my history was read from a running Clearos 6 server. I copied the content anyway and while rebooting the main server (on ClearOs 6), the disk showed its partition as /dev/sdb1.....

    A bit lost what is happening (and would like to know), but it works on the old fstab entries. So problem does not occure in ClearOS

  • Stassen
    Stassen started a new discussion, Parted 3TB disk

    Parted 3TB disk

    I just formatted a 3TB linux partition and I've something that I would like to ask...

    In a previous formatting cycle I was able to achieve a harddisk with the following layout and /dev/sdb1 via fdisk -l

    Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
    255 heads, 63 sectors/track, 486401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x00000000

    Device Boot Start End Blocks Id System
    /dev/sdb1 1 267350 2147483647+ ee GPT

    Today with parted I've created a disk of 3.0TB via "parted /dev/sdb" and which is formatted ext3 and is mounted via /dev/sdb1 on /<whatever>

    Using fdisk -l now I see

    Disk label type: GPT
    Disk Identifier: <something>

    Partition start, partition end, size, Type, name

    That's it !

    I formatted /dev/sdb1

    Question: What is the reason that I don't see /dev/sdb1 while using fdisk -l ?