<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Arial">Johnny - yes, of course - that is the risk.
Let's do this in a organized way. Johnny - please propose a 15
minute window any day or night - we will run the test while you
are around watching it.</font></p>
<p><font face="Arial">Do you want me to drop the Multinet link when
we do this?<br>
</font></p>
<div class="moz-cite-prefix">On 4/27/20 3:03 PM, Johnny Billquist
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5ed3da51-edf1-cbac-40ae-384032c81b05@softjar.se">I can
certainly set up a link in the bridge, but you got to be very
careful to not create any loops in the bridge, because it does not
detect this, and it will cause a storm within seconds, which will
be very bad.
<br>
<br>
Johnny
<br>
<br>
<br>
On 2020-04-27 18:49, Supratim Sanyal wrote:
<br>
<blockquote type="cite">Johnny and all,
<br>
<br>
Would it be possible to help me test Rob Jarratt's Route20?
<br>
<br>
At this point, ROUT20 (31.1022) is configured as an additional
Level-2 router for Area 31 not doing much beyond waiting to talk
to other area routers.
<br>
<br>
Johnny - do you think you could open up a port on your bridge
for testing? This side is at 64.137.176.104 (static), port 4711.
<br>
<br>
Anyone who owns an area and connects to Johnny's bridge using an
area router can also perhaps set up a second bridge link to
31.1022 for testing.
<br>
<br>
Here is my config file, followed by Rob's readme file. Hopefully
I am not missing something basic here and such a test will be a
really bad idea.
<br>
<br>
---
<br>
$ cat route20.ini
<br>
[node]
<br>
name=ROUT20
<br>
level=2
<br>
address=31.1022
<br>
priority=5
<br>
<br>
[ethernet]
<br>
interface=vde-decnet-tap1
<br>
cost=4
<br>
<br>
[bridge]
<br>
address=psilo.update.uu.se:4711
<br>
port=4711
<br>
cost=7
<br>
<br>
; DNS section is optional, if not present then there is no
periodic check to make sure
<br>
; that IP addresses have not changed. Note that the periodic
checks do not cause any delay
<br>
; as they are done asynchronously.
<br>
[dns]
<br>
address=8.8.8.8
<br>
poll=60
<br>
<br>
[logging]
<br>
ethpcapline=verbose
<br>
general=detail
<br>
circuit=verbose
<br>
line=verbose
<br>
adjacency=verbose
<br>
update=verbose
<br>
decision=detail
<br>
forwarding=verbose
<br>
messages=detail
<br>
dns=verbose
<br>
ethinit=verbose
<br>
ethcircuit=detail
<br>
ethpcapline=verbose
<br>
ethsockline=verbose
<br>
ddcmpsock=detail
<br>
ddcmp=verbose
<br>
ddcmpinit=verbose
<br>
sock=detail
<br>
nsp=verbose
<br>
nspmessages=verbose
<br>
netman=verbose
<br>
---
<br>
<br>
User Mode DECnet Router Readme
<br>
==============================
<br>
<br>
This program is a DECnet router that implements version 2.0 of
the DECnet routing specification
<br>
found here: <a class="moz-txt-link-freetext" href="http://linux-decnet.sourceforge.net/docs/route20.txt">http://linux-decnet.sourceforge.net/docs/route20.txt</a>
<br>
<br>
Second Alpha Release 15th Sep 2012 --> Actually no, Rob
updated it in March 2020
<br>
----------------------------------
<br>
<br>
This second release has been successfully tested with another
person in another area. It
<br>
fixes the following bugs and limitations:
<br>
<br>
1. Implements Level 1 Routing messages and interoperates
correctly with Level 1 routers
<br>
(ie routing nodes that are not area routers).
<br>
2. Packets routed from outside into the local area are no longer
dropped.
<br>
3. More tolerant of different line end formats on the
configuration file (ie DOS or non-DOS format).
<br>
4. Fixed some compiler warnings related to format strings.
<br>
<br>
I have also realised that for every bridge connection you use
you need a separate UDP port.
<br>
I am not sure if this is a flaw or a feature.
<br>
<br>
Features
<br>
--------
<br>
<br>
1. Runs on Windows either as a Windows Service, or as a console
program.
<br>
2. Runs on Linux as a daemon.
<br>
3. Full routing capability, so it avoids broadcasting all
routing messages to
<br>
entire network and kills looping packets.
<br>
4. Supports Ethernet (using pcap/winpcap).
<br>
5. Supports Johnny's bridge. You can now have multiple bridge
connections to
<br>
Johnny and direct to other people without creating loops.
<br>
6. Can be extended to support other kinds of circuit (Cisco and
Multinet might
<br>
be examples, not tried).
<br>
7. Does dynamic DNS updates without blocking.
<br>
<br>
Limitations
<br>
-----------
<br>
<br>
1. Only tested on Windows Server 2003 and Raspberry Pi running
Debian.
<br>
2. Does not support Phase III nodes.
<br>
3. Although it can be configured as a Level 1 node, it has only
been tested
<br>
as a Level 2 (area router) node.
<br>
4. Limited testing on Raspberry Pi.
<br>
5. Performance not tested. Does not implement throttling, so
traffic sent to
<br>
a machine with a slow network interface may experience
problems.
<br>
6. Not tested with multiple ethernets.
<br>
7. It does not handle LAT and MOP, if you need these protocols
then you still
<br>
need to use Johnny's bridge.
<br>
<br>
Configuration
<br>
-------------
<br>
<br>
The program expects a configuration file called route20.ini. A
sample
<br>
is provided, but here are some notes.
<br>
<br>
An [ethernet] section is used to define an Ethernet network
interface.
<br>
You can have as many [ethernet] sections as you have ethernet
network
<br>
interfaces.
<br>
<br>
A [bridge] section is used to define an interface compatible
with Johnny's
<br>
bridge. You can have as many [bridge] sections as you have
direct links to
<br>
other people's bridge or router (each requires a separate port).
Use a DNS
<br>
name rather than an IP address, the IP address is checked and
updated
<br>
according the [dns] section. Note also that the router will not
accept packets
<br>
from bridges not configured in the [bridge] section.
<br>
<br>
The [dns] section is used to specify the IP address of your DNS
server. This
<br>
must be a numeric IP address. The poll period determines the
period (in
<br>
seconds) of the checks for changes to the IP address in your
[bridge]
<br>
sections.
<br>
<br>
Windows Installation
<br>
--------------------
<br>
<br>
Prerequisites: winpcap
<br>
<br>
To install it as a service do the following:
<br>
<br>
1. Open a command prompt as an administrator.
<br>
2. Run "route20 install".
<br>
3. Copy the configuration file to %windir%\system32
<br>
4. Make sure the "DECnet 2.0 Router" service is configured to
run under an
<br>
account that has administrative privileges.
<br>
5. Start the service.
<br>
<br>
To run it as a console program:
<br>
<br>
1. Create a configuration file in the directory where the
executable is
<br>
located.
<br>
2. Run the executable.
<br>
<br>
Linux Installation
<br>
------------------
<br>
<br>
Prerequisites: pcap
<br>
<br>
The program is designed to run only as a daemon. It logs to the
syslog.
<br>
Launch the program and it will fork and create a daemon.
<br>
<br>
<br>
-- <br>
Supratim Sanyal, W1XMT
<br>
39.19151 N, 77.23432 W
<br>
QCOCAL::SANYAL via HECnet
<br>
<br>
</blockquote>
<br>
</blockquote>
<pre class="moz-signature" cols="72">--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet</pre>
</body>
</html>