Need explanation/clarification on step #7 of SPUD setup

[ericjarvies]

Hello,

I am currently in the process of installing SPUD onto one of my servers… but seeing as how this is my first time, and lacking documentation, perhaps someone could explain what exactly is needed as per item 7 on the installation notes, e.g.- 7) Configure SPUD

1. What IP & Port number should be used for the VIS server?
2. Regarding VIS server version… I cloned the source from the Github repo, so does this mean I use ‘trunk’ setting?
3. the VIS server mode... does this need to be changed?

I am looking to interface with MP01 devices on my home network… I am installing SPUD on a remote DigitalOcean server.

Any other advise regarding the rest of the setup process would of course be welcome and appreciated.

Thank you,

Eric Jarvies Cabo San Lucas, Baja California Sur, Mexico

[stevesong]

Sorry about that, the instructions for 7) are a little dated. To answer your questions

1/ The VIS server IP address should be the IP address of the mesh node that you have configured as the vis server on the network. Any mesh node can be the vis server but it is typical to use the gateway node. Setting a mesh node into VIS server node instructs other mesh nodes to provide mesh connection information to the VIS server.

Having Spud on a remote server could be problematic if your local network is NAT'ed. The Spud server needs to see the VIS server. You might have to map port 2005 on the VIS server node to your outside IP address in order for an external Spud server to see it and collect the data.

2/ Yes trunk

3/ the VIS server mode should be set to batman-adv

[ericjarvies]

Steve,

Much of the documentation is outdated... as are links to various resources and/or files, like to the following .ipx for example. None the less, a bigger problem -for me anyways- is that the xinetd_2.3.14-1_mips.ipk package does not work on my MP device/firmware, e.g.-

root@MP-252:/tmp# opkg install xinetd_2.3.14-1_mips.ipk Unknown package 'xinetd'. Collected errors:

• _pkg_hash_fetch_best_installationcandidate: Packages for xinetd found, but incompatible with the architectures configured
• _opkg_installcmd: Cannot install package xinetd.

Any ideas or suggestions?

Thanks,

Eric

[stevesong]

Which version of the SECN firmware are you using?

[ericjarvies]

SECN-2_0-Alpha3 MP01 on all 4 MP01 devices.

[stevesong]

ok, I think xinetd is already installed on alpha3. You can check to see whether

 /etc/init.d/xinetd 

exists to confirm. You can start xinetd with the command

 /etc/init.d/xinetd start

and making it permanent by doing

  ln -s /etc/init.d/xinetd /etc/rc.d/S70xinetd

Then you can create the file

/etc/xinetd.d/vis

with the contents:

   # default: on
   # description: Vis socket server
   service vis
    {
    port            = 2005
    socket_type     = stream
    wait            = no
    user            = root
    server          = /etc/vis.sh
    log_on_success  += USERID
    log_on_failure  += USERID
    disable         = no
     }

Create /etc/vis.sh with the contents

  #!/bin/sh
  batctl vd json

save it and make it executable with

 chmod +x /etc/vis.sh

then you can test whether xinetd and the vis server are working with

 telnet localhost 2005

Don't forget to enable the vis server on the gateway MP with by adding the following line:

option 'vis_mode' 'server' 

to the file /etc/config/batman-adv

Finally, also don't forget to populate the /etc/bat-hosts file with the IP addresses that correspond to the MAC addresses.

[ericjarvies]

Unfortunately, xinetd is not installed:

[tgillett]

Hi Eric

It seems xinetd was not included in the build for Alpha 3. Apologies.

Attached is an xinetd package that you can install on the MP01s.

Copy the file to /tmp on the devices then install with opkg.

From a Linux PC: $ scp ./xinetd_2.3.14-1_atheros.ipk root@:/tmp

On the MP01:

cd /tmp

opkg install ./xinetd_2.3.14-1_atheros.ipk

Regards Terry

On Mon, Nov 10, 2014 at 6:24 AM, Eric Jarvies notifications@github.com wrote:

Unfortunately, xinetd is not installed: [image: terminal_output] https://cloud.githubusercontent.com/assets/977450/4968873/48b3bbd8-684e-11e4-8b59-b8aa26280bbc.png

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62317871.

[ericjarvies]

Hello,

Where is the attachment located exactly?

Thanks,

Eric

[tgillett]

Hi Eric

I am not sure I understand your question.

Did you receive the xinetd .ipk file with the email?

Once you have the file, copy it into the /tmp directory on the MP01 using scp, and then install it with the opkg command.

Does that help?

Regards Terry

On Mon, Nov 10, 2014 at 7:44 AM, Eric Jarvies notifications@github.com wrote:

Hello,

Where is the attachment located exactly?

Thanks,

Eric

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62321223.

[ericjarvies]

Terry,

No I did not receive the file :-)

Perhaps git is stripping it from your reply?

Eric

On Nov 9, 2014, at 3:10 PM, Terry Gillett notifications@github.com wrote:

Hi Eric

I am not sure I understand your question.

Did you receive the xinetd .ipk file with the email?

Once you have the file, copy it into the /tmp directory on the MP01 using scp, and then install it with the opkg command.

Does that help?

Regards Terry

On Mon, Nov 10, 2014 at 7:44 AM, Eric Jarvies notifications@github.com wrote:

Hello,

Where is the attachment located exactly?

Thanks,

Eric

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62321223.

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62322234.

[tgillett]

Ahh! That is likely the case.

Do you have a direct email I can send it to? It is only 60k.

On Mon, Nov 10, 2014 at 8:12 AM, Eric Jarvies notifications@github.com wrote:

Terry,

No I did not receive the file :-)

Perhaps git is stripping it from your reply?

Eric

On Nov 9, 2014, at 3:10 PM, Terry Gillett notifications@github.com wrote:

Hi Eric

I am not sure I understand your question.

Did you receive the xinetd .ipk file with the email?

Once you have the file, copy it into the /tmp directory on the MP01 using scp, and then install it with the opkg command.

Does that help?

Regards Terry

On Mon, Nov 10, 2014 at 7:44 AM, Eric Jarvies notifications@github.com

wrote:

Hello,

Where is the attachment located exactly?

Thanks,

Eric

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62321223.

— Reply to this email directly or view it on GitHub < https://github.com/villagetelco/spud/issues/2#issuecomment-62322234>.

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62322280.

[ericjarvies]

On Nov 9, 2014, at 3:18 PM, Terry Gillett notifications@github.com wrote:

Ahh! That is likely the case.

Do you have a direct email I can send it to? It is only 60k.

eric@csl.mx mailto:eric@csl.mx

Thanks Terry.

On Mon, Nov 10, 2014 at 8:12 AM, Eric Jarvies notifications@github.com wrote:

Terry,

No I did not receive the file :-)

Perhaps git is stripping it from your reply?

Eric

On Nov 9, 2014, at 3:10 PM, Terry Gillett notifications@github.com wrote:

Hi Eric

I am not sure I understand your question.

Did you receive the xinetd .ipk file with the email?

Once you have the file, copy it into the /tmp directory on the MP01 using scp, and then install it with the opkg command.

Does that help?

Regards Terry

On Mon, Nov 10, 2014 at 7:44 AM, Eric Jarvies notifications@github.com

wrote:

Hello,

Where is the attachment located exactly?

Thanks,

Eric

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62321223.

— Reply to this email directly or view it on GitHub < https://github.com/villagetelco/spud/issues/2#issuecomment-62322234>.

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62322280.

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62322496.

[ericjarvies]

I can't seem to telnet onto the gateway MP... have tried telnet 192.168.1.252 2005 and other acceptable strings, but the MP keeps refusing the connection.

Everything else seems to go fine... SPUD is working, but does not show any of my MP devices, e.g.- http://104.131.56.182/spud/

I've pointed to my aDSL IP address, and have configured my aDSL modem so it allows 2005-2015 port access to 192.168.1.252(my gateway MP), and I've tried with both range(2005 to 2015) and just single fixed(2005):

When I try to telnet onto the MP by way of the public IP route... it too fails like it does using the localhost and 192.168.1.252 LAN addresses. Whilst I cannot access the MP by way of telnet, I can access it just fine by way of browser admin page and via SSH(I can't access it via SFTP).

Also, I added MAC info in the following format(with colons... is this correct?): 80:82:87:XX:XX:XX 192.168.1.252 80:82:87:XX:XX:XX 192.168.1.22 80:82:87:XX:XX:XX 192.168.1.23 80:82:87:XX:XX:XX 192.168.1.24

Should the "gw_mode" line be removed?: config 'mesh' 'bat0' option 'interfaces' 'wlan0-1' option 'bl' '1' option 'gw_mode' 'server' option 'vis_mode' 'server'

[tgillett]

Hi Eric

Can you ping the MP01?

Have you set the password on the MP01? If so, then telnet is disabled and you use ssh to access the command line.

On Mon, Nov 10, 2014 at 11:27 AM, Eric Jarvies notifications@github.com wrote:

I can't seem to telnet onto the gateway MP... have tried telnet 192.168.1.252 2005 and other acceptable strings, but the MP keeps refusing the connection.

Everything else seems to go fine... SPUD is working, but does not show any of my MP devices, e.g.- http://104.131.56.182/spud/

I've pointed to my aDSL IP address, and have configured my aDSL modem so it allows 2005-2015 port access to 192.168.1.252(My gateway MP), and I've tried with both range(2005 t o2015 and just 2005): [image: firewall1] https://cloud.githubusercontent.com/assets/977450/4970082/31fcc298-6878-11e4-8c15-16ece930e7c4.png [image: firewall2] https://cloud.githubusercontent.com/assets/977450/4970083/322f3340-6878-11e4-8152-41f51ace3dd3.png

When I try to telnet onto the MP by way of the public IP route... it too fails like it does using the localhost and 192.168.1.252 LAN addresses.

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62330184.

[tgillett]

Eric Did you receive the xinetd file OK? Terry

On Mon, Nov 10, 2014 at 11:27 AM, Eric Jarvies notifications@github.com wrote:

I can't seem to telnet onto the gateway MP... have tried telnet 192.168.1.252 2005 and other acceptable strings, but the MP keeps refusing the connection.

Everything else seems to go fine... SPUD is working, but does not show any of my MP devices, e.g.- http://104.131.56.182/spud/

I've pointed to my aDSL IP address, and have configured my aDSL modem so it allows 2005-2015 port access to 192.168.1.252(My gateway MP), and I've tried with both range(2005 t o2015 and just 2005): [image: firewall1] https://cloud.githubusercontent.com/assets/977450/4970082/31fcc298-6878-11e4-8c15-16ece930e7c4.png [image: firewall2] https://cloud.githubusercontent.com/assets/977450/4970083/322f3340-6878-11e4-8152-41f51ace3dd3.png

When I try to telnet onto the MP by way of the public IP route... it too fails like it does using the localhost and 192.168.1.252 LAN addresses.

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62330184.

[ericjarvies]

Terry,

Yes, I received and installed the file onto the one MP(Gateway), thanks.

Ok, so when the root password is set on the MP devices, Telnet is turned off. I can indeed ping the MP both locally and using aDSL public IP.

I have a question that is sort of related to this thread... Is it possible to build the MP firmware so that either(or both) UPnP and/or NAT-PMP is present/active? It would be nice if the user could toggle this setting in the admin section.

Thanks,

Eric

[ericjarvies]

I have not yet attempted to build the firmware, but plan on doing so sometime soon. As it stands, what would be involved in adding uPnP to the build? e.g.- http://wiki.openwrt.org/doc/howto/upnp

[tgillett]

Hi Eric

Indeed UPnP and NAT-PNP are implemented in OpenWrt. See link below:

  http://wiki.openwrt.org/doc/howto/upnp

However UPnP is generally regarded as a security barn door, and NAT-PNP requires a largish package to be added.

It is unlikely that we will add these to MP01 firmware as it is really approaching end of life.

It may be feasible to add NAT-PNP support to later devices with more memory and CPU resources. This can be done just by installing and configuring the required package(s) on top of the standard firmware.

Regards Terry

On Mon, Nov 10, 2014 at 12:15 PM, Eric Jarvies notifications@github.com wrote:

Terry,

Yes, I received and installed the file onto the one MP(Gateway), thanks.

Ok, so when the root password is set on the MP devices, Telnet is turned off. I can indeed ping the MP both locally and using aDSL public IP.

I have a question that is sort of related to this thread... Is it possible to build the MP firmware so that either(or both) UPnP and/or NAT-PMP is present/active? It would be nice if the user could toggle this setting in the admin section.

Thanks,

Eric

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62332668.

[stevesong]

Hi Eric,

Have you confirmed that everything is working on the Vis server MP? i.e. can you ssh into the MP and confirm the Vis server is collecting data by executing

batctl vd json

then make sure the vis script is producing output

vis.sh

then check that xinetd is calling the vis script ok with

telnet localhost 2005

Are all those working?

[ericjarvies]

Steve,

The first two do nothing, and the telnet command returns connection error, e.g.-

root@MP-252:/etc# batctl vd json root@MP-252:/etc# sh vis.sh root@MP-252:/etc# telnet localhost 2005 telnet: can't connect to remote host (127.0.0.1): Connection refused root@MP-252:/etc#

Eric

[stevesong]

ok, it seems as if vis server mode for batman-adv has not been enabled. If you execute

batctl vis_mode server

on the command line and re-do the tests above, does that work? If so then we just have to figure out why the batman-adv configuration enabling vis server mode on boot.

[ericjarvies]

That helped! I can now see output(identical) with both via.sh and batctl vd json. But telnet is still refusing connections(via localhost, 127.0.0.1, and 192.168.1.252).

[stevesong]

ok, make sure that /etc/config/batman-adv matches the following:

config 'mesh'  'bat0'
    option 'interfaces' 'wlan0-1'
    option 'bl' '1'
    option 'gw_mode' 'off'
    option 'vis_mode' 'server' 

now we have to work out why xinetd is not responding. Can you try executing

/etc/init.d/xinetd start

and then trying telnet again? If that works then we need to check that xinetd is set to start up on boot. does /etc/rc.d/S70xinetd exist? If not then run:

ln -s /etc/init.d/xinetd /etc/rc.d/S70xinetd

[ericjarvies]

Ok, I changed option 'gw_mode' 'server' to 'off' and I executed xinetd start but Telnet still does not work. The S70xinetd file is/was there.

[stevesong]

and you can confirm that you have created the file: /etc/xinetd.d/vis with the following content?

   # default: on
   # description: Vis socket server
   service vis
    {
    port            = 2005
    socket_type     = stream
    wait            = no
    user            = root
    server          = /etc/vis.sh
    log_on_success  += USERID
    log_on_failure  += USERID
    disable         = no
     }

[ericjarvies]

Yes, confirmed.

[stevesong]

Hmmm... I think we have a problem with the version of xinetd that Terry sent. It installs ok but it doesn't appear to run. Will get back to you on this. Thanks for being patient.

[ericjarvies]

Thanks for your help, and no problems.

[tgillett]

Hi Eric

Telnet to munin is working for me from the command line (see below).

Just to confirm, Is this not working on your device?

Regards Terry

root@MP-37:~# cat /etc/banner ..... Village Telco - Small Enterprise Campus Network

Version: SECN-2_0-Alpha3 MP01 OpenWRT: Attitude Adjustment (unknown) Build date: 2014-08-27-12:14 GitHub: vt-firmware Alpha3-build-0-gdedff533af

root@MP-37:~# opkg list_installed | grep xinetd xinetd - 2.3.14-1 root@MP-37:~# opkg list_installed | grep munin muninlite - 1.0.4-1

root@MP-37:~# cat /etc/services|grep munin munin 4949/tcp

root@MP-37:~# ps |grep xinet 23810 root 1468 S grep xinet root@MP-37:~# /etc/init.d/xinetd start root@MP-37:~# ps |grep xinet 23879 root 1204 S xinetd 23911 root 1468 S grep xinet

root@MP-37:~# /usr/sbin/munin-node

munin node at MP-37

^C

root@MP-37:~# telnet localhost 4949

munin node at MP-37

quit Connection closed by foreign host

On Tue, Nov 11, 2014 at 2:20 AM, Steve Song notifications@github.com wrote:

Hmmm... I think we have a problem with the version of xinetd that Terry sent. It installs ok but it doesn't appear to run. Will get back to you on this. Thanks for being patient.

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62408939.

[ericjarvies]

Terry,

Below is my output using the same commands you provided in your above response... notice munin has not output:

root@TP-252:/# cat /etc/banner ... Village Telco - Small Enterprise Campus Network

Version: SECN-2_0-Alpha3 MP01 OpenWRT: Attitude Adjustment (unknown) Build date: 2014-08-27-12:14 GitHub: vt-firmware Alpha3-build-0-gdedff533af

root@TP-252:/# opkg list_installed | grep xinetd xinetd - 2.3.14-1 root@TP-252:/# opkg list_installed | grep munin <<--notice no output root@TP-252:/# cat /etc/services|grep munin <<--notice no output root@TP-252:/# ps |grep xinet 4133 root 1468 S grep xinet root@TP-252:/# /etc/init.d/xinetd start root@TP-252:/# ps |grep xinet 4202 root 1468 S grep xinet root@TP-252:/# /usr/sbin/munin-node -ash: /usr/sbin/munin-node: not found root@TP-252:/# telnet localhost 4949 telnet: can't connect to remote host (127.0.0.1): Connection refused root@TP-252:/# telnet localhost 2005 telnet: can't connect to remote host (127.0.0.1): Connection refused root@TP-252:/#

[tgillett]

Eric

root@TP-252:/# opkg listinstalled | grep munin <<--notice no output_

The munin package is not installed on your MP01.

You can install it on-line if the MP has internet access, or you can download and install it manually.

1. Online Ensure that the MP has internet access. Try to ping www.google.com from the command line.

You will need to edit the opkg config file (/etc/opkg.conf) to point to the correct repo as follows:

cat /etc/opkg.conf

src/gz backfire http://downloads.openwrt.org/backfire/10.03.1/atheros/packages # Change this dest root / dest ram /tmp lists_dir ext /var/opkg-lists

Then run these commands to install muninlite:

opkg update

opkg install muninlite

1. Download Alternatively, you can download the .ipk file from the repo and copy it into /tmp on the MP and install from there. The package is available here:

https://downloads.openwrt.org/backfire/10.03.1/atheros/packages/muninlite_1.0.4-1_atheros.ipk

Regards Terry

On Tue, Nov 11, 2014 at 9:01 AM, Eric Jarvies notifications@github.com wrote:

Terry,

Below is my output using the same commands you provided in your above response... notice munin has not output:

root@TP-252:/# cat /etc/banner ... Village Telco - Small Enterprise Campus Network

_Version: SECN-20-Alpha3 MP01 OpenWRT: Attitude Adjustment (unknown) Build date: 2014-08-27-12:14 GitHub: vt-firmware Alpha3-build-0-gdedff533af

root@TP-252:/# opkg list_installed | grep xinetd xinetd - 2.3.14-1 root@TP-252:/# opkg listinstalled | grep munin <<--notice no output root@TP-252:/# cat /etc/services|grep munin <<--notice no output_ root@TP-252:/# ps |grep xinet 4133 root 1468 S grep xinet root@TP-252:/# /etc/init.d/xinetd start root@TP-252:/# ps |grep xinet 4202 root 1468 S grep xinet root@TP-252:/# /usr/sbin/munin-node -ash: /usr/sbin/munin-node: not found root@TP-252:/# telnet localhost 4949 telnet: can't connect to remote host (127.0.0.1): Connection refused root@TP-252:/# telnet localhost 2005 telnet: can't connect to remote host (127.0.0.1): Connection refused root@TP-252:/#

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62472396.

[ericjarvies]

Terry,

My opkg.conf file currently reads as follows; src testing http://elektrad.info/download/MESH-POTATO/attitude-adjustment/packag dest root / dest ram /tmp _listsdir ext /var/opkg-lists

You say it should instead read like so; src/gz backfire http://downloads.openwrt.org/backfire/10.03.1/atheros/packages dest root / dest ram /tmp lists_dir ext /var/opkg-lists

I was/am uncertain about the src/gz backfire portion.

Eric

[ericjarvies]

Using the above revised .conf settings, I was able to update, but the muninlite seemed not to work... it seems to be hanging(not returning to the prompt): root@TP-252:/etc# opkg update Downloading http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/Packages.gz. Inflating http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/Packages.gz. Updated list of available packages in /var/opkg-lists/backfire. root@TP-252:/etc# opkg install muninlite

I will try to manually download the .ipk and install it that way.

[tgillett]

Correct. Elektra's repo does not contain the additional packages.

src/gz just tells opkgto download the .gz compressed version of the package list and expand it locally to save data on the wire.

On Tue, Nov 11, 2014 at 9:27 AM, Eric Jarvies notifications@github.com wrote:

Terry,

My opkg.conf file currently reads as follows; src testing http://elektrad.info/download/MESH-POTATO/attitude-adjustment/packag http://elektrad.info/download/MESH-POTATO/attitude-adjustment/packag dest root / dest ram /tmp _listsdir ext /var/opkg-lists

You say it should instead read like so; src/gz backfire http://downloads.openwrt.org/backfire/10.03.1/atheros/packages http://downloads.openwrt.org/backfire/10.03.1/atheros/packages dest root / dest ram /tmp _listsdir ext /var/opkg-lists

I was/am uncertain about the src/gz backfire portion.

Eric

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62475701.

[tgillett]

The munin installation on the MP01 does take a longish time. You may have just not waited long enough. I went and had a coffee while it installed on my last test.

On Tue, Nov 11, 2014 at 9:34 AM, Eric Jarvies notifications@github.com wrote:

Using the above revised .conf settings, I was able to update, but the muninlite seemed not to work... it seems to be hanging(not returning to the prompt): root@TP-252:/etc# opkg update Downloading http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/Packages.gz http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/Packages.gz. Inflating http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/Packages.gz http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/Packages.gz. Updated list of available packages in /var/opkg-lists/backfire. root@TP-252:/etc# opkg install muninlite

I will try to manually download the .ipk and install it that way.

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62476474.

[ericjarvies]

So, when I attempt to opkg install muninlite it hangs, and when I press the enter/return key, it kicks me out(broken pipe), and I have to SSH onto the MP again. Open returning, and attempting the opkg install muninlite again, it indicates it cannot install the package muninlite, but after opkg update again I can then do opkg install muninlite but it fails again. Anyways, I'll try to manually install it now.

[ericjarvies]

Hmm. So, from the MP device I attempted to wget the file and it would not work(I believe because of https), so I returned to /etc and updated the packages and ran the muninlite install once again, and this time it returned; root@MP-252:/etc# opkg update Downloading http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/Packages.gz. Inflating http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/Packages.gz. Updated list of available packages in /var/opkg-lists/backfire. root@MP-252:/etc# opkg install muninlite Installing muninlite (1.0.4-1) to root... Downloading http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/muninlite_1.0.4-1_atheros.ipk. Configuring muninlite.**

It is still hanging below the Configuring muninlite line... but will let it hang for another 30 minutes or so and see if it works. Otherwise, I've since removed the s from the URL you provided and it works so will try to wget and install manually if the above fails.

Thanks.

[ericjarvies]

Ok, here is the latest output:

root@MP-252:/tmp# wget http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/muninlite_1.0.4-1_at heros.ipk Connecting to downloads.openwrt.org (78.24.191.177:80) muninlite_1.0.4-1_at 100% |**_| *_6549 0:00:00 ETA root@MP-252:/tmp# opkg install muninlite_1.0.4-1_atheros.ipk Installing muninlite (1.0.4-1) to root... Configuring muninlite. root@MP-252:/tmp# opkg list_installed | grep xinetd xinetd - 2.3.14-1 root@MP-252:/tmp# opkg list_installed | grep munin muninlite - 1.0.4-1 root@MP-252:/tmp# cat /etc/services|grep munin munin 4949/tcp root@MP-252:/tmp# ps |grep xinet 2844 root 1468 S grep xinet root@MP-252:/tmp# /etc/init.d/xinetd start root@MP-252:/tmp# ps |grep xinet 2854 root 1204 S xinetd 2873 root 1468 S grep xinet root@MP-252:/tmp# /usr/sbin/munin-node # munin node at MP-252 ^C root@MP-252:/tmp# telnet localhost 4949 # munin node at MP-252 quit Connection closed by foreign host** root@MP-252:/tmp#

[tgillett]

That now matches what I get from the telnet command.

Xinetd and munin should be working now. On 11/11/2014 10:01 AM, "Eric Jarvies" notifications@github.com wrote:

Ok, here is the latest output:

root@MP-252:/tmp# wget http://downloads.openwrt.org/backfire/10.03.1/atheros/packages/muninlite_1.0.4-1_at heros.ipk Connecting to downloads.openwrt.org http://downloads.openwrt.org (78.24.191.177:80 http://78.24.191.177:80) _muninlite_1.0.4-1at 100% |**| *6549 0:00:00 ETA root@MP-252:/tmp# opkg install muninlite_1.0.4-1_atheros.ipk Installing muninlite (1.0.4-1) to root... Configuring muninlite. root@MP-252:/tmp# opkg list_installed | grep xinetd xinetd - 2.3.14-1 root@MP-252:/tmp# opkg list_installed | grep munin muninlite - 1.0.4-1 root@MP-252:/tmp# cat /etc/services|grep munin munin 4949/tcp root@MP-252:/tmp# ps |grep xinet 2844 root 1468 S grep xinet root@MP-252:/tmp# /etc/init.d/xinetd start root@MP-252:/tmp# ps |grep xinet 2854 root 1204 S xinetd 2873 root 1468 S grep xinet root@MP-252:/tmp# /usr/sbin/munin-node # munin node at MP-252 ^C root@MP-252:/tmp# telnet localhost 4949 # munin node at MP-252 quit Connection closed by foreign host root@MP-252:/tmp#

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62479450.

[ericjarvies]

So, I've opened up port 2005 for my gateway MP device(the one with muninlite etc. installed on it), but I cannot connect to it from the outside(public IP). I am able to set the same port number using my computer's LAN IP, and I can access it, but for some reason I cannot access any of the MP devices from the outside using public IP. Steve had previously mentioned it is not a good idea to install SPUD on a remote computer outside of the LAN on which the MP devices are installed... is there a particular reason for this? When I use my aDSL modem's admin page to adjust the firewall settings for any of the MP devices, it seems it behaves differently with/for the MP devices then it does for my Mac or QNAP(etc.). Scratching my head as to why.

[tgillett]

I can not understand why port forwarding would not work for the MP.

Have you tried to forward the ssh port and access that from outside? On 11/11/2014 10:27 AM, "Eric Jarvies" notifications@github.com wrote:

So, I've opened up port 2005 for my gateway MP device(the one with muninlite etc. installed on it), but I cannot connect to it from the outside(public IP). I am able to set the same port number using my computer's LAN IP, and I can access it, but for some reason I cannot access any of the MP devices from the outside using public IP. Steve had previously mentioned it is not a good idea to install SPUD on a remote computer outside of the LAN on which the MP devices are installed... is there a particular reason for this? When I use my aDSL modem's admin page to adjust the firewall settings for any of the MP devices, it seems it behaves differently with/for the MP devices then it does for my Mac or QNAP(etc.). Scratching my head as to why.

— Reply to this email directly or view it on GitHub https://github.com/villagetelco/spud/issues/2#issuecomment-62481947.

[stevesong]

ok, I got telnet localhost 2005 to work. I realised that xinetd will not load as a daemon unless it finds something that it needs to run. I didn't have /etc/vis.sh set up or munin installed, so xinetd didn't load.

However, I realised there is a step missing. The line

 vis       2005/tcp

needs to be added to /etc/services. Now when I telnet to localhost at port 2005, I get the batctl vd json output

[ericjarvies]

Thanks Terry & Steve! I've certainly made progress. I applied your latest advice and subsequently ran /etc/init.d/xinetd stop/start and sh vis.sh and am now able to telnet to either 2005 or 4949, receiving the respective output(neighbors/gateways & munin node at MP-252), but I would point out if I pass the enter key whilst in 4949 I get the following output: /usr/sbin/munin-node: line 589: do_: not found

Not sure what that means, otherwise if I type quit the connection closes as normal.

Alas, whilst everything locally on the MP seems to be working, for whatever reason I cannot access the MP devices via the public IP. I thought that perhaps my aDSL modem was the problem, but I went ahead and set ports 2005 and 4949 to point to my Mac desktop computer, and am able to access it fine using said ports. But when I set the aDSL modem to point to the MP gateway device(192.168.1.252) I cannot access it from the public IP... and the same applies with any of the MP devices. It seems my computer and NAS and AppleTVs and other appliances can be accessed just fine from the public IP, but not the MPs. Is there anything obvious that I could be missing?

[ericjarvies]

I sent both of you a private email... this is an elaboration on that. I SSH'd onto my remote server that has SPUD installed on it, and from that session I telnet'd back to my network via the public IP, and it worked! I do not understand why I was/am unable to do the same from my local computer, but none the less I see that it works.

Now then, what is supposed to be seen on the SPUd web pages? Should they not be displaying the MP devices?

[vusy-nathan]

i am following this blog i tried to install spud but without luck but now i see that my /etc/config/batman-adv looks like this

config mesh 'bat0' options interfaces 'ath0-1 wlan0-1' option bl '1' option gw_mode 'server' option 'vis_mode' 'server'

and steve posted the following /etc/config/batman-adv in reply to eric config 'mesh' 'bat0' option 'interfaces' 'wlan0-1' option 'bl' '1' option 'gw_mode' 'off' option 'vis_mode' 'server'