[HECnet] Node 4.249

[Rob Jarratt]

I am working on it right now, working on the Update Process so that other
routers know how to route back to me. I am hoping to have a basic router
that works on a LAN and against the bridge at the other end in the next week
or so. At this stage it will be Windows only (can run on your desktop or as
a Windows service) and various parts of the spec won't be fully implemented.
I had an earlier version running on a Raspberry Pi, but I suspect it will
take a day or two longer to get it working on there again.

Right now I have the Ethernet Initialization Layer done, the Decision
Process coded (and tested to some degree), and I have started on the Update
and Forwarding processes which are the least well developed.

Regards

Rob

-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Gregg Levine
Sent: 28 August 2012 20:35
To: hecnet at update.uu.se
Subject: Re: [HECnet] Node 4.249

On Tue, Aug 28, 2012 at 3:30 PM, Rob Jarratt <robert.jarratt at ntlworld.com>
wrote:
The problem stopped around the time of your first email, so I guess
you fixed it. My user mode router is not reporting adjacency up and
down any more.

Regards

Rob

-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-
hecnet at Update.UU.SE]
On Behalf Of Mark Wickens
Sent: 28 August 2012 17:08
To: hecnet at update.uu.se
Subject: Re: [HECnet] Node 4.249

I'm not totally clear on your setup. You have two interfaces, eth0
and
eth2.
I think I got that. And the bridge program is using eth0 for it's
bridge.
But how does your ethernet looks like? Is both eth0 and eth2
connected to the same physical network? Is the router on that same
segment as
well?

Both interfaces are on the same segment as the router.

What sessions are you seeing on the router?

On the router I see the following sessions:


----------------------------------------------------------------------
------
---
        Private IP :Port #Pseudo Port                 Peer IP :Port   Ifno   Status

----------------------------------------------------------------------
------
---
  192.168.1.126   4711                 4711     130.238.19.25   4711         3   0
  192.168.1.127   4711                 4711     130.238.19.25   4711         3   0

Where 192.168.1.126 is eth0 and 192.168.1.127 is eth2

And what did the routing table on the machine running the bridge
look like, if you have two interfaces?


No idea on this one.

The bridge program does not try to do anything clever with the UDP
packets, so they will be sent on any interface, based on your
routing table. It might sound as if your router/NAT was pointing at
the IP address of eth0, but the default entry of the routing table
on your machine would be using eth2. But this is all wild guessing
right
now...

OK, that probably explains it. I thought the bridge was tied to that
particular
interface. It's worth pointing out that what I'm doing it probably
daft -
the
2nd card was installed to use for a SIMH instance, so I should
probably
de-
configure it from an OS point of view.


Hello!
Funny you should mention that reason behind that card, Mark, I had plans
utilizing that idea, but I shelved them for the moment, when I realized
that
there would be a big problem. Namely the fact that my DSL device is
getting
on in years, and I'm not all sure what would happen when I tried any of
that.

Next:
Rob you've mentioned several times a user mode router. Presumably for
Decnet issues of course. When will it become an available option and on
what platforms?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."