LEA (LowEndAdmin) is the original founder of LowEndBox and the visionary who gave rise to an entire movement around minimalist, efficient hosting. In 2008, LEA launched LowEndBox with a simple but powerful idea: that it was possible to run meaningful applications, web servers, VPNs, mail servers, and more – on small, low-cost virtual machines with minimal resources.
At a time when most infrastructure discussions were dominated by high-end servers and enterprise platforms, LEA championed the opposite approach: lightweight Linux distros, self-managed servers, open source software, and thoughtful optimization. This philosophy gave birth to the term “Low End Box”, which would come to define a new genre of hosting tailored to developers, tinkerers, and budget-conscious users around the world.
Through LowEndBox and its companion forum, LowEndTalk, LEA built the foundation for what would become one of the most active and enduring communities in the hosting world, prioritizing knowledge-sharing, transparency, and accessibility.
After several years of nurturing the site and community, LEA stepped away from active involvement, passing the torch to a new generation of admins, contributors, and moderators. Today, LEA remains a respected figure in the LowEnd ecosystem, credited with launching a platform and philosophy that continues to influence thousands of infrastructure providers and users globally.
LowEndBox’s legacy, and its thriving community, is a direct result of LEA’s original vision.
Hi, I’ve rented this offer from echoservers, for me, it works, but I’m new to vpss though, I had to reinstall the OS 20 times, to learn, and everything works fine, I’m not sure I can judge the speed etc, because I’m a total noob, but everything went smooth after learning things, so, I can say, echoservers vps is cool!
@bogacaeghin:
THis looks like a really good hosting provider.
I asked them some pre-sales questions on Nov 6th. But the answer to 2 questions made me back out.
One of them is about a quote for a custom config of the VPS Hosting 5 plan. lowering the monthly bandwidth from 5TB to 1TB would shave off only $5 off the monthly price. That’s something I’m not going to argue, it’s their calculation, and I either have to take it ot leave it.
But the other thing that bugs me was their reply to my request about iptables. I mentioned the ones I needed in my question. And this was their reply :
“We do allow some of the iptables modules but not all of them. What do
you need iptables for specifically? We have advanced hardware
firewall rules to help mitigate attacks. You might want to consider
some of our Xen options if you need highly configurable kernel
options.”
So I have to justify my iptables usage first, or take a $30 more expensive XEN plan to be able to load some iptables kernel modules and load my iptables rules set.
Long story short.
Are you using iptables with your echoservers plan ?
And if yes, are you loading your own rules set, and does it work ?
I’ve been wondering the same thing as Robert, on a XEN VPS I would use ‘ufw’ to easily configure iptables for me, but this doesn’t work on OpenVZ, nor do some iptables rules. If anyone knows how to get this working with OpenVZ please let us know.
On OpenVZ not all kernel modules are yet virtualized (at least not around this time last year when I checked their wiki.)
Especially the iptables kernel modules had problems, ipt_LOG for example will not log even when enabled.
Try if you can display the file /etc/vz/conf/vspid.conf (where vpsid = a number e.g. 100.cnf) and see a line starting with IPTABLES = . Your iptables kernel modules (to be virtualized and enabled) should be listed after the equal sign.
(You probably will not have access to this file as it is a configuration file of your VPS.)
Also check if you have this file : /etc/sysconfig/iptables-config and if it contains aline starting with IPTABLES_MODULES = .
And check file /etc/sysconfig/vz for a line starting with IPTABLES = .
Any changes you make to these files would have you to issue these commands:
service vz stop
service iptables restart
service vz start
But I also read on the OpenVZ wiki that removing all iptables lines, causes all iptables kernel modules to be virtualized. And because the list of virtualized iptables kernel modules is frequently changing, this is apparently the best way.
But I don’t know for sure, because with another host I was with they had to add the iptables kernel modules to my VE configuration files for ip connection tracking and status matching to work.
Some of the iptables kernel module names are:
ip_tables ipt_REJECT ipt_tos ipt_TOS ipt_LOG ip_conntrack ip_conntrack_ftp ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp ip_conntrack_netbios_ns ipt_LOG
I guess they know about this mess over at echoservers, and don’t want to waste their time with it.
Sorry for late reply, well, for me, it works fine, I’m not into iptables etc, and I’m not usin it for so much detailed, just messing with it, settings up things, mostly for learning, but I’m fine with their system
I re-read that last sentence in my previous comment.
“I guess they know about this mess over at echoservers, and don’t want to waste their time with it.”
But I did not mean that it is a mess at echoservers.
I meant to say that echoservers probably is aware of the mess iptables are/were with OpenVZ about a year ago.
If you don’t use iptables and completely rely on the (hardware) firewall echoservers has setup, obviously you will not have any worries about iptables.