Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proposal mini scripts #3

Open
viisauksena opened this issue Mar 19, 2016 · 7 comments
Open

proposal mini scripts #3

viisauksena opened this issue Mar 19, 2016 · 7 comments

Comments

@viisauksena
Copy link

so i nicely noticed you loved some of my ssh infos and you advanced them heavily, which i took than for myself - thx 👍

  • maybe you like our new miniscripts - named after the infos itself to quickly and easily change stuff
    like you can use :
contact <[email protected]>
MoL 1
MoW 0
branch stable
autoupdater 1
fastd 0
hop_penalty 200
lat 47.0000
lon 7.00000
alt 2000
location 1
sshkeys
geoguess

viisauksena/gluon-banner@f9cf579
the git is tooo different to do simply merge-request - sorry for that (be aware of minor following bugfixes)

edit: especially the colliding names of autoupdater and fastd - which means these miniscripts have to be renamed, beside some internal bugfixes

@ghost
Copy link

ghost commented Mar 20, 2016

This is the way to go without question..

One thing: I would prefer the different commands to be grouped in one i.e.:

#nodeinfo contact
<[email protected]>

#nodeinfo lat
12.3456

#nodeinfo sshkeys
ssh-rsa uiaeosnrnrtd key1
ssh-rsa xvlcqfwgkcqoet key2

#nodeinfo foo
bar

@viisauksena
Copy link
Author

also nice idea, i love that you basicly could use all the identifiers from the ssh-login-info (or by others the nodeinfo) ..
i present plenty of Information when somebody is logging in .. and if logical you could use the "whatever" to change the values directly

# example output on login - yes i like the owl ;)
              Freifunk Gluon Node      http://gluon.readthedocs.org/
   ,     ,    based on OpenWrt         http://openwrt.org/
   )\___/(    powered by GNU/Linux     http://gnu.org/
  {(@)v(@)}   respect PPA guidelines   http://www.picopeer.net/
   {|~~~|}    building mesh networks   http://freifunk.net/
   {/^^^\}    network documentation    http://freiburg.freifunk.net/
 ---`m-m`---  support needed?       -> http://forum.freifunk.net/
                                       http://cccfr.de/wiki/freifunk

for command line help type 'help' - for status info type 'nodeinfo'
########################################
checking v4 - empty if v4 available 
you may want IPv4, try :   udhcpc -i br-client -q -S -n
########################################
### IP :            inet6 addr: 2001:bf7:2810:ff42:c66e:1fff:fe2d:4dee/64 Scope:Global
### from ssh : fe80::224:d7ff:fe96:b440%br-client 59219 fe80::c66e:1fff:fe2d:4dee%br-client 22
### known sshkeys : fuzzle birger mar fabzgy@fabzgy wuschl - active : 5
### uptime/load :   17:20:21 up 14:04,  load average: 0.45, 0.40, 0.32
########################################
### pubkey :  96aabe3ba566f47036caffeeaffeecaffee....cut-some-stuff...40c250e0a
### firmware :  v2016.1.2.d   branch :  support   autoupdater : 1
### hardware :  TP-Link TL-WR841N/ND v9
########################################
### MoL:'1'   MoW:'0'   fastd:'1'
### Location:  '0' lat: lon: alt:
### contact :  'kaulquappen supäää'
########################################
### connected to this node  :    1
### number of nodes (inkl SN) :  297
### number of total clients :    627
### number of GW :  7  - connected to =>          Herr-SN9 (219) ea:e1:28:58:a0:e6 [     ibss0]: 215 - 96MBit/96MBit
########################################
### /sys/class/net/bat0/mesh/hop_penalty :    15
### batctl gw :      client (selection class: 20)
####logread#############################
Sun Mar 20 17:20:21 2016 daemon.info fastd[1616]: resolving host `sn4.freiburg.freifunk.net' for peer <mesh_vpn_backbone_peer_sn9>...
Sun Mar 20 17:20:21 2016 daemon.info fastd[1616]: resolving host `sn4.freiburg.freifunk.net' failed: Name or service not known
Sun Mar 20 17:20:22 2016 daemon.info fastd[1616]: resolving host `sn3.freiburg.freifunk.net' for peer <mesh_vpn_backbone_peer_sn3>...
########################################

but you could easily get in trouble with generating plenty and maybe concurrent names like fastd autoupdater ... this gives you solution a clear plus
and as our versions differ so much - i like to see your solutions ... and maybe there is upstream someday for that in a generic gluon-package

@ghost
Copy link

ghost commented Mar 20, 2016

I wouldn't want the login to be so bloated. That could be the output of nodeinfo all.
This package needs some work everywhere. Even the installation is buggy when using sysupgrade.

@Adorfer
Copy link
Member

Adorfer commented May 6, 2016

Es wäre praktisch, wenn man über die Site.conf für diese Scripts ändern könnte
a) community-spezifisches (Name, Fallback-DNS...)
b) den "bloat-level", also ob z.B. die NodeInfo über die banner/profile kommt.

b) würde auch ermöglichen, auf Nodes mit erwiesenermaßen "mieser Anbindung" das abzustellen. Oder dem Wunsch einzelner Nodeaufstellenden nachzukommen, die das "bei sich" nicht haben wollen mit so viel test. (oder umgekehrt: Per default aus, und nur bei denen die es möchten....)

@ghost
Copy link

ghost commented May 6, 2016

Hmm. Du meinst eher per UCI setting, die beim Update bestehen bleibt..?
In der Site könnte man wenn dann die Defaults für die genannten UCI-Werte haben.
Da stellt sich für mich die Frage, ob es sauber genug ist, die Werte in einem Bash-Script per uci show zu holen..

@rubo77
Copy link
Collaborator

rubo77 commented Jan 24, 2017

ich denke, man sollte nicht mehr auf dem Router speichern, als notwendig für den Betrieb ist. Wenn man solche Kürzel braucht, dann kann man sie einfach lokal auf seinem Rechner anlegen und per SSH ausführen

@viisauksena
Copy link
Author

@rubo77 auch eine gute idee , das als externes script zu haben, aber meine Faulheit machte das script . auf jedem node ein einfaches set an befehlen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants