This issue has been dealt with here. The declab.net site runs a
dedicated VAX with Multinet that polls the other end at predetermined
intervals. When the other ends' address changes this end makes change
to the Multinet database and reboots. This software has been in use for
well over a year and appears to work very well.
It does require the use of DynDNS at the end that changes addresses so
that this end can do the lookup.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Mark Wickens
Sent: Thursday, September 15, 2011 17:14
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Alternatives to bridge when running via a dynamic
IP address
On 15/09/11 22:03, hvlems at zonnet.nl wrote:
Won't the IP address remain unchanged as long as you keep the router
up and running?
Or would thet be too costly?
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Alternatives to bridge when running via a dynamic
IP address
Verzonden: 15 september 2011 22:53
Guys,
Might as well explore this as an option.
The 3G network enabled Vigor 2800 router that I will be using at the
DEC Legacy event appears to be working reasonably well, but
unsurprisingly there does appear to be some fluctuation in the IP
address.
This means that an alternative to Johnny's bridge program might be
called for. I have a dynamic DNS reference set up and now updating
periodically, hecnet.no-ip.org, the question is what can I use as an
alternative to the bridge program which will cope with IP address
changes?
I seem to remember Multinet tunnels being mentioned in the past, do
they support dnydns, or any other technology?
Thanks for the help,
Mark.
Unfortunately not. I've seen three IP address changes in about the same
number of hours.
I don't know whether this poor performance is down to the completely
haphazard location of the dongle, or whether it's always this rubbish
but you don't realise when all you're doing is browsing the internet.
My experience of using a 3G dongle for anything other than web browsing
is very limited!
Regards
Mark.
It should happen before disk access across the CI bus is even possible.
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Satellite configuration/NCP crash
Verzonden: 15 september 2011 23:29
On 15/09/11 22:27, Peter Coghlan wrote:
Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node.
I would have thought that shutting off decnet will not affect SCS
traffic. If it happend that it did, AND there were two or more nodes
in the cluster trying to communicate and failing, I would expect one
or more nodes that lost quorum to hang for RECNXINTERVAL seconds
(by default, 20). After that, one or modes might bugcheck with a
CLUEXIT exception.
A SSRVEXCEPT exception much more likely indicates something is wrong
with the software.
Regards,
Peter Coghlan.
If it helps in the discussion the crash happened very quickly.
In a scsi cluster the cluster traffic is passed across another bus, like FDDI, ethernet (and possibly memory channel). That is the main difference between SCSI and DSSI. Likewise there is mo decnet over scsi as there is decnet over dssi (and the older CI)
------Origineel bericht------
Van: Peter Coghlan
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Satellite configuration/NCP crash
Verzonden: 15 september 2011 23:27
Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node.
I would have thought that shutting off decnet will not affect SCS
traffic. If it happend that it did, AND there were two or more nodes
in the cluster trying to communicate and failing, I would expect one
or more nodes that lost quorum to hang for RECNXINTERVAL seconds
(by default, 20). After that, one or modes might bugcheck with a
CLUEXIT exception.
A SSRVEXCEPT exception much more likely indicates something is wrong
with the software.
Regards,
Peter Coghlan.
On 15/09/11 22:23, hvlems at zonnet.nl wrote:
Which is where a dongle was originally designed for: occasionally browsing Inteernet resources where stability of the transmission pipe over any extended interval is unnecessary. Simply put a dongle is not an infrastructure component. There's no friendly neighbour to help you out?
Possibly.
The alternative is a local company, but they don't have a fixed IP address either. Obviously over an ADSL connection we are more likely to get a reliable IP address. However, the problem with this solution is that configuring NAT was an issue last time - they're router was managed by an external company, which put a spanner in the works at the time...
However, it might be worth a try again.
Regards, Mark.
On 15/09/11 22:27, Peter Coghlan wrote:
Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node.
I would have thought that shutting off decnet will not affect SCS
traffic. If it happend that it did, AND there were two or more nodes
in the cluster trying to communicate and failing, I would expect one
or more nodes that lost quorum to hang for RECNXINTERVAL seconds
(by default, 20). After that, one or modes might bugcheck with a
CLUEXIT exception.
A SSRVEXCEPT exception much more likely indicates something is wrong
with the software.
Regards,
Peter Coghlan.
If it helps in the discussion the crash happened very quickly.
Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node.
I would have thought that shutting off decnet will not affect SCS
traffic. If it happend that it did, AND there were two or more nodes
in the cluster trying to communicate and failing, I would expect one
or more nodes that lost quorum to hang for RECNXINTERVAL seconds
(by default, 20). After that, one or modes might bugcheck with a
CLUEXIT exception.
A SSRVEXCEPT exception much more likely indicates something is wrong
with the software.
Regards,
Peter Coghlan.
Which is where a dongle was originally designed for: occasionally browsing Inteernet resources where stability of the transmission pipe over any extended interval is unnecessary. Simply put a dongle is not an infrastructure component. There's no friendly neighbour to help you out?
On 15/09/11 22:03, hvlems at zonnet.nl wrote:
Won't the IP address remain unchanged as long as you keep the router up and running?
Or would thet be too costly?
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Alternatives to bridge when running via a dynamic IP address
Verzonden: 15 september 2011 22:53
Guys,
Might as well explore this as an option.
The 3G network enabled Vigor 2800 router that I will be using at the DEC
Legacy event appears to be working reasonably well, but unsurprisingly
there does appear to be some fluctuation in the IP address.
This means that an alternative to Johnny's bridge program might be
called for. I have a dynamic DNS reference set up and now updating
periodically,
hecnet.no-ip.org, the question is what can I use as an alternative to
the bridge program which will cope with IP address changes?
I seem to remember Multinet tunnels being mentioned in the past, do they
support dnydns, or any other technology?
Thanks for the help,
Mark.
Unfortunately not. I've seen three IP address changes in about the same number of hours.
I don't know whether this poor performance is down to the completely haphazard location of the dongle,
or whether it's always this rubbish but you don't realise when all you're doing is browsing the internet.
My experience of using a 3G dongle for anything other than web browsing is very limited!
Regards
Mark.
Won't the IP address remain unchanged as long as you keep the router up and running?
Or would thet be too costly?
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Alternatives to bridge when running via a dynamic IP address
Verzonden: 15 september 2011 22:53
Guys,
Might as well explore this as an option.
The 3G network enabled Vigor 2800 router that I will be using at the DEC
Legacy event appears to be working reasonably well, but unsurprisingly
there does appear to be some fluctuation in the IP address.
This means that an alternative to Johnny's bridge program might be
called for. I have a dynamic DNS reference set up and now updating
periodically,
hecnet.no-ip.org, the question is what can I use as an alternative to
the bridge program which will cope with IP address changes?
I seem to remember Multinet tunnels being mentioned in the past, do they
support dnydns, or any other technology?
Thanks for the help,
Mark.
Guys,
Might as well explore this as an option.
The 3G network enabled Vigor 2800 router that I will be using at the DEC Legacy event appears to be working reasonably well, but unsurprisingly there does appear to be some fluctuation in the IP address.
This means that an alternative to Johnny's bridge program might be called for. I have a dynamic DNS reference set up and now updating periodically,
hecnet.no-ip.org, the question is what can I use as an alternative to the bridge program which will cope with IP address changes?
I seem to remember Multinet tunnels being mentioned in the past, do they support dnydns, or any other technology?
Thanks for the help,
Mark.