Xnet axudp link Jnos

The axudp link from xnet to jnos has caused a lot of problems.
But he is up and running … Here the explanation.

In the line “attach axudp xnet 256 192.168.1.112” (jnos) is the secret.
This must therefore “not” refer to the ip address of xnet like you
have indicated in ip.net at myip, but to the IP address of Linux itself.
So the ip address of (for example) eth0

Autoexec.nos (Jnos)

Eth0 (Linux)

Ip.net (xnet)

Autoboot.net (xnet)

 

(X)Net IP.NET

A small example of IP.NET from (X) Net

(X)Net Crontab

Here a small example of the crontab of (X) Net

(X)Net autoexec.net

 

(X)Net autoboot.net

 

Start (X)Net/kissattach/slip at boot

I have written the startup script below so that all services are started. Now of course it is nice if this also happens when booting the server. First the start script.

Now I have created the following file in /etc/init.d with the name xnet.

Now it has to be added.
update-rc.d xnet defaults
update-rc.d xnet enable

Well, reboot and see if everything is alright.

(X)Net slip link linux

Well here I have been working on it for a while. Because (new) Linux works with master /dev/pmtx and slave /dev/pts/? it is not always easy to find out which slave you will be assigned. Custom programs such as kissattach that give the slave with stdout. Now slattach does not suffer from it unfortunately. Oh well in Debian than.

I use the following program to create a master and slave.

I have added the code below. Because I would like the pts to be written down in a file.

As you can see above, the pts are displayed with printf and they are written in /tmp/slip. Well here I wanted to go. Now I can read the file. Here I use the following in my start script of (X) Net.

With the command “sed” the PTS is adjusted in AUTOBOOT.NET. Now I do not have to worry about what pts I get assigned.

(X)Net – Statd / Rstatd Port Statistieken.

It is possible with (X)net to display the port statistics in a bar chart.
This way you get a nice overview per port. In the file postat.zip the cgi script is what you need to get the statistics from the file * .sta. There is also a postat.txt in which “what” explains how it should and works. I found it fairly unclear, but that can also be my knowledge of the German language 🙂
Here the necessary file…postat.zip

apt-get install libgd2-xpm-dev            “You really need this one”

GD is an open source code library for the dynamic creation of images by programmers. GD is written in C, and “wrappers” are available for Perl, PHP and other languages. GD creates PNG, JPEG, GIF, WebP, XPM, BMP images, among other formats. GD is commonly used to generate charts, graphics, thumbnails, and most anything else, on the fly.

 

 

There are two different ways to achieve this.
The first option described below I use for my port statistics.

In IP.NET the rstatd deamon is started with the IP address of your web server

start rstatd 192.168.1.112    #ip-adres webserver

In the start of (X) Net, I have included the following line. The rstatrxd refers to the directory of your web server in this case /var/www/cgi-bin/postat/

./rstatrxd /var/www/cgi-bin/postat/ &

I use the following to get the statistics from the file pi1lap.sta.
Here I get the data from port 0 with an interval of 10 from the file.
/cgi-bin/postat.cgi?df=pi1lap.sta&port=0&interval=10&cfg=0&l2con=2
The cfg = 0 indicates the size of the bar chart. Give it a try. Option 1 and 2 are also possible. l2con = 1 or 2

Here below with an interval of 60 minutes and 720 minutes.
/cgi-bin/postat.cgi?df=pi1lap.sta&port=0&interval=60&cfg=0&l2con=2
/cgi-bin/postat.cgi?df=pi1lap.sta&port=0&interval=720&cfg=0&l2con=2

Example :
Poort Statistieken

Option 2 actually works the same way. Only a simlink is placed from the file min.sta to the web server directory.

In IP.NET
#### Start statd
start statd
start statd 60 min.sta
start statd 3600 hour.sta
start statd 86400 day.sta

ln -s /usr/local/xnet/min.sta /var/www/cgi-bin/postat/min.sta
ln -s /usr/local/xnet/hour.sta /var/www/cgi-bin/postat/hour.sta
ln -s /usr/local/xnet/day.sta /var/www/cgi-bin/postat/day.sta
ln -s /usr/local/xnet/port.sta /var/www/cgi-bin/postat/port.sta

/cgi-bin/postat.cgi?df=port.sta&port=-1&l2con=1 # Status of all ports
/cgi-bin/postat.cgi?df=min.sta&port=3&l2con=1 # Status of port 3 in 10 minutes
/cgi-bin/postat.cgi?df=hour.sta&port=3&l2con=1 # Status of port 3 in 1 hour
/cgi-bin/postat.cgi?df=day.sta&port=3&l2con=1 # Status of port 3 in 1 day

min.sta is the status for 10 minutes
hour.sta is the status for 1 hour
day.sta is the status for 24 hours
port.sta is the complete status?

This could also suffice with just a simlink to the post.sta and then requesting the status with interval = 10 (60,720).