For those who want to give this a go, try renaming the interfaces on the first boot before going through the first boot wizard. That should help reduce (and possibly eliminate) configuration file hacking.
Port forwarding the port used by your Bittorrent client is usually all that is required. In other words, all you need is a single port forwarding rule to the IP address of your VM instance.
Some extra work with ebtables is required to get this working and there is some documentation on the topic here. I don't know how complete the documentation is, but I do know that this has been implemented for ClearBOX/ClearCenter clients.
Thanks Marcel and Wayne! We were busy with the Canadian long weekend I try to catch most of the forum threads, but if I fall more than a couple of days behind, things start to get missed.
Scott wrote: Hi, I understand that this app is still Beta, but is there going to be documentation on how to mount Multiple Hard drives and/or network drives? or was this kinda explained already and I need to get a better handle on how drives are mounted and that /storage will work all devices (sigh).
There's good documentation on how to mount drives somewhere on the Internet, it's just a matter of finding the document and linking to it
By default, the Storage Manager only uses one storage target. However, you can override the "configlets" to implement multiple storage targets (e.g. storage for the web proxy on disk1, storage for Flexshare on disk2). There's a mini-example mentioned in the Configlets section of the Technical Guide.
Add "Connection Type" of "none" to list - ie: This would allow the ability to have an interface configured, but specify that it should NOT have an IP address. While there are probably many reasons for doing this, the most common one would be for when VLANs are configured, and one does not wish to use the base interface (ie: ethX) untagged. ie: I might wish to specify each VLAN on eth0 as tagged (ie: eth0.1, eth0.2, etc) without having eth0 itself to have an IP. This can be done by having "BOOTPROTO=none" and NOT specifying an IPADDRESS=line (and NETMASK, etc) at all.
Good idea -- added to the tracker: tracker.clearfoundation.com/view.php?id=1145
(also useful to set IPV6INIT=no and IPV6_AUTOCONF=no, but I don't do this, don't use IPv6 at all myself).
I'm sure that will be part of the IPv6 initiative in ClearOS 6. That reminds me, I need to go request my address block from my ISP!
Oh, and BTW - if you were to add the ability to stop/start an interface from web config (per my prior suggestions), I would recommend that if the user clicks this on the physical interface (ie: ethX) that also has VLANs configured (ethX.Y), that the app would warn the user that "Stopping or restarting a physical interface will stop or restart all VLANs configured on that interface. It you are accessing this webpage from one of those VLANs, this may disconnect you. Would you like to continue?"
Noted!
We've had it with the performance of the forums and are now actively looking at alternatives. 400 database queries to load the main forum page is just ridiculous! The blog software is also broken and the URL rewrite engine (sh404SEF) is a horror show. Other bits of ClearFoundation infrastructure are okay (though the translation server is sluggish too):
Our mirror system is well designed to get updates out quickly, but it suffers from two weaknesses:
- If an update fails high up on the mirror hierarchy, the mirrors further down the line are marked as "offline". This increases the load on the higher mirrors which in turn might get overloaded and taken offline. Aaaaand death spiral. That's exactly what happened a few days ago.
- For most mirrors, all you need is rsync and cron. ClearFoundation's mirrors are more complex to configure and it has been hard to convince potential mirror hosts to bit the bullet.
I think being able to show the MAC address for each interface would be EXTREMELY helpful, as would (which I didn't mention before) showing the network driver name (ie: "ASIX USB Ehternet Adapter" or "r8169 Gigabit Ethernet driver", etc). This would help one to find out (without dropping to the shell or messing with network cables) which NIC actually got mapped to which device.
I added an enhancement request to the tracker: tracker.clearfoundation.com/view.php?id=1142
BTW - one question - I haven't looked at this much in COS 6.4, but do we still have to do the EXTRALANS= thing that was required in COS 5.2 to have COS route between LANS? (at the time it was in /etc/system/network, though looks like now its /etc/clearos/network.conf). This would also be nice if web admin would ask about and configure for you.
Yes, that command line parameter is still around. And yes, adding "static route manager" is on the todo list too!
I try to catch most of the forum threads, but if I fall more than a couple of days behind, things start to get missed.
