[HECnet] Adjacencies Keep Bouncing

[Robert Jarratt]

I wouldn't exclude that possibility at all. Basically there seems to be a problem with packets getting lost somewhere between Sampsa's nodes and whatever machine he is peering with. Pcap/winpcap is a possibility based on some experience I have had with winpcap. But it would be good to hear if there is anything else that is unusual in his setup that might cause this. I am guessing that there are many other nodes on HECnet that are also SIMH, if there are, they do not bounce nearly as often.

Regards

Rob

-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Gregg Levine
Sent: 29 June 2014 23:50
To: hecnet at update.uu.se
Subject: Re: [HECnet] Adjacencies Keep Bouncing

Hello!
Now this is straight out into deep space, and probably aiming for a cloaked
starship, but what if the problem is how the network is connected to what
Sampsa runs?
Sampsa how about some input from you please?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."


On Sun, Jun 29, 2014 at 12:38 PM, Johnny Billquist <bqt at softjar.se> wrote:
Just a few comments...

8.400 (GORVAX) is a SIMH VAX, according to the nodename database.
http://madame.update.uu.se/~bqt/nodedb?search=gorvax&field=0&sort=0

I see the same issues with GORVAX and KUHAVX (47.556) also on MIM.

Both machines (and areas) are run by Sampsa. Not sure how relevant
that is...

I have not done any further looking at actual packets yet. I might if
I find some time. But it do seem there is some kind of problem/issue here.

              Johnny


On 2014-06-29 02:04, Robert Jarratt wrote:

I think this was discussed not too long ago, but I can   t find the
email thread. Sorry, this is quite a long email.

Here at 5.1023 I keep experiencing certain adjacencies going up and
down. At the bottom of this email is an extract of several hours of
my log (all times are UK local time, current GMT+1).

Last night I investigated one of these, when 8.400 went down at
2014-06-28 22:04:03. I used a packet sniffer and could see that my
Ethernet Router Hello message went out, with 8.400 in it, at the
following times:

22:03:18

22:03:23

22:03:33

22:03:38

22:03:48

22:03:53

I did not send any Ethernet Router Hello messages in that period that
excluded 8.400.

Conversely, from 8.400 I received Ethernet Router Hello messages,
with
5.1023 included except where noted at the following times:

22:03:28

22:03:29

22:03:30

22:03:45

22:03:46

22:03:47

22:04:03 (5.1023 missing)

22:04:04

22:04:07

22:04:08

22:04:09

22:04:25

22:04:26

So here are some interesting things about the above information.

1. I am supposed to send out the Ethernet Router Hello every 15 seconds.