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 got a nice headless server and if you direct its log traffic to an external server you aren't quickly wearing out the flash card (if that's a concern.)
I have a Perl script checking every few seconds the modification timestamp of the /etc/dhcpd.conf (on my distro, anyway). When it changes, a restart of DHCPD takes place. Pretty much hands-off. Curt On Tue, Mar 19, 2013 at 3:03 PM, Curt Lundgren <verif...@gmail.com> wrote: > 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 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 ~!@#$%^ printers >> from jumping ship. >> >> Were this one location, no problem. Load dhcpd on the application >> server, turn off dhcp on the ASA, and go. But they have multiple >> locations, each behind their own firewalls. Yes, I know how to configure >> one DHCP server for multiple subnets but I am concerned for the distributed >> network topology. >> >> My question is about hardware. Looking for a small device booting from >> solid state media (USB but not USB...) so that I may have a linux DHCP >> server at each location in place of the ASA. Would be even more cool if I >> could cascade DHCP from the main server to the remotes (yes I remember >> Tilghman talking about having multiple DHCP servers). I think I want a >> local "presence" at each location within the respective firewalls, if for >> no other reason than WAN meltdowns. >> >> I guess I really should try turning off DHCP on all of the ASAs and try >> to run DHCP for all of the subnets of the main server. >> >> Howard >> >> -- >> -- >> You received this message because you are subscribed to the Google Groups >> "NLUG" group. >> To post to this group, send email to nlug-talk@googlegroups.com >> To unsubscribe from this group, send email to nlug-talk+unsubscribe@** >> googlegroups.com <nlug-talk%2bunsubscr...@googlegroups.com> >> For more options, visit this group at http://groups.google.com/** >> group/nlug-talk?hl=en <http://groups.google.com/group/nlug-talk?hl=en> >> >> --- You received this message because you are subscribed to the Google >> Groups "NLUG" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to >> nlug-talk+unsubscribe@**googlegroups.com<nlug-talk%2bunsubscr...@googlegroups.com> >> . >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> >> > -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to nlug-talk@googlegroups.com To unsubscribe from this group, send email to nlug-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to nlug-talk+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
