emerge freeradius failed on gentoo:
>>> Test phase [not enabled]: net-dialup/freeradius-1.1.1-r1
>>> Install freeradius-1.1.1-r1 into /var/tmp/portage/freeradius-1.1.1-r1/image/ category net-dialup
* ‘enewgroup()’ called from ‘install()’ which is not a pkg_* function.
* Package fails at QA and at life. Please file a bug.
!!! ERROR: net-dialup/freeradius-1.1.1-r1 failed.
!!! Function enewgroup, Line 648, Exitcode 0
!!! Bad package! enewgroup is only for use in pkg_* functions!
!!! If you need support, post the topmost build error, NOT this status message.
Bandwidth Throttling on Linux
To setup bandwidth throttling on linux, you can use advanced linux routing techniques. Install a package called iproute2, and it should include the "tc" binary command.
tc - traffic control
Traffic control on linux is done using the tc command. It can setup kernel packet queuing management disciplies, and you have incredible control over how the packets are released to the network. You can also have limited control over incoming packets using an ingress queue.
My tc notes
TBF is causing rsync and scp to report back very low transfer rates. Something with this is not right because Fugu, an SCP client reports accurate transfer rates.
External tc - related links
http://snafu.freedom.org/linux2.2/iproute-notes.html
http://www.opalsoft.net/qos/
There are some good websites on OpenVPN. One of course being the OpenVPN website itself.
I am using tun instead of tap. From what I gathered, tun allows you to use NAT instead of bridging, which is what TAP uses.
Tun is a virtual device like eth0. So whenI set this up, I had to edit my firewall and network address translation (NAT) / ip_masquerade rules to provide for the new device. So far things are looking good.
One thing that really impresses me about OpenVPN is its speed. It is very fast!
The configuration can be a little tricky, thought I think with some planning and thinking, we can get clients connected easily.
* When I connected to OpenVPN from home over this past weekend, I accidentally took down the LAN. Was it because tun0-00 had the same ip # as the LAN gateway - eth1? Stopping the OpenVPN fixed the problem.
Latest Comments
RSS