asiawatcher

Members
  • Content Count

    17
  • Joined

  • Last visited

  • Days Won

    1

asiawatcher last won the day on November 28 2021

asiawatcher had the most liked content!

Community Reputation

2 Neutral

About asiawatcher

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Also @pocopico will any support for Intel® 82579LM and 82574L, be added on redpill ? cheers
  2. yes i agree with @Franks4fingers some better documentation would be great, not everyone has linux machine and while it could be easy to install it on vmware we don't have the knowledge to compile linux binaries and/or add drivers to the image have been using xpenology since version 5 and then 6 with juns loader but this redpill one i cant follow it !!! talking about legal worries...for how long has xpenology.org exist ? Also finding the actual person to file a lawsuit from a "TTG" nickname is very unlikely !! thats all !
  3. hey @haydibe not all people know how to compile the image!! we just want to use it why jun shared his loader then if there were legal problems?.
  4. does anyone know if this redpill loader https://www.suteediy.tk/downloads which is for the following cards – Intel(R) Gigabit Ethernet Linux Driver E1000 – VirtIO support for fast network/PCI/SCSI/network/console – VMware vmxnet3 virtual NIC driver Other Lan Driver – Realtek RT8125B Gigabit Ethernet Linux Driver – Realtek RT8111GR Gigabir Ethernet Linux Driver – Intel i210 Gigabit Ethernet Linux Driver will work with Realtek RT8111F CHIPSET which my lan card has ? @pocopico is realtek rt8111gr driver same as re
  5. I have tried all DSM versions and high availability has worked for me only on the old 5.2.5592 dsm, anyone has the same problem with me ? using supermicro pizza box atom servers
  6. asiawatcher

    DSM 6.2 Loader

    no its still there you install it from package center separately
  7. asiawatcher

    DSM 6.2 Loader

    high availability doesn't work on any of the ds918 loaders 1.03 or 1.04 with 6.2.1 or 6.2 does anyone know why ? while it sets it up ok then it cant find passive server at least on vmware only with 5.2.5592.2 high avail. with corresponding boot loader works cheers
  8. asiawatcher

    DSM 6.2 Loader

    seems i cannot create high availability cluster i get this error with both filesystems btrfs and ext4 using x2 vmware machines anyone else has the same problem ? cheers
  9. asiawatcher

    DSM 6.2 Loader

    s/n generator is dead https://xpenogen.github.io/serial_generator/index.html how can i create s/n for a new machine i got ? cheers
  10. bare metal loader 1.01 works fine but high availability setup gives me error, it says i have to disable dhcp server while its already disabled and wont let me setup the high availability, the rest seem to work fine.
  11. You are right i must check that how do i add something to be run on boottime on xpenology ? Cheers
  12. using xpenology on x2 qnap's ts-459u work great better than production grade whoever uses qnaps like me only use 5.2-5592.2 update 4, later versions dont work i tried everything.
  13. solved the issue by adding this routing table route add -net 192.168.100.0 netmask 255.255.255.0 dev eth1:HA ip route flush cache login as: root root@cluster's password: BusyBox v1.16.1 (2015-06-29 18:21:52 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. cluster> ip route list default via 192.168.100.1 dev eth1 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.197.22 169.254.1.0/30 dev eth0 proto kernel scope link src 169.254.1.2 192.168.100.0/24 dev eth1 scope link src 192.168.100.200 192.168.100.0/24 dev eth1 scope link
  14. asterisk worked flawlessly while i had it on standalone function on the single nas only in cluster ip it seems to have a problem it again works flawlessly if i use the nas lan card ip, it only cant find asterisk if i use the redundant floating ip all other services such as dns radius mariadb etc work flawlessly with the floating ip only asterisk has problem the phones time out they cannot find the server if phone tries to connect to the floating ip but in the nas direct ip it connects great. This is beyond me really as both ips floating and the nas one are on the same machine whil