From what I understand of the current client/server/forwarder split
there's no way to get ahcp working across multiple physical networks...
I'm not sure what you mean. Getting configuration to work across
multiple links is exactly what AHCP was designed to do.
Perhaps the confusion stems from
On Tue, Jul 2, 2013 at 11:50 AM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
From what I understand of the current client/server/forwarder split
there's no way to get ahcp working across multiple physical networks...
I'm not sure what you mean. Getting configuration to work
Perhaps the confusion stems from the dodgy documentation, which
doesn't make it clear that *all* AHCP nodes act as forwarders, whether
they also act as clients or servers.
Yes,
Since I have no plans for a release, I'll add this to the FAQ.
Where I had run into trouble was a more limited
By the way, Juliusz, I believe that ahcpd does not reassign an
address to the interface when it goes up again, but I've had a hard
time reproducing the issue. Is it a case it should handle correctly
in theory, or a shortcoming of the implementation?
Confirmed. Ahcpd doesn't monitor
On Sun, Jun 30, 2013 at 09:01:30PM +0200, Juliusz Chroboczek wrote:
If you want to try your hand at fixing it, it's check_network in
ahcpd.c. Note that the natural solution is racy (an interface could
go down-up before ahcpd notices), and the right solution is quite
a bit of work (it would
On Mon, Jul 01, 2013 at 11:56:50AM +0200, Baptiste Jonglez wrote:
On Sun, Jun 30, 2013 at 09:01:30PM +0200, Juliusz Chroboczek wrote:
If you want to try your hand at fixing it, it's check_network in
ahcpd.c. Note that the natural solution is racy (an interface could
go down-up before ahcpd
On Mon, Jul 1, 2013 at 2:56 AM, Baptiste Jonglez
baptiste.jong...@ens-lyon.fr wrote:
On Sun, Jun 30, 2013 at 09:01:30PM +0200, Juliusz Chroboczek wrote:
If you want to try your hand at fixing it, it's check_network in
ahcpd.c. Note that the natural solution is racy (an interface could
go
7 matches
Mail list logo