| Message ID | 1510494527-4816-2-git-send-email-tim@tn-x.org |
|---|---|
| State | Accepted |
| Headers | show |
diff --git a/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred b/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred index e09281e..3df6764 100644 --- a/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred +++ b/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred @@ -6,7 +6,7 @@ uci batch <<EOF set alfred.alfred=alfred set alfred.alfred.interface='br-mesh' set alfred.alfred.mode='slave' - set alfred.alfred.batmanif='bat0' + set alfred.alfred.batmanif='none' set alfred.alfred.start_vis='0' set alfred.alfred.run_facters='0' EOF
hi Tested-by: Christian Dresel <fff@chrisi01.de> auf einen wr1043 v2 leider ist die Situation für #74 nicht aufgetreten (configurehood wurde schneller fertig als Alfred startet) würde aber behaupten das es das Problem behebt. Sonst läuft Alfred damit problemlos. Reviewed-by: Christian Dresel <fff@chrisi01.de> mfg Christian On 12.11.2017 14:48, Tim Niemeyer wrote: > During system boot, the dependency of alfred to the bat0 > interface is problematic. In some circumstances (no eth mesh > and no wifi mesh), the mesh interfaces are disabled, the > bat0 interface is removed and the station mode is entered. > > Because alfred is started after the station mode (current > boot order), it doesn't start up with the missing bat0 interface. > > Signed-off-by: Tim Niemeyer <tim@tn-x.org> > --- > > Changes in v2: > - Based on uci-defaults patch > > src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred b/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > index e09281e..3df6764 100644 > --- a/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > +++ b/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > @@ -6,7 +6,7 @@ uci batch <<EOF > set alfred.alfred=alfred > set alfred.alfred.interface='br-mesh' > set alfred.alfred.mode='slave' > - set alfred.alfred.batmanif='bat0' > + set alfred.alfred.batmanif='none' > set alfred.alfred.start_vis='0' > set alfred.alfred.run_facters='0' > EOF
Hallo, ich habe regelmäßig Probleme mit Mesh-Routern, die ich auf V2 aktualisiere und die dann nicht sofort den configap finden. Manchmal liefert alfred -r 64 einfach keine Daten, einmal hatte ich auch einen "Socket not found" error. In der Regel klappt hier alfred aber nicht gut. Vll. kann man da noch was machen? Neustart behebt das Problem. Grüße Adrian > -----Original Message----- > From: franken-dev [mailto:franken-dev-bounces@freifunk.net] On Behalf > Of Tim Niemeyer > Sent: Sonntag, 12. November 2017 14:49 > To: franken-dev@freifunk.net > Subject: [PATCH v2 2/2] fff-alfred: do not use bat0 for master selection > > During system boot, the dependency of alfred to the bat0 interface is > problematic. In some circumstances (no eth mesh and no wifi mesh), the > mesh interfaces are disabled, the > bat0 interface is removed and the station mode is entered. > > Because alfred is started after the station mode (current boot order), it > doesn't start up with the missing bat0 interface. > > Signed-off-by: Tim Niemeyer <tim@tn-x.org> > --- > > Changes in v2: > - Based on uci-defaults patch > > src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > b/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > index e09281e..3df6764 100644 > --- a/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > +++ b/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > @@ -6,7 +6,7 @@ uci batch <<EOF > set alfred.alfred=alfred > set alfred.alfred.interface='br-mesh' > set alfred.alfred.mode='slave' > - set alfred.alfred.batmanif='bat0' > + set alfred.alfred.batmanif='none' > set alfred.alfred.start_vis='0' > set alfred.alfred.run_facters='0' > EOF > -- > 2.1.4 > > -- > franken-dev mailing list > franken-dev@freifunk.net > http://lists.freifunk.net/mailman/listinfo/franken-dev-freifunk.net
Hier nochmal die Meldung: can't connect to unix socket: No such file or directory Ist reproduzierbar und geht nicht von selbst weg. Grüße Adrian > -----Original Message----- > From: mail@adrianschmutzler.de [mailto:mail@adrianschmutzler.de] > Sent: Samstag, 25. November 2017 21:20 > To: 'Tim Niemeyer' <tim@tn-x.org>; 'franken-dev@freifunk.net' <franken- > dev@freifunk.net> > Subject: RE: [PATCH v2 2/2] fff-alfred: do not use bat0 for master selection > > Hallo, > > ich habe regelmäßig Probleme mit Mesh-Routern, die ich auf V2 aktualisiere > und die dann nicht sofort den configap finden. > > Manchmal liefert alfred -r 64 einfach keine Daten, einmal hatte ich auch > einen "Socket not found" error. > > In der Regel klappt hier alfred aber nicht gut. Vll. kann man da noch was > machen? > > Neustart behebt das Problem. > > Grüße > > Adrian > > > -----Original Message----- > > From: franken-dev [mailto:franken-dev-bounces@freifunk.net] On Behalf > > Of Tim Niemeyer > > Sent: Sonntag, 12. November 2017 14:49 > > To: franken-dev@freifunk.net > > Subject: [PATCH v2 2/2] fff-alfred: do not use bat0 for master > > selection > > > > During system boot, the dependency of alfred to the bat0 interface is > > problematic. In some circumstances (no eth mesh and no wifi mesh), the > > mesh interfaces are disabled, the > > bat0 interface is removed and the station mode is entered. > > > > Because alfred is started after the station mode (current boot order), > > it doesn't start up with the missing bat0 interface. > > > > Signed-off-by: Tim Niemeyer <tim@tn-x.org> > > --- > > > > Changes in v2: > > - Based on uci-defaults patch > > > > src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred | 2 > > +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git > > a/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > > b/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > > index e09281e..3df6764 100644 > > --- a/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > > +++ b/src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred > > @@ -6,7 +6,7 @@ uci batch <<EOF > > set alfred.alfred=alfred > > set alfred.alfred.interface='br-mesh' > > set alfred.alfred.mode='slave' > > - set alfred.alfred.batmanif='bat0' > > + set alfred.alfred.batmanif='none' > > set alfred.alfred.start_vis='0' > > set alfred.alfred.run_facters='0' > > EOF > > -- > > 2.1.4 > > > > -- > > franken-dev mailing list > > franken-dev@freifunk.net > > http://lists.freifunk.net/mailman/listinfo/franken-dev-freifunk.net
During system boot, the dependency of alfred to the bat0 interface is problematic. In some circumstances (no eth mesh and no wifi mesh), the mesh interfaces are disabled, the bat0 interface is removed and the station mode is entered. Because alfred is started after the station mode (current boot order), it doesn't start up with the missing bat0 interface. Signed-off-by: Tim Niemeyer <tim@tn-x.org> --- Changes in v2: - Based on uci-defaults patch src/packages/fff/fff-alfred/files/etc/uci-defaults/51-fff-alfred | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)