2009/10/24 Warren Selby wcse...@selbytech.com
What I do is run virtual interfaces on one box, and run multiple instances
of atftpd inside xinetd,
Great idea !
I didn't know it could be possible to run several instances of xinetd, each
binded to a specific IP address.
Is this specific to
Great idea !
I didn't know it could be possible to run several instances of xinetd, each
binded to a specific IP address.
Is this specific to xinetd or does openbsd-inetd also support this feature ?
Anyway, I'll check this in openbsd-inetd doc myself and (hopefully) report
my findings here.
2009/10/24 Dave Platt dpl...@radagast.org
xinetd will let you do multiple bindings of a single port, with a
single instance of xinetd running.
...
As far as I know, standard BSD (and Linux) inetd doesn't have
this capability.
Good to know !
Thanks for the pointer !!
Testing xinetd is
On Sat, 24 Oct 2009, Dave Platt wrote:
xinetd will let you do multiple bindings of a single port, with a single
instance of xinetd running.
You would define two service entries in the config file, with the same
service name, different ids (e.g. tftp1 and tftp2), and different
bind
On Thu, Oct 22, 2009 at 10:50:29PM +0200, Benny Amorsen wrote:
Olivier oza-4...@myamail.com writes:
Most (if not all) IP phones support provisioning through DHCP/TFTP.
The trouble is some phones seem to require to store their config files in
TFTP root directory.
A lot of IP phones
Steve Edwards asterisk@sedwards.com writes:
atftpd can do PCRE substitutions to transform a requested file name into
something else. I've not used this facility, but I'm guessing you could
transform:
SIPDefault.cnf - cisco/SIPDefault.cnf
sip.cfg - polycom/sip.cfg
Steve Edwards asterisk@sedwards.com writes:
atftpd can do PCRE substitutions to transform a requested file name
into something else. I've not used this facility, but I'm guessing you
could transform:
SIPDefault.cnf - cisco/SIPDefault.cnf
sip.cfg - polycom/sip.cfg
What I do is run virtual interfaces on one box, and run multiple instances
of atftpd inside xinetd, each one bound to a different IP and a different
root directory. Thus, my file structure looks like this -
/home/phones/
/home/phones/cisco/
/home/phones/cisco/7960 (root directory for one of the
Olivier wrote:
Hi,
Most (if not all) IP phones support provisioning through DHCP/TFTP.
The trouble is some phones seem to require to store their config files in
TFTP root directory.
This makes this TFTP root directory a bit messy.
What are the best practices or tricks to manage this TFTP
On Thu, 2009-10-22 at 11:15 -0400, Dave Fullerton wrote:
#2 might be possible, but there's a lot of depends on factors.
The ISC dhcpd often packaged in linux distributions has the ability to
specify different dhcp options to different pools of addresses. You
can then assign clients to
2009/10/22 Jared Smith jsm...@digium.com
On Thu, 2009-10-22 at 11:15 -0400, Dave Fullerton wrote:
#2 might be possible, but there's a lot of depends on factors.
The ISC dhcpd often packaged in linux distributions has the ability to
specify different dhcp options to different pools of
Olivier oza-4...@myamail.com writes:
Most (if not all) IP phones support provisioning through DHCP/TFTP.
The trouble is some phones seem to require to store their config files in
TFTP root directory.
A lot of IP phones support HTTP instead of TFTP. This helps, because it
is fairly easy to
On Thu, 22 Oct 2009, Benny Amorsen wrote:
A lot of IP phones support HTTP instead of TFTP. This helps, because it
is fairly easy to write a script which dynamically generates the
configuration.
Someone really ought to write a TFTP daemon with the same feature... Or
a TFTP plugin for apache
13 matches
Mail list logo
