On 10/06/12 21:53, Marc Chametzky wrote:
I have increased the timeout values on the router that is attached to
SG1::. Hopefully this improves matters.
I may have missed something, but I saw that you increased the TCP timeouts. By default, DECnet-over-IP uses UDP packets, so that'd be the timeout you'd want to increase.
> The uplink port is a gigabit port connected to my FiOS ONT (connected at
> 100 Mbps).
What does it speak to the fios NT (I knew nothing about what strange
things local phone compnies manage to do..) Is it just DHCP or exoting
things like pppoe?
The ONT simply presents itself as a regular, routed 100Base-TX network interface. There's no special protocol used between the SonicWALL and the ONT. The SonicWALL specifies 71.182.147.1 as its default route, which is either the ONT itself or something upstream from it. I don't know where the fiber's IP router actually lives.
I have five static IP addresses that I manually configure, so I'm not using DHCP on my WAN segment.
Now, getting back to the UDP versus TCP, MultiNet does support setting up DECnet circuits using TCP. It's not available via MULTINET CONFIGURE/DECNET from what I could see, but it is listed in the online help for MULTINET SET/DECNET as /TCP=[CONNECT|LISTEN]. TCP connections may prove to be more reliable under some circumstances.
--Marc
My comments are probably completely useless, but I'll say it anyway.
I've seen this behaviour in a box with multiple network adapters where one (or more) are not connected to a network segment.
Mark.
--
http://www.wickensonline.co.ukhttp://declegacy.org.uk
I have increased the timeout values on the router that is attached to
SG1::. Hopefully this improves matters.
I may have missed something, but I saw that you increased the TCP timeouts. By default, DECnet-over-IP uses UDP packets, so that'd be the timeout you'd want to increase.
> The uplink port is a gigabit port connected to my FiOS ONT (connected at
> 100 Mbps).
What does it speak to the fios NT (I knew nothing about what strange
things local phone compnies manage to do..) Is it just DHCP or exoting
things like pppoe?
The ONT simply presents itself as a regular, routed 100Base-TX network interface. There's no special protocol used between the SonicWALL and the ONT. The SonicWALL specifies 71.182.147.1 as its default route, which is either the ONT itself or something upstream from it. I don't know where the fiber's IP router actually lives.
I have five static IP addresses that I manually configure, so I'm not using DHCP on my WAN segment.
Now, getting back to the UDP versus TCP, MultiNet does support setting up DECnet circuits using TCP. It's not available via MULTINET CONFIGURE/DECNET from what I could see, but it is listed in the online help for MULTINET SET/DECNET as /TCP=[CONNECT|LISTEN]. TCP connections may prove to be more reliable under some circumstances.
--Marc
I'm still seeing issues with STUPI:: though...
The other Multinet Tunnel connections seem to be quiet (for now...).
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Bob Armstrong
Sent: Sunday, June 10, 2012 12:08
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] netowrk flapping....
... considering creating a static route to your end and to Sampsa's
end because those constitute the US backbone into Europe.
I'm not quite sure what you have in mind - in the FVS338 I
already have an inbound rule that forwards all inbound UDP
packets addressed to 64.142.52.93:700 (that's the WAN address
of decnet.jfcl.com) to 10.1.1.13:700 (that's the IP of LEGATO
on my internal network). I think that's as much of a static
route as is possible in this case.
So far, SG1 hasn't "flapped" since 7:28AM PDT.
Bob
The timeout is currently set to 2 billion seconds. This "should" not be
a problem for most people. :-)
I may reduce it to a week if this timeout causes me any grief.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Peter Lothberg
Sent: Sunday, June 10, 2012 17:02
To: hecnet at Update.UU.SE
Cc: hecnet at Update.UU.SE
Subject: RE: [HECnet] netowrk flapping....
I have increased the timeout values on the router that is
attached to
SG1::. Hopefully this improves matters.
Can you make the timer multiple days or weeks?
(Anyone trying to use HECnet traveling over that link will be very
frustrated....)
-P
I have increased the timeout values on the router that is attached to
SG1::. Hopefully this improves matters.
Can you make the timer multiple days or weeks?
(Anyone trying to use HECnet traveling over that link will be very
frustrated....)
-P
... considering creating a static route to your end and to Sampsa's
end because those constitute the US backbone into Europe.
I'm not quite sure what you have in mind - in the FVS338 I already have an
inbound rule that forwards all inbound UDP packets addressed to
64.142.52.93:700 (that's the WAN address of decnet.jfcl.com) to
10.1.1.13:700 (that's the IP of LEGATO on my internal network). I think
that's as much of a static route as is possible in this case.
So far, SG1 hasn't "flapped" since 7:28AM PDT.
Bob
Bob,
I have the 318 - the little brother of the 338. I adjusted the TCP
timeout value (default 600 seconds). I did not touch the UDP time value
(default 75 seconds). I set the TCP timeout to the max value. If it
causes other issues I will back it off as necessary.
I was considering creating a static route to your end and to Sampsa's
end because those constitute the US backbone into Europe. I may still
do that. You might want to consider it as well. IF we do it at the
same time who knows how much better things can become. :-)
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Bob Armstrong
Sent: Sunday, June 10, 2012 11:00
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] netowrk flapping....
Steve -
You said you have an FVS338, right? Which timeout values
on which setup screen did you change?
I want to check my FVS338 to see how it's set.
BTW, you did define (under Security >> Services) a service
for UDP 700, right? And then under Security >> Firewall, you
added incoming and outgoing rules for that service ?
Bob
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Steve Davidson
Sent: Sunday, June 10, 2012 7:45 AM
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] netowrk flapping....
I have increased the timeout values on the router that is
attached to SG1::.
Hopefully this improves matters.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl
Sent: Sunday, June 10, 2012 03:08
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] netowrk flapping....
Bob, on A44RTR is see SG1 flapping as well. After breakfast
I'll see
whether there is a pattern. Initially I thought it was the linux
laptop going to sleep after a whule. That may not be the case.
Hans
------Origineel bericht------
Van: Bob Armstrong
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] netowrk flapping....
Verzonden: 10 juni 2012 01:32
Yup, that's basically a deficiency I've got...
Yeah, but the next question is "Are you the only one", or
do other
people's routers have similar timeout issues?
Bob
Steve -
You said you have an FVS338, right? Which timeout values on which setup
screen did you change?
I want to check my FVS338 to see how it's set.
BTW, you did define (under Security >> Services) a service for UDP 700,
right? And then under Security >> Firewall, you added incoming and outgoing
rules for that service ?
Bob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
Of Steve Davidson
Sent: Sunday, June 10, 2012 7:45 AM
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] netowrk flapping....
I have increased the timeout values on the router that is attached to SG1::.
Hopefully this improves matters.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl
Sent: Sunday, June 10, 2012 03:08
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] netowrk flapping....
Bob, on A44RTR is see SG1 flapping as well. After breakfast I'll see
whether there is a pattern. Initially I thought it was the linux
laptop going to sleep after a whule. That may not be the case.
Hans
------Origineel bericht------
Van: Bob Armstrong
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] netowrk flapping....
Verzonden: 10 juni 2012 01:32
Yup, that's basically a deficiency I've got...
Yeah, but the next question is "Are you the only one", or do other
people's routers have similar timeout issues?
Bob
I have increased the timeout values on the router that is attached to
SG1::. Hopefully this improves matters.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl
Sent: Sunday, June 10, 2012 03:08
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] netowrk flapping....
Bob, on A44RTR is see SG1 flapping as well. After breakfast
I'll see whether there is a pattern. Initially I thought it
was the linux laptop going to sleep after a whule. That may
not be the case.
Hans
------Origineel bericht------
Van: Bob Armstrong
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] netowrk flapping....
Verzonden: 10 juni 2012 01:32
Yup, that's basically a deficiency I've got...
Yeah, but the next question is "Are you the only one", or
do other people's routers have similar timeout issues?
Bob
