V9, linux, getting the band back together

[BobPhoenix]

Originally Posted by EnterNoEscape

That's what I would do. Just mount whatever you need on some folders under /mnt. I don't have a lot of faith in "smart" automated mounting solutions, so I always use fstab.

That is what I did. I even symlinked to the location SageTV was trying to mount automatically. Most of the time it worked but I found that my /mnt's were becoming unmounted unless I did a "mount -A" periodically. The symlinks would end up messed up as well. I wanted the paths to exactly match my Windows box so I could switch back and forth if needed. Haven't been using my linux install since I found my slow boot up times for the service were due to a bad wiz.bin. Went from 3+ hours for the server to show up in placeshifter to ~10 minutes when I blew away the wiz.bin and started over from scratch and reentered all my favorites again. So haven't really been motivated to switch back to Linux but am still planing on it once my job search is over.

[Narflex]

The pull request for the smbmount change is merged...I figured GitHub would send me another email after changes were made to it that I requested but it didn't...so I forgot about it...sorry...merged now though.

[BobPhoenix]

Originally Posted by Narflex

The pull request for the smbmount change is merged...I figured GitHub would send me another email after changes were made to it that I requested but it didn't...so I forgot about it...sorry...merged now though.

Thank you.

[SageWizdom]

Originally Posted by cat6man

i see the name of the sage server both times, but with the linux server the hd200 does not seem to have an ip address.

could there be a firewall port that needs to be opened?
on the other hand, the clients do find the linux server and connect.

Can you verify what ports you have open or not open? Did you specifically enable iptables or another firewall tool (ex. ufw), or are you assuming something turned on automatically? At the core is iptables.

sudo iptables -S

The above command will either spit out lots of fun gibberish like text with the firewall configuration if your firewall is configured, or on a machine with a disabled firewall, you would get...

$ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT

I believe you will get the above, even if your firewall is configured but disabled. (in my test machine I did, but I'm not certain if this is always true)

If your firewall is on, you need to open ports... you can run the following

sudo ufw allow proto tcp to any port 22 2>/dev/null
sudo ufw allow proto tcp to any port 7760 2>/dev/null
sudo ufw allow proto tcp to any port 7818 2>/dev/null
sudo ufw allow proto tcp to any port 8018 2>/dev/null
sudo ufw allow proto tcp to any port 8080 2>/dev/null
sudo ufw allow proto udp to any port 8271 2>/dev/null
sudo ufw allow proto tcp to any port 31099 2>/dev/null
sudo ufw allow proto udp to any port 31100 2>/dev/null
sudo ufw allow proto tcp to any port 42024 2>/dev/null

sudo iptables -I INPUT -p udp -m udp --sport 65001 -j ACCEPT

There is an issue in the auto script where the install does not appear to return, so the end of the script does not always seem to run.