Anyone else using ClearOS and having trouble getting dhcp on an external port?
-
So, the software I use to do the routing around here decided that it doesn't want to get a dhcp address. When I try to start the interface manually I get this:
ifup eth2 Determining IP information for eth2.../etc/sysconfig/network-scripts/ifup-eth: line 294: 8441 Terminated /sbin/dhclient ${DHCLIENTARGS} ${DEVICE}ClearOS is based on CentOS. Maybe time to look for something else?
-
We've got 2 internet connections, and the other one is a static IP that is working just fine.
-
Why ClearOS instead of CentOS itself in this scenario?
-
Maybe show us the ifcfg-eth2 file?
-
@scottalanmiller said:
Why ClearOS instead of CentOS itself in this scenario?
Honestly, it was originally a 20 minutes to get running, which is a lot less time than it'd take me to figure out how to do everything myself. This might just be the sign that it's time to start a DIY project to take over.
-
Hmmm.... if you search on this error, ClearOS comes up right away. That's not proof or anything, but that such an uncommon OS comes up with this error twice (and CentOS not at all) points to this likely being something about ClearOS that is the problem.
-
What happens if you run dhclient eth2 ?
-
@travisdh1 said:
@scottalanmiller said:
Why ClearOS instead of CentOS itself in this scenario?
Honestly, it was originally a 20 minutes to get running, which is a lot less time than it'd take me to figure out how to do everything myself. This might just be the sign that it's time to start a DIY project to take over.
My worry with things like ClearOS is that it is the Jurassic Park Effect. They take an enterprise platform with the best enterprise support in the business, the broadest expert community support, the most industry experience and knowledge... and layer tons of small time, one off stuff on top of it making the system more fragile, complex and unknown.
Or like a front wheel drive car... it makes it too easy to get moving but when something goes wrong, you are moving beyond your ability to control.
It's the opposite of what you want. You want hard to get up and running and easy and reliable to support. Rather than easy to get running and hard to support. You want all of the risk and effort to exist because it goes into product rather than the opposite (just like you want to have your problems with your car when at a stand still on ice, not once you are up to speed and then find out things are dangerous.)
-
@scottalanmiller said:
Hmmm.... if you search on this error, ClearOS comes up right away. That's not proof or anything, but that such an uncommon OS comes up with this error twice (and CentOS not at all) points to this likely being something about ClearOS that is the problem.
ClearOS also has a huge Attack surface, lots of extras for no reason.
-
I'm thinking next week will be starting with me building a CentOS router from the ground up. While I know how to do most of it, I'm going to look for a good set of instructions first.
-
@travisdh1 said:
I'm thinking next week will be starting with me building a CentOS router from the ground up. While I know how to do most of it, I'm going to look for a good set of instructions first.
Why use a "build your own" Linux router? Why are you not using a hardware router or, at the very least, a router OS like VyOS?
-
@scottalanmiller said:
@travisdh1 said:
I'm thinking next week will be starting with me building a CentOS router from the ground up. While I know how to do most of it, I'm going to look for a good set of instructions first.
Why use a "build your own" Linux router? Why are you not using a hardware router or, at the very least, a router OS like VyOS?
VyOS? I'll have to check that out. Mostly because the other software routers I know of are just more of that Jurassic Park Effect you were talking about @scottalanmiller.
-
@travisdh1 said:
VyOS? I'll have to check that out. Mostly because the other software routers I know of are just more of that Jurassic Park Effect you were talking about @scottalanmiller.
Who makes a software router other than VyOS? Everything else is a full OS that isn't meant to be a router just routing in additional to being a general purpose OS. VyOS is the only software router I would consider (and the only one I have considered for a decade now.)
Why a software router? Is this in a VM?
-
VyOS is the reason that I fell in love with Ubiquiti. They build hardware to run VyOS on, which is exactly what I wanted. Full stack hardware support (and a MIPS RISC board) for VyOS. VyOS is to routing what normal Linux is to servers.
-
@scottalanmiller said:
@travisdh1 said:
VyOS? I'll have to check that out. Mostly because the other software routers I know of are just more of that Jurassic Park Effect you were talking about @scottalanmiller.
Who makes a software router other than VyOS? Everything else is a full OS that isn't meant to be a router just routing in additional to being a general purpose OS. VyOS is the only software router I would consider (and the only one I have considered for a decade now.)
Why a software router? Is this in a VM?
Sure is. Not the ideal I know, but it had been working well.
-
@travisdh1 said:
@scottalanmiller said:
@travisdh1 said:
VyOS? I'll have to check that out. Mostly because the other software routers I know of are just more of that Jurassic Park Effect you were talking about @scottalanmiller.
Who makes a software router other than VyOS? Everything else is a full OS that isn't meant to be a router just routing in additional to being a general purpose OS. VyOS is the only software router I would consider (and the only one I have considered for a decade now.)
Why a software router? Is this in a VM?
Sure is. Not the ideal I know, but it had been working well.
Not so bad in a VM, presumably behind the "real" firewall and only firewalling internal systems from each other. Still, VyOS is much lighter. Runs nothing that isn't needed and is a customer platform for routing, rather than tacking routing on top of an already bloated system.
-
VyOS configuration style would remind you of Cisco IOS.
-
@scottalanmiller said:
VyOS configuration style would remind you of Cisco IOS.
Time to dive into something new then, off I go.
-
@scottalanmiller said:
VyOS is the reason that I fell in love with Ubiquiti. They build hardware to run VyOS on, which is exactly what I wanted. Full stack hardware support (and a MIPS RISC board) for VyOS. VyOS is to routing what normal Linux is to servers.
VyOS is pretty similar to Cisco IOS too. (without the cost)
-
Instead of wandering around the actual issue as @scottalanmiller is doing.
How about we ask a related question or two?
First, what version of ClearOS? 5.2 was rock solid and stable. 5.2 was based on CentOS.
ClearOS 6 was a mess. They chose to break off of CentOS and moved to their own distro.I still have a 5.2 system out there running just fine.
