Okay. Somewhat unique situation. I have two network cards in my old PC
(which talk to two different networks). I will be moving the PCI ethernet
card over to my new computer permanently.
The default is for it to assign eth0 to the PCI card and eth1 to the one on
the motherboard.
I am
Under centos/redhat, I know I have seen a few that lock the MAC address to the
specific eth device. It was part of a config file. Caused all kinds of
annoyance when cloning machines and the mac would change and then the eth would
be incremented and the network wouldn't come up.
I know that
- Original Message -
Okay. Somewhat unique situation. I have two network cards in my old PC
(which talk to two different networks). I will be moving the PCI
ethernet card over to my new computer permanently.
The default is for it to assign eth0 to the PCI card and eth1 to the
one on
On 03/19/2013 07:48 AM, Paul Boniol wrote:
Okay. Somewhat unique situation. I have two network cards in my old PC
(which talk to two different networks). I will be moving the PCI
ethernet card over to my new computer permanently.
The default is for it to assign eth0 to the PCI card and eth1
Trick: set module aliases for ethernet drivers to be the device name
you want. Simply editing the config (RedHat/CentOS) and changing the MAC
will not do this. I think it is modprobe.conf:
alias e1000 eth3
alias bt999 eth2
Then you can use system-config-networking or simply edit your
Okay guys,
All of my extensive DHCP configuration experience (which fits on the
back of a personal check sized envelope) has been sought by one of our
customers (me and my big mouth). You see, they have Cisco ASA 5510
firewalls which do DHCP but not reserved IPs which we need to keep these
Is there a 24/7 Linux server at each location?
Alternatively, is it possible to set static IPs on the printers?
Curt
On Tue, Mar 19, 2013 at 2:53 PM, Howard White hwh...@vcch.com wrote:
Okay guys,
All of my extensive DHCP configuration experience (which fits on the back
of a personal check
On a re-read, what about a Raspberry Pi in a suitable case? Saw an
aluminum milled case (think: costs more than the Pi) on adafruit. I
brought mine up without ever connecting the HDMI, just applied power and
observed what address it was given, then made an SSH connection. From that
point you've
Do you need to push new DHCP configurations out to each location or do you
just need to be able to remotely access and update DHCP at each location?
I'm wondering if a $50 router with DD-WRT might be sufficient (if you're
working with businesses with $50 budgets...)
Chris
On Tue, Mar 19, 2013
On 03/19/2013 03:03 PM, Curt Lundgren wrote:
Is there a 24/7 Linux server at each location?
Alternatively, is it possible to set static IPs on the printers?
Curt
Sigh,
I seek this small footprint, no moving parts linux box to be the 24x7
linux box at each remote location.
We _HAVE_ set
Do you have a budget? Do you have any other needs that this linux box
needs to address? If DHCP is the only thing you need, I'd feel more
comfortable with a small, solid-state device than a full hardware and
software system to support.
Chris
Chris
On Tue, Mar 19, 2013 at 3:10 PM, Howard
On 03/19/2013 03:09 PM, Chris McQuistion wrote:
Do you need to push new DHCP configurations out to each location or do
you just need to be able to remotely access and update DHCP at each
location?
I'm wondering if a $50 router with DD-WRT might be sufficient (if you're
working with businesses
What about a Mikrotik device? Small, cheap, and no moving parts. Has
a learning curve if you've never used one, but it's fairly easy to get
the hang of it.
--
--
You received this message because you are subscribed to the Google Groups
NLUG group.
To post to this group, send email to
On 03/19/2013 03:12 PM, Chris McQuistion wrote:
Do you have a budget? Do you have any other needs that this linux box
needs to address? If DHCP is the only thing you need, I'd feel more
comfortable with a small, solid-state device than a full hardware and
software system to support.
Chris
I'm not suggesting you have the DD-WRT device doing firewall or routing.
You can simply have it sitting in your network, dishing out DHCP
(including reservations). Clients would still route as they always have.
They would just have this little solid-state device doing DHCP, as opposed
to the
On 03/19/2013 03:56 PM, Blake Dunlap wrote:
What's wrong with just central dhcp relay?
-Blake
The only problem is the implementor - me :)
I'll look for that, Blake.
Howard
--
--
You received this message because you are subscribed to the Google Groups
NLUG group.
To post to this group,
+1 on the router. Raspberry Pi devices are great except that you can't
find them and when you do you'll have to do a lot of setup (hardware and
software). Getting openwrt or ddwrt on an off-the-shelf router has a lot
of advantages, including the fact that if the hardware craps (which is
rare)
Not to argue the point about the Pi - last week when I was browsing
adafruit they had the Pi in stock (albeit not at list price.)
On Tue, Mar 19, 2013 at 5:07 PM, Michael Chaney
mdcha...@michaelchaney.comwrote:
+1 on the router. Raspberry Pi devices are great except that you can't
find them
You can get one off ebay tomorrow if you're willing to pay. I'm not sure
why you would buy one of those when you can get a router off the shelf at
Walmart right now or at 3AM or whenever it breaks.
On Tue, Mar 19, 2013 at 5:09 PM, Curt Lundgren verif...@gmail.com wrote:
Not to argue the point
You still have the added management overhead for consumer devices running a
standalone dhcp server which have to be kept operational and monitored. If
he doesn't have server infrastructure at the sites that the dhcp daemon can
be dropped on, he's better off relaying it to where it can be properly
I would probably go with any piece of consumer or business grade hardware
wifi router that has at least the number of wired ports you need at each
branch for your printers.
Thus the router creates a new private LAN typically 192.168 or 10 x for
the devices physically attached to the router.
21 matches
Mail list logo
