I've used mpd3 for a long time now and I switched to mpd4 a few days ago (using 6-STABLE, i386).
mpd4 is controlling a PPPoE A-DSL connection. mpd connects just fine when started but when the 24 hours disconnect appears, mpd4 won't reconnect automagically (as mpd3 did). I've already checked the docs and inserted a max-redial 0 statement but this did not solve the problem. I can easily (manually) send a USR1 signal to mpd4 and it will reconnect.
Using mpd3 I haven't had this kind of problem. After 24 hours disconnect it took 5 seconds to have mpd been reconnected.
My mpd.conf looks like (only relevant lines):
new -i ng1 callando_dsl PPPoE
set iface addrs 10.0.0.1 10.0.0.2
set iface route default
set iface disable on-demand
set iface idle 0
set iface session 0
set iface enable tcpmssfix
set bundle disable multilink
set auth authname "...."
set link no acfcomp protocomp
set link disable pap chap
set link accept chap
set link mtu 1492
set link keep-alive 10 60
set link max-redial 0
set ipcp yes vjcomp
set ipcp ranges 0.0.0.0/0 1.2.3.4/0
set iface up-script /usr/local/etc/mpd4/iface-up.sh
set iface down-script /usr/local/etc/mpd4/iface-down.sh
open link
This config is copied over from my older working mpd3 and modified a bit.
I thought setting idle 0, disable on-demand and max-redial 0 will do it but this is not the case (disconnected w/o reconnect a few minutes ago).
Any hints how I do get mpd4 to automagically reconnect on connection drop?
Greetings,
Volker
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This option should be included in the PPPoE example in mpd.conf, or mentioned at least!
I've played senselessly with max-redial too.
The retry option should be mentioned in the max-redial description.
BTW: "no noretry"? What about an option like "set bundle retry"? "no no" is a no-no! ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys,
I've used mpd3 for a long time now and I switched to mpd4 a few days ago (using 6-STABLE, i386).
mpd4 is controlling a PPPoE A-DSL connection. mpd connects just fine when started but when the 24 hours disconnect appears, mpd4 won't reconnect automagically (as mpd3 did). I've already checked the docs and inserted a max-redial 0 statement but this did not solve the problem. I can easily (manually) send a USR1 signal to mpd4 and it will reconnect.
Using mpd3 I haven't had this kind of problem. After 24 hours disconnect it took 5 seconds to have mpd been reconnected.
My mpd.conf looks like (only relevant lines):
new -i ng1 callando_dsl PPPoE
set iface addrs 10.0.0.1 10.0.0.2
set iface route default
set iface disable on-demand
set iface idle 0
set iface session 0
set iface enable tcpmssfix
set bundle disable multilink
set auth authname "...."
set link no acfcomp protocomp
set link disable pap chap
set link accept chap
set link mtu 1492
set link keep-alive 10 60
set link max-redial 0
set ipcp yes vjcomp
set ipcp ranges 0.0.0.0/0 1.2.3.4/0
set iface up-script /usr/local/etc/mpd4/iface-up.sh
set iface down-script /usr/local/etc/mpd4/iface-down.sh
open link
This config is copied over from my older working mpd3 and modified a bit.
I thought setting idle 0, disable on-demand and max-redial 0 will do it but this is not the case (disconnected w/o reconnect a few minutes ago).
Any hints how I do get mpd4 to automagically reconnect on connection drop?
Greetings,
Volker
"max-redial 0" only means infinite connection retries, but not reconnects.
Add
set bundle no noretry
to your config file.
It's default was changed in 4.1.
Alexander,
> "max-redial 0" only means infinite connection retries, but not reconnects.
> Add
> set bundle no noretry
> to your config file.
thanks for clarification and your hint. I've added this to my config and will see if now behaves greatly as mpd3 did.
> It's default was changed in 4.1.
hmm, it seemes I've missed that setting in the docs.
Again, thanks for your fast reply.
Greetings,
Volker
This option should be included in the PPPoE example in mpd.conf, or mentioned at least!
I've played senselessly with max-redial too.
The retry option should be mentioned in the max-redial description.
BTW: "no noretry"? What about an option like "set bundle retry"? "no no" is a no-no! ;)