Hans,
Assuming you can priv up to root, you should be able to search the `rpm` database on your system (I believe you said you are on a red-hat system).
# rpm -qa |grep -i pcap
If libpcap is not installed, you may be able to use a tool such as `yum` to identify the package that you need to add. For example:
# yum whatprovides */libpcap.so */libpcap.a
<... SNIP...>
14:libpcap-devel-0.9.4-15.el5.x86_64 : A pcap library.
Repo : base
Matched from:
Filename : /usr/lib64/libpcap.so
14:libpcap-devel-0.9.4-15.el5.x86_64 : A pcap library.
Repo : base
Matched from:
Filename : /usr/lib64/libpcap.a
You could then, potentially, install one of the listed libs...
# yum install libpcap-devel*
or what have you....
Pay attention to the path... you may need to instruct the bridge code on the whereabouts of the lib... (which can, of course be determined with the fore-mentioned rpm commands)...
Joe
On Sun, Jul 4, 2010 at 4:28 PM, H Vlems <hvlems at zonnet.nl> wrote:
Apparently it is already on the system. But unixes have a tremendous
capacity to hide resources for the simple owner/user ....
Steve Davidson knows the answer, he's done the trick on a BSD system.
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: zondag, juli 2010 22:22
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
I'll happily answer any questions, and so on. pcap is a library that is
needed by the bridge program, but exactly how you get that onto your
machine is beyond me.
Johnny
H Vlems wrote:
> Johnny, as soon as I've figured out how this works I'll write a manual for
> you :-)
> But you've got to guide me through the entire painful process first.
> I had to shut down my Fedora 9 workstation because of the heat.
> The error messages I got while attempting to compile the source were all
> related to 'pcap'. Any suggestions?
>
> Hans
>
> PS
> Later in the evening when the system is up again I'll post more
information.
>
> -----Oorspronkelijk bericht-----
> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
> Johnny Billquist
> Verzonden: vrijdag, juli 2010 9:50
> Aan: hecnet at Update.UU.SE
> Onderwerp: Re: [HECnet] Attaching to hecnet
>
> You don't need "your own" port number. You need a port number. You are
> free to pick any that isn't used by something else on your system.
>
> That said, 4744 works just as fine as anything else, including 4711. As
> Sampsa pointed out, you can use 4711 as well, if you want to. It only
> needs to be unique on your system. What ports I (or anyone else) is
> using, does not affect you more than that you have to have that
> information in your conf-file.
>
> Your own port number is specified on the command line, as mentioned as
well.
>
> Oh, and the reason you haven't seen a manual about the bridge program is
> because I've never written one. :-)
> Feel free to contribute... ;-)
>
> Johnny
>
> H Vlems wrote:
>> OK, I understand that part (I think) of the bridge program.
>> I wasn't aware that I'd need my own port number. I'll opt for 4744, if
> that
>> is alright.
>> Do I need to configure this somewhere (like in the .conf file)?
>> Hans
>>
>> PS
>> My apologies for all these questions but I haven't seen a manual about
the
>> bridge program....
>>
>>
>> -----Oorspronkelijk bericht-----
>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
>> Johnny Billquist
>> Verzonden: donderdag, juli 2010 15:45
>> Aan: hecnet at Update.UU.SE
>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>
>> Hi.
>>
>> H Vlems wrote:
>>> OK, let's try the bridge option first. Could you give me a sample .conf
>> file
>>> that I can use?
>> Hmm. Not one that you can use straight away, no.
>>
>> However, it should look something like this:
>> ================
>> [bridge]
>> local <your ethernet interface name>
>> update psilo.update.uu.se:4711
>> [decnet]
>> local
>> update
>> =================
>>
>> And that's it. What your local ethernet name is, I have no idea.
>>
>>> My external IP address is:
>>>
>>> Name: osmium.homeip.net
>>> Address: 87.209.50.192
>> That is something I need for my side of the bridge. In addition, I also
>> need to know what port number you will be using.
>>
>>> I assume that a NAT entry is needed on my ADSL router, right? Would that
>> be
>>> for port 4711 (as in eau de cologne ??)
>> Yes, 4711 is named after the water from Cologne. :-)
>> (Very oldish hacker folklore that I suspect people nowadays might not
>> know...)
>>
>> And yes, if you have NAT running, you will need to forward traffic
>> between your box, at whatever port you are using, and
>> psilo.update.uu.se:4711. And this is UDP traffic.
>>
>> Johnny
>>
>>> Hans
>>>
>>> -----Oorspronkelijk bericht-----
>>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
>>> Johnny Billquist
>>> Verzonden: woensdag, juni 2010 14:16
>>> Aan: hecnet at Update.UU.SE
>>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>>
>>> Hi, Hans.
>>>
>>> H Vlems wrote:
>>>> OK Johnny, talk to me :-)
>>>> This is my plan: I intend to modify two systems to try the connection
to
>>>> HECnet.
>>>> 1) I have a linux system under Fedora 9 that will run the bridge
> software
>>>> and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address
>>> 1.1010.
>>>
>>> That should work without any strange problems. You'll probably want to
>>> connect the bridge to me in that case. Let me know when you are ready to
>>> try.
>>>
>>>> 2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in
>>> area
>>>> 44.
>>>> I'd like to try that connection without the linux system.
>>> You need to find someone who can act as the other end in this case.
>>> Which I suspect meaning someone running phase V and as an area router. I
>>> don't know who might be doing this. Maybe someone who do can speak up.
>>>
>>> Anyone know if this would be compatible with DECnet over IP as Multinet
>>> does it?
>>>
>>>> Option 2 is my preferred situation since it removes a by and large
>> unknown
>>>> factor from the equation (the linux box).
>>> Sure. We just need to identify someone you can connect to.
>>>
>>>> So, what do I need to know and to do to make this work?
>>> Someone to connect to...
>>>
>>> Johnny
>>>
>>>> Hans
>>>>
>>>> -----Oorspronkelijk bericht-----
>>>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
>>>> Johnny Billquist
>>>> Verzonden: maandag, juni 2010 21:03
>>>> Aan: hecnet at Update.UU.SE
>>>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>>>
>>>> H Vlems wrote:
>>>>> What I meant with the phase III-IV-V answer is that direct
connectivity
>>>>> between a phase V and phase III system won't work. But poor man's
>> routing
>>>>> will work with a phase IV node in between. Functionality of course is
>>>>> limited by the phase III host :-)
>>>> I wonder if phase III to phase V neccesarily will not work. However,
DEC
>
>>>> never guaranteed that it will work, nor did they ever try it.
>>>>
>>>>> But you're absolutely right that very few people will have a phase III
>>>>> system, RT-11 being the most likely candidate?
>>>> Probably. Or if someone is running some old versions of other systems.
>>>>
>>>>> I've seen the bridge program, but am not sure how to make the .conf
> file
>>>>> work. Is it possible to use DECnet address 1.1010 to try and make this
>>>> work?
>>>>
>>>> Yes. 1.1010 is not used by anyone, so that node number would be ok to
>>>> use to test.
>>>> But you also need to talk with me (or someone else) with the bridge
>>>> running, to act as the remote end.
>>>>
>>>> Johnny
>>>>
>>>>> Hans
>>>>>
>>>>> -----Oorspronkelijk bericht-----
>>>>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
> Namens
>>>>> Johnny Billquist
>>>>> Verzonden: maandag, juni 2010 11:02
>>>>> Aan: hecnet at Update.UU.SE
>>>>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>>>>
>>>>> Hi.
>>>>>
>>>>> H Vlems wrote:
>>>>>> DECnet phase IV nodes are backwards compatible with phase III.
>>>>> Yes. But the question here was if phase V will interoperate with phase
>>>>> III. I don't know the answer to that one, but on the other hand, I
> don't
>>>>> think anyone around is running phase III anyway.
>>>>>
>>>>>> There are no restrictions in functionality between phase IV nodes and
>>>>> phase
>>>>>> V as seen by the unpriviledged user. Area routing may be an issue on
>>>>> Alpha,
>>>>>> and of course ncl is more of a pain to remember than ncp ;-)
>>>>> True, as far as that goes.
>>>>> However, I am not sure that a phase V node can operate as a phase IV
>>>>> area router.
>>>>>
>>>>> Someone else pointed out that although DEC claimed that alphas could
> not
>>>>> be area routers, that information is incorrect, and you can just tell
> an
>>>>> Alpha VMS phase IV node to be an area router, if you want to.
>>>>>
>>>>> However, DECnet+ is phase V, and all bets are off. :-)
>>>>>
>>>>> And yes, not only are the NCL commands more difficult to remember
>>>>> (atleast for me), the node name management is way more difficult as
>>>>> well. Do anyone know how you copy a nodename database from another
>>>>> machine with DECnet+?
>>>>>
>>>>>> Two questions:
>>>>>> 1-May I use area 44?
>>>>> Sure.
>>>>>
>>>>>> 2-Is there a short guide to set up DECnet over IP to connect to
> HECnet?
>>>>> Not that I know of. Maybe Mark Wickens have something on hecnet.eu?
>>>>> My page (http://www.update.uu.se/~bqt/hecnet.html) only have
> information
>>>>> about the bridge.
>>>>>
>>>>> Johnny
>>>>>
>>>>>> Hans
>>>>>> -----Oorspronkelijk bericht-----
>>>>>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
>> Namens
>>>>>> Marc Chametzky
>>>>>> Verzonden: maandag, juni 2010 0:04
>>>>>> Aan: hecnet at Update.UU.SE
>>>>>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>>>>>
>>>>>>> DECnet-Plus isn't
>>>>>>> able to connect, or at least reliably connect to all OS's that can
>>>>>>> potentially be on HECnet. I forget what all OS's I was having issues
>>>>>>> with, I know one was RSTS/E v10.1, but I want to say it also
included
>>>>>>> VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase
>> IV,
>>>>>>> all these issues went away. These were things as simple as SET HOST.
>>>>>> It's probably that DECnet-Plus (Phase V) cannot speak with DECnet
> Phase
>>>>>> III (such as on RSTS/E and TOPS-10/20). That's my guess anyway.
>>>>>>
>>>>>> Phase V should be able to communicate with VAX/VMS since that's Phase
>>>>>> IV, which is the gold standard of DECnet, IMHO.
>>>>>>
>>>>>> --Marc
>>>>>> Geen virus gevonden in het binnenkomende-bericht.
>>>>>> Gecontroleerd door AVG - www.avg.com
>>>>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte:
>>>>> 06/27/10
>>>>>> 08:35:00
>>>>>>
>>>>> Geen virus gevonden in het binnenkomende-bericht.
>>>>> Gecontroleerd door AVG - www.avg.com
>>>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte:
>>>> 06/28/10
>>>>> 08:37:00
>>>>>
>>>> Geen virus gevonden in het binnenkomende-bericht.
>>>> Gecontroleerd door AVG - www.avg.com
>>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
>>> 06/28/10
>>>> 20:35:00
>>>>
>>> Geen virus gevonden in het binnenkomende-bericht.
>>> Gecontroleerd door AVG - www.avg.com
>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
>> 06/28/10
>>> 20:35:00
>>>
>> Geen virus gevonden in het binnenkomende-bericht.
>> Gecontroleerd door AVG - www.avg.com
>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
> 07/01/10
>> 08:35:00
>>
> Geen virus gevonden in het binnenkomende-bericht.
> Gecontroleerd door AVG - www.avg.com
> Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
07/01/10
> 08:35:00
>
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2981 - datum van uitgifte: 07/04/10
08:35:00
Hans,
The DECnet-over-IP port is 399.
Regards,
Kari
On 4.7.2010 21:46, H Vlems wrote:
OK, i didn t install that package as an add-on. It s probably not a
component of Fedora 9.
BTW I have DECnet OSI running on a VAX. It is now a question of figuring
out what IP ports it uses and put them in the NAT service list on my
ADSL router.
My outside IP address is pointed to by the name osmium.homeip.net
(nslookup translates this to an IP address).
------------------------------------------------------------------------
*Van:* owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
*Namens *Joe Ferraro
*Verzonden:* zondag, juli 2010 20:06
*Aan:* hecnet at update.uu.se
*Onderwerp:* Re: [HECnet] Attaching to hecnet
Hans,
Make sure you have libpcap-devel installed. I'm not looking at the
bridge code at the moment, but you'll obviously want to make sure that
you are pointing to your libpcap libraries when you do the compile.
$ rpm -qa |grep -i libpcap # determine if packet cap libs are installed
Cheers,
Joe
On Sun, Jul 4, 2010 at 12:51 PM, H Vlems <hvlems at zonnet.nl
<mailto:hvlems at zonnet.nl>> wrote:
Johnny, as soon as I've figured out how this works I'll write a manual for
you :-)
But you've got to guide me through the entire painful process first.
I had to shut down my Fedora 9 workstation because of the heat.
The error messages I got while attempting to compile the source were all
related to 'pcap'. Any suggestions?
Hans
PS
Later in the evening when the system is up again I'll post more information.
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>
[mailto:owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>] Namens
Johnny Billquist
Verzonden: vrijdag, juli 2010 9:50
Aan: hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>
Onderwerp: Re: [HECnet] Attaching to hecnet
You don't need "your own" port number. You need a port number. You are
free to pick any that isn't used by something else on your system.
That said, 4744 works just as fine as anything else, including 4711. As
Sampsa pointed out, you can use 4711 as well, if you want to. It only
needs to be unique on your system. What ports I (or anyone else) is
using, does not affect you more than that you have to have that
information in your conf-file.
Your own port number is specified on the command line, as mentioned as well.
Oh, and the reason you haven't seen a manual about the bridge program is
because I've never written one. :-)
Feel free to contribute... ;-)
Johnny
H Vlems wrote:
OK, I understand that part (I think) of the bridge program.
I wasn't aware that I'd need my own port number. I'll opt for 4744, if
that
is alright.
Do I need to configure this somewhere (like in the .conf file)?
Hans
PS
My apologies for all these questions but I haven't seen a manual about the
bridge program....
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>
[mailto:owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>] Namens
Johnny Billquist
Verzonden: donderdag, juli 2010 15:45
Aan: hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
> OK, let's try the bridge option first. Could you give me a sample .conf
file
> that I can use?
Hmm. Not one that you can use straight away, no.
However, it should look something like this:
================
[bridge]
local <your ethernet interface name>
update psilo.update.uu.se:4711 <http://psilo.update.uu.se:4711>
[decnet]
local
update
=================
And that's it. What your local ethernet name is, I have no idea.
> My external IP address is:
>
> Name: osmium.homeip.net <http://osmium.homeip.net>
> Address: 87.209.50.192
That is something I need for my side of the bridge. In addition, I also
need to know what port number you will be using.
> I assume that a NAT entry is needed on my ADSL router, right? Would that
be
> for port 4711 (as in eau de cologne ??)
Yes, 4711 is named after the water from Cologne. :-)
(Very oldish hacker folklore that I suspect people nowadays might not
know...)
And yes, if you have NAT running, you will need to forward traffic
between your box, at whatever port you are using, and
psilo.update.uu.se:4711 <http://psilo.update.uu.se:4711>. And this is
UDP traffic.
Johnny
> Hans
>
> -----Oorspronkelijk bericht-----
> Van: owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>
[mailto:owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>] Namens
> Johnny Billquist
> Verzonden: woensdag, juni 2010 14:16
> Aan: hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>
> Onderwerp: Re: [HECnet] Attaching to hecnet
>
> Hi, Hans.
>
> H Vlems wrote:
>> OK Johnny, talk to me :-)
>> This is my plan: I intend to modify two systems to try the connection to
>> HECnet.
>> 1) I have a linux system under Fedora 9 that will run the bridge
software
>> and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address
> 1.1010.
>
> That should work without any strange problems. You'll probably want to
> connect the bridge to me in that case. Let me know when you are ready to
> try.
>
>> 2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in
> area
>> 44.
>> I'd like to try that connection without the linux system.
> You need to find someone who can act as the other end in this case.
> Which I suspect meaning someone running phase V and as an area router. I
> don't know who might be doing this. Maybe someone who do can speak up.
>
> Anyone know if this would be compatible with DECnet over IP as Multinet
> does it?
>
>> Option 2 is my preferred situation since it removes a by and large
unknown
>> factor from the equation (the linux box).
> Sure. We just need to identify someone you can connect to.
>
>> So, what do I need to know and to do to make this work?
> Someone to connect to...
>
> Johnny
>
>> Hans
>>
>> -----Oorspronkelijk bericht-----
>> Van: owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>
[mailto:owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>] Namens
>> Johnny Billquist
>> Verzonden: maandag, juni 2010 21:03
>> Aan: hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>
>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>
>> H Vlems wrote:
>>> What I meant with the phase III-IV-V answer is that direct connectivity
>>> between a phase V and phase III system won't work. But poor man's
routing
>>> will work with a phase IV node in between. Functionality of course is
>>> limited by the phase III host :-)
>> I wonder if phase III to phase V neccesarily will not work. However, DEC
>> never guaranteed that it will work, nor did they ever try it.
>>
>>> But you're absolutely right that very few people will have a phase III
>>> system, RT-11 being the most likely candidate?
>> Probably. Or if someone is running some old versions of other systems.
>>
>>> I've seen the bridge program, but am not sure how to make the .conf
file
>>> work. Is it possible to use DECnet address 1.1010 to try and make this
>> work?
>>
>> Yes. 1.1010 is not used by anyone, so that node number would be ok to
>> use to test.
>> But you also need to talk with me (or someone else) with the bridge
>> running, to act as the remote end.
>>
>> Johnny
>>
>>> Hans
>>>
>>> -----Oorspronkelijk bericht-----
>>> Van: owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>
[mailto:owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>]
Namens
>>> Johnny Billquist
>>> Verzonden: maandag, juni 2010 11:02
>>> Aan: hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>
>>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>>
>>> Hi.
>>>
>>> H Vlems wrote:
>>>> DECnet phase IV nodes are backwards compatible with phase III.
>>> Yes. But the question here was if phase V will interoperate with phase
>>> III. I don't know the answer to that one, but on the other hand, I
don't
>>> think anyone around is running phase III anyway.
>>>
>>>> There are no restrictions in functionality between phase IV nodes and
>>> phase
>>>> V as seen by the unpriviledged user. Area routing may be an issue on
>>> Alpha,
>>>> and of course ncl is more of a pain to remember than ncp ;-)
>>> True, as far as that goes.
>>> However, I am not sure that a phase V node can operate as a phase IV
>>> area router.
>>>
>>> Someone else pointed out that although DEC claimed that alphas could
not
>>> be area routers, that information is incorrect, and you can just tell
an
>>> Alpha VMS phase IV node to be an area router, if you want to.
>>>
>>> However, DECnet+ is phase V, and all bets are off. :-)
>>>
>>> And yes, not only are the NCL commands more difficult to remember
>>> (atleast for me), the node name management is way more difficult as
>>> well. Do anyone know how you copy a nodename database from another
>>> machine with DECnet+?
>>>
>>>> Two questions:
>>>> 1-May I use area 44?
>>> Sure.
>>>
>>>> 2-Is there a short guide to set up DECnet over IP to connect to
HECnet?
>>> Not that I know of. Maybe Mark Wickens have something on hecnet.eu
<http://hecnet.eu>?
>>> My page (http://www.update.uu.se/~bqt/hecnet.html
<http://www.update.uu.se/%7Ebqt/hecnet.html>) only have
information
>>> about the bridge.
>>>
>>> Johnny
>>>
>>>> Hans
>>>> -----Oorspronkelijk bericht-----
>>>> Van: owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>
[mailto:owner-hecnet at Update.UU.SE <mailto:owner-hecnet at Update.UU.SE>]
Namens
>>>> Marc Chametzky
>>>> Verzonden: maandag, juni 2010 0:04
>>>> Aan: hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>
>>>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>>>
>>>>> DECnet-Plus isn't
>>>>> able to connect, or at least reliably connect to all OS's that can
>>>>> potentially be on HECnet. I forget what all OS's I was having issues
>>>>> with, I know one was RSTS/E v10.1, but I want to say it also included
>>>>> VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase
IV,
>>>>> all these issues went away. These were things as simple as SET HOST.
>>>> It's probably that DECnet-Plus (Phase V) cannot speak with DECnet
Phase
>>>> III (such as on RSTS/E and TOPS-10/20). That's my guess anyway.
>>>>
>>>> Phase V should be able to communicate with VAX/VMS since that's Phase
>>>> IV, which is the gold standard of DECnet, IMHO.
>>>>
>>>> --Marc
>>>> Geen virus gevonden in het binnenkomende-bericht.
>>>> Gecontroleerd door AVG - www.avg.com <http://www.avg.com>
>>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte:
>>> 06/27/10
>>>> 08:35:00
>>>>
>>> Geen virus gevonden in het binnenkomende-bericht.
>>> Gecontroleerd door AVG - www.avg.com <http://www.avg.com>
>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte:
>> 06/28/10
>>> 08:37:00
>>>
>> Geen virus gevonden in het binnenkomende-bericht.
>> Gecontroleerd door AVG - www.avg.com <http://www.avg.com>
>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
> 06/28/10
>> 20:35:00
>>
> Geen virus gevonden in het binnenkomende-bericht.
> Gecontroleerd door AVG - www.avg.com <http://www.avg.com>
> Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
> 20:35:00
>
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com <http://www.avg.com>
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
07/01/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com <http://www.avg.com>
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2981 - datum van uitgifte:
07/04/10 08:35:00
I should know better than to open my big yap but: pcap isn't the only way to
do raw packet I/O on Linux; you can also use socket(PF_PACKET) and not need
any special libraries. Maybe a bit of conditionalized code in bridge.c would
make it easier to build on Linux w/o breaking it on other Unices? (Yes I'd
be happy to contribute code -- I've been working on my own mopd replacement
anyway partly because of how hard mopd is to build on Slackware Linux.)
John Wilson
D Bit
Apparently it is already on the system. But unixes have a tremendous
capacity to hide resources for the simple owner/user ....
Steve Davidson knows the answer, he's done the trick on a BSD system.
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: zondag, juli 2010 22:22
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
I'll happily answer any questions, and so on. pcap is a library that is
needed by the bridge program, but exactly how you get that onto your
machine is beyond me.
Johnny
H Vlems wrote:
Johnny, as soon as I've figured out how this works I'll write a manual for
you :-)
But you've got to guide me through the entire painful process first.
I had to shut down my Fedora 9 workstation because of the heat.
The error messages I got while attempting to compile the source were all
related to 'pcap'. Any suggestions?
Hans
PS
Later in the evening when the system is up again I'll post more
information.
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: vrijdag, juli 2010 9:50
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
You don't need "your own" port number. You need a port number. You are
free to pick any that isn't used by something else on your system.
That said, 4744 works just as fine as anything else, including 4711. As
Sampsa pointed out, you can use 4711 as well, if you want to. It only
needs to be unique on your system. What ports I (or anyone else) is
using, does not affect you more than that you have to have that
information in your conf-file.
Your own port number is specified on the command line, as mentioned as
well.
Oh, and the reason you haven't seen a manual about the bridge program is
because I've never written one. :-)
Feel free to contribute... ;-)
Johnny
H Vlems wrote:
OK, I understand that part (I think) of the bridge program.
I wasn't aware that I'd need my own port number. I'll opt for 4744, if
that
is alright.
Do I need to configure this somewhere (like in the .conf file)?
Hans
PS
My apologies for all these questions but I haven't seen a manual about
the
bridge program....
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: donderdag, juli 2010 15:45
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
OK, let's try the bridge option first. Could you give me a sample .conf
file
that I can use?
Hmm. Not one that you can use straight away, no.
However, it should look something like this:
================
[bridge]
local <your ethernet interface name>
update psilo.update.uu.se:4711
[decnet]
local
update
=================
And that's it. What your local ethernet name is, I have no idea.
My external IP address is:
Name: osmium.homeip.net
Address: 87.209.50.192
That is something I need for my side of the bridge. In addition, I also
need to know what port number you will be using.
I assume that a NAT entry is needed on my ADSL router, right? Would that
be
for port 4711 (as in eau de cologne ??)
Yes, 4711 is named after the water from Cologne. :-)
(Very oldish hacker folklore that I suspect people nowadays might not
know...)
And yes, if you have NAT running, you will need to forward traffic
between your box, at whatever port you are using, and
psilo.update.uu.se:4711. And this is UDP traffic.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: woensdag, juni 2010 14:16
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi, Hans.
H Vlems wrote:
OK Johnny, talk to me :-)
This is my plan: I intend to modify two systems to try the connection
to
HECnet.
1) I have a linux system under Fedora 9 that will run the bridge
software
and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address
1.1010.
That should work without any strange problems. You'll probably want to
connect the bridge to me in that case. Let me know when you are ready to
try.
2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in
area
44.
I'd like to try that connection without the linux system.
You need to find someone who can act as the other end in this case.
Which I suspect meaning someone running phase V and as an area router. I
don't know who might be doing this. Maybe someone who do can speak up.
Anyone know if this would be compatible with DECnet over IP as Multinet
does it?
Option 2 is my preferred situation since it removes a by and large
unknown
factor from the equation (the linux box).
Sure. We just need to identify someone you can connect to.
So, what do I need to know and to do to make this work?
Someone to connect to...
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Johnny Billquist
Verzonden: maandag, juni 2010 21:03
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
H Vlems wrote:
What I meant with the phase III-IV-V answer is that direct
connectivity
between a phase V and phase III system won't work. But poor man's
routing
will work with a phase IV node in between. Functionality of course is
limited by the phase III host :-)
I wonder if phase III to phase V neccesarily will not work. However,
DEC
never guaranteed that it will work, nor did they ever try it.
But you're absolutely right that very few people will have a phase III
system, RT-11 being the most likely candidate?
Probably. Or if someone is running some old versions of other systems.
I've seen the bridge program, but am not sure how to make the .conf
file
work. Is it possible to use DECnet address 1.1010 to try and make this
work?
Yes. 1.1010 is not used by anyone, so that node number would be ok to
use to test.
But you also need to talk with me (or someone else) with the bridge
running, to act as the remote end.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Johnny Billquist
Verzonden: maandag, juni 2010 11:02
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
DECnet phase IV nodes are backwards compatible with phase III.
Yes. But the question here was if phase V will interoperate with phase
III. I don't know the answer to that one, but on the other hand, I
don't
think anyone around is running phase III anyway.
There are no restrictions in functionality between phase IV nodes and
phase
V as seen by the unpriviledged user. Area routing may be an issue on
Alpha,
and of course ncl is more of a pain to remember than ncp ;-)
True, as far as that goes.
However, I am not sure that a phase V node can operate as a phase IV
area router.
Someone else pointed out that although DEC claimed that alphas could
not
be area routers, that information is incorrect, and you can just tell
an
Alpha VMS phase IV node to be an area router, if you want to.
However, DECnet+ is phase V, and all bets are off. :-)
And yes, not only are the NCL commands more difficult to remember
(atleast for me), the node name management is way more difficult as
well. Do anyone know how you copy a nodename database from another
machine with DECnet+?
Two questions:
1-May I use area 44?
Sure.
2-Is there a short guide to set up DECnet over IP to connect to
HECnet?
Not that I know of. Maybe Mark Wickens have something on hecnet.eu?
My page (http://www.update.uu.se/~bqt/hecnet.html) only have
information
about the bridge.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Marc Chametzky
Verzonden: maandag, juni 2010 0:04
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
DECnet-Plus isn't
able to connect, or at least reliably connect to all OS's that can
potentially be on HECnet. I forget what all OS's I was having issues
with, I know one was RSTS/E v10.1, but I want to say it also
included
VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase
IV,
all these issues went away. These were things as simple as SET HOST.
It's probably that DECnet-Plus (Phase V) cannot speak with DECnet
Phase
III (such as on RSTS/E and TOPS-10/20). That's my guess anyway.
Phase V should be able to communicate with VAX/VMS since that's Phase
IV, which is the gold standard of DECnet, IMHO.
--Marc
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte:
06/27/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte:
06/28/10
08:37:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
07/01/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
07/01/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2981 - datum van uitgifte: 07/04/10
08:35:00
I'll happily answer any questions, and so on. pcap is a library that is needed by the bridge program, but exactly how you get that onto your machine is beyond me.
Johnny
H Vlems wrote:
Johnny, as soon as I've figured out how this works I'll write a manual for
you :-)
But you've got to guide me through the entire painful process first.
I had to shut down my Fedora 9 workstation because of the heat.
The error messages I got while attempting to compile the source were all
related to 'pcap'. Any suggestions?
Hans
PS
Later in the evening when the system is up again I'll post more information.
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: vrijdag, juli 2010 9:50
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
You don't need "your own" port number. You need a port number. You are free to pick any that isn't used by something else on your system.
That said, 4744 works just as fine as anything else, including 4711. As Sampsa pointed out, you can use 4711 as well, if you want to. It only needs to be unique on your system. What ports I (or anyone else) is using, does not affect you more than that you have to have that information in your conf-file.
Your own port number is specified on the command line, as mentioned as well.
Oh, and the reason you haven't seen a manual about the bridge program is because I've never written one. :-)
Feel free to contribute... ;-)
Johnny
H Vlems wrote:
OK, I understand that part (I think) of the bridge program.
I wasn't aware that I'd need my own port number. I'll opt for 4744, if
that
is alright.
Do I need to configure this somewhere (like in the .conf file)?
Hans
PS
My apologies for all these questions but I haven't seen a manual about the
bridge program....
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: donderdag, juli 2010 15:45
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
OK, let's try the bridge option first. Could you give me a sample .conf
file
that I can use?
Hmm. Not one that you can use straight away, no.
However, it should look something like this:
================
[bridge]
local <your ethernet interface name>
update psilo.update.uu.se:4711
[decnet]
local
update
=================
And that's it. What your local ethernet name is, I have no idea.
My external IP address is:
Name: osmium.homeip.net
Address: 87.209.50.192
That is something I need for my side of the bridge. In addition, I also need to know what port number you will be using.
I assume that a NAT entry is needed on my ADSL router, right? Would that
be
for port 4711 (as in eau de cologne ??)
Yes, 4711 is named after the water from Cologne. :-)
(Very oldish hacker folklore that I suspect people nowadays might not know...)
And yes, if you have NAT running, you will need to forward traffic between your box, at whatever port you are using, and psilo.update.uu.se:4711. And this is UDP traffic.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: woensdag, juni 2010 14:16
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi, Hans.
H Vlems wrote:
OK Johnny, talk to me :-)
This is my plan: I intend to modify two systems to try the connection to
HECnet.
1) I have a linux system under Fedora 9 that will run the bridge
software
and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address
1.1010.
That should work without any strange problems. You'll probably want to connect the bridge to me in that case. Let me know when you are ready to try.
2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in
area
44.
I'd like to try that connection without the linux system.
You need to find someone who can act as the other end in this case. Which I suspect meaning someone running phase V and as an area router. I don't know who might be doing this. Maybe someone who do can speak up.
Anyone know if this would be compatible with DECnet over IP as Multinet does it?
Option 2 is my preferred situation since it removes a by and large
unknown
factor from the equation (the linux box).
Sure. We just need to identify someone you can connect to.
So, what do I need to know and to do to make this work?
Someone to connect to...
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: maandag, juni 2010 21:03
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
H Vlems wrote:
What I meant with the phase III-IV-V answer is that direct connectivity
between a phase V and phase III system won't work. But poor man's
routing
will work with a phase IV node in between. Functionality of course is
limited by the phase III host :-)
I wonder if phase III to phase V neccesarily will not work. However, DEC
never guaranteed that it will work, nor did they ever try it.
But you're absolutely right that very few people will have a phase III
system, RT-11 being the most likely candidate?
Probably. Or if someone is running some old versions of other systems.
I've seen the bridge program, but am not sure how to make the .conf
file
work. Is it possible to use DECnet address 1.1010 to try and make this
work?
Yes. 1.1010 is not used by anyone, so that node number would be ok to use to test.
But you also need to talk with me (or someone else) with the bridge running, to act as the remote end.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Johnny Billquist
Verzonden: maandag, juni 2010 11:02
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
DECnet phase IV nodes are backwards compatible with phase III.
Yes. But the question here was if phase V will interoperate with phase III. I don't know the answer to that one, but on the other hand, I
don't
think anyone around is running phase III anyway.
There are no restrictions in functionality between phase IV nodes and
phase
V as seen by the unpriviledged user. Area routing may be an issue on
Alpha,
and of course ncl is more of a pain to remember than ncp ;-)
True, as far as that goes.
However, I am not sure that a phase V node can operate as a phase IV area router.
Someone else pointed out that although DEC claimed that alphas could
not
be area routers, that information is incorrect, and you can just tell
an
Alpha VMS phase IV node to be an area router, if you want to.
However, DECnet+ is phase V, and all bets are off. :-)
And yes, not only are the NCL commands more difficult to remember (atleast for me), the node name management is way more difficult as well. Do anyone know how you copy a nodename database from another machine with DECnet+?
Two questions:
1-May I use area 44?
Sure.
2-Is there a short guide to set up DECnet over IP to connect to
HECnet?
Not that I know of. Maybe Mark Wickens have something on hecnet.eu?
My page (http://www.update.uu.se/~bqt/hecnet.html) only have
information
about the bridge.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Marc Chametzky
Verzonden: maandag, juni 2010 0:04
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
DECnet-Plus isn't
able to connect, or at least reliably connect to all OS's that can
potentially be on HECnet. I forget what all OS's I was having issues
with, I know one was RSTS/E v10.1, but I want to say it also included
VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase
IV,
all these issues went away. These were things as simple as SET HOST.
It's probably that DECnet-Plus (Phase V) cannot speak with DECnet
Phase
III (such as on RSTS/E and TOPS-10/20). That's my guess anyway.
Phase V should be able to communicate with VAX/VMS since that's Phase IV, which is the gold standard of DECnet, IMHO.
--Marc
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte:
06/27/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte:
06/28/10
08:37:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
07/01/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10
08:35:00
pcap, if I saw the other emails right.
That needs to be installed, and is something I cannot help with in much detail, since it differs between different Linux distros, and I'm not a big Linux-person myself... :-)
Johnny
H Vlems wrote:
First I'll have to build the codefile.
I used the command from the makefile and got a *lot* of error messages.
I'm not a C expert but apparently I'm missing a component, LCAP perhaps?
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Sampsa Laine
Verzonden: donderdag, juli 2010 22:13
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
You don't need your own port, I run mine on 4711 and it works fine - the key thing is that the other end knows where you are, i.e. address and port..
The port is passed as the command line parameter to the bridge program, e.g.:
./bridge 4711
runs it on the standard port.
Sampsa
On 1 Jul 2010, at 21:10, H Vlems wrote:
OK, I understand that part (I think) of the bridge program.
I wasn't aware that I'd need my own port number. I'll opt for 4744, if that
is alright.
Do I need to configure this somewhere (like in the .conf file)?
Hans
PS
My apologies for all these questions but I haven't seen a manual about the
bridge program....
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: donderdag, juli 2010 15:45
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
OK, let's try the bridge option first. Could you give me a sample .conf
file
that I can use?
Hmm. Not one that you can use straight away, no.
However, it should look something like this:
================
[bridge]
local <your ethernet interface name>
update psilo.update.uu.se:4711
[decnet]
local
update
=================
And that's it. What your local ethernet name is, I have no idea.
My external IP address is:
Name: osmium.homeip.net
Address: 87.209.50.192
That is something I need for my side of the bridge. In addition, I also
need to know what port number you will be using.
I assume that a NAT entry is needed on my ADSL router, right? Would that
be
for port 4711 (as in eau de cologne ??)
Yes, 4711 is named after the water from Cologne. :-)
(Very oldish hacker folklore that I suspect people nowadays might not
know...)
And yes, if you have NAT running, you will need to forward traffic
between your box, at whatever port you are using, and
psilo.update.uu.se:4711. And this is UDP traffic.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: woensdag, juni 2010 14:16
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi, Hans.
H Vlems wrote:
OK Johnny, talk to me :-)
This is my plan: I intend to modify two systems to try the connection to
HECnet.
1) I have a linux system under Fedora 9 that will run the bridge software
and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address
1.1010.
That should work without any strange problems. You'll probably want to
connect the bridge to me in that case. Let me know when you are ready to
try.
2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in
area
44.
I'd like to try that connection without the linux system.
You need to find someone who can act as the other end in this case.
Which I suspect meaning someone running phase V and as an area router. I
don't know who might be doing this. Maybe someone who do can speak up.
Anyone know if this would be compatible with DECnet over IP as Multinet
does it?
Option 2 is my preferred situation since it removes a by and large
unknown
factor from the equation (the linux box).
Sure. We just need to identify someone you can connect to.
So, what do I need to know and to do to make this work?
Someone to connect to...
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: maandag, juni 2010 21:03
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
H Vlems wrote:
What I meant with the phase III-IV-V answer is that direct connectivity
between a phase V and phase III system won't work. But poor man's
routing
will work with a phase IV node in between. Functionality of course is
limited by the phase III host :-)
I wonder if phase III to phase V neccesarily will not work. However, DEC
never guaranteed that it will work, nor did they ever try it.
But you're absolutely right that very few people will have a phase III
system, RT-11 being the most likely candidate?
Probably. Or if someone is running some old versions of other systems.
I've seen the bridge program, but am not sure how to make the .conf file
work. Is it possible to use DECnet address 1.1010 to try and make this
work?
Yes. 1.1010 is not used by anyone, so that node number would be ok to
use to test.
But you also need to talk with me (or someone else) with the bridge
running, to act as the remote end.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: maandag, juni 2010 11:02
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
DECnet phase IV nodes are backwards compatible with phase III.
Yes. But the question here was if phase V will interoperate with phase
III. I don't know the answer to that one, but on the other hand, I don't
think anyone around is running phase III anyway.
There are no restrictions in functionality between phase IV nodes and
phase
V as seen by the unpriviledged user. Area routing may be an issue on
Alpha,
and of course ncl is more of a pain to remember than ncp ;-)
True, as far as that goes.
However, I am not sure that a phase V node can operate as a phase IV
area router.
Someone else pointed out that although DEC claimed that alphas could not
be area routers, that information is incorrect, and you can just tell an
Alpha VMS phase IV node to be an area router, if you want to.
However, DECnet+ is phase V, and all bets are off. :-)
And yes, not only are the NCL commands more difficult to remember
(atleast for me), the node name management is way more difficult as
well. Do anyone know how you copy a nodename database from another
machine with DECnet+?
Two questions:
1-May I use area 44?
Sure.
2-Is there a short guide to set up DECnet over IP to connect to HECnet?
Not that I know of. Maybe Mark Wickens have something on hecnet.eu?
My page (http://www.update.uu.se/~bqt/hecnet.html) only have information
about the bridge.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Marc Chametzky
Verzonden: maandag, juni 2010 0:04
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
DECnet-Plus isn't
able to connect, or at least reliably connect to all OS's that can
potentially be on HECnet. I forget what all OS's I was having issues
with, I know one was RSTS/E v10.1, but I want to say it also included
VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase
IV,
all these issues went away. These were things as simple as SET HOST.
It's probably that DECnet-Plus (Phase V) cannot speak with DECnet Phase
III (such as on RSTS/E and TOPS-10/20). That's my guess anyway.
Phase V should be able to communicate with VAX/VMS since that's Phase
IV, which is the gold standard of DECnet, IMHO.
--Marc
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte:
06/27/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte:
06/28/10
08:37:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10
08:35:00
Steve, thanks! But I guess libpcap isn't even installed so I'd better check
that first!
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Steve Davidson
Verzonden: zondag, juli 2010 19:06
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hans,
You may have to symbolically link libpcap.so to libpcap.so.<version> or
something like that. That's what I had to do for NetBSD.
-Steve
Johnny, as soon as I've figured out how this works I'll write a manual for
you :-)
But you've got to guide me through the entire painful process first.
I had to shut down my Fedora 9 workstation because of the heat.
The error messages I got while attempting to compile the source were all
related to 'pcap'. Any suggestions?
Hans
PS
Later in the evening when the system is up again I'll post more
information.
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: vrijdag, juli 2010 9:50
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
You don't need "your own" port number. You need a port number. You are
free to pick any that isn't used by something else on your system.
That said, 4744 works just as fine as anything else, including 4711. As
Sampsa pointed out, you can use 4711 as well, if you want to. It only
needs to be unique on your system. What ports I (or anyone else) is
using, does not affect you more than that you have to have that
information in your conf-file.
Your own port number is specified on the command line, as mentioned as
well.
Oh, and the reason you haven't seen a manual about the bridge program is
because I've never written one. :-)
Feel free to contribute... ;-)
Johnny
H Vlems wrote:
OK, I understand that part (I think) of the bridge program.
I wasn't aware that I'd need my own port number. I'll opt for 4744, if
that
is alright.
Do I need to configure this somewhere (like in the .conf file)?
Hans
PS
My apologies for all these questions but I haven't seen a manual about
the
bridge program....
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: donderdag, juli 2010 15:45
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
OK, let's try the bridge option first. Could you give me a sample .conf
file
that I can use?
Hmm. Not one that you can use straight away, no.
However, it should look something like this:
================
[bridge]
local <your ethernet interface name>
update psilo.update.uu.se:4711
[decnet]
local
update
=================
And that's it. What your local ethernet name is, I have no idea.
My external IP address is:
Name: osmium.homeip.net
Address: 87.209.50.192
That is something I need for my side of the bridge. In addition, I also
need to know what port number you will be using.
I assume that a NAT entry is needed on my ADSL router, right? Would
that
be
for port 4711 (as in eau de cologne ??)
Yes, 4711 is named after the water from Cologne. :-)
(Very oldish hacker folklore that I suspect people nowadays might not
know...)
And yes, if you have NAT running, you will need to forward traffic
between your box, at whatever port you are using, and
psilo.update.uu.se:4711. And this is UDP traffic.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Johnny Billquist
Verzonden: woensdag, juni 2010 14:16
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi, Hans.
H Vlems wrote:
OK Johnny, talk to me :-)
This is my plan: I intend to modify two systems to try the connection
to
HECnet.
1) I have a linux system under Fedora 9 that will run the bridge
software
and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address
1.1010.
That should work without any strange problems. You'll probably want to
connect the bridge to me in that case. Let me know when you are ready
to
try.
2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V,
in
area
44.
I'd like to try that connection without the linux system.
You need to find someone who can act as the other end in this case.
Which I suspect meaning someone running phase V and as an area router.
I
don't know who might be doing this. Maybe someone who do can speak up.
Anyone know if this would be compatible with DECnet over IP as Multinet
does it?
Option 2 is my preferred situation since it removes a by and large
unknown
factor from the equation (the linux box).
Sure. We just need to identify someone you can connect to.
So, what do I need to know and to do to make this work?
Someone to connect to...
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Johnny Billquist
Verzonden: maandag, juni 2010 21:03
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
H Vlems wrote:
What I meant with the phase III-IV-V answer is that direct
connectivity
between a phase V and phase III system won't work. But poor man's
routing
will work with a phase IV node in between. Functionality of course is
limited by the phase III host :-)
I wonder if phase III to phase V neccesarily will not work. However,
DEC
never guaranteed that it will work, nor did they ever try it.
But you're absolutely right that very few people will have a phase
III
system, RT-11 being the most likely candidate?
Probably. Or if someone is running some old versions of other systems.
I've seen the bridge program, but am not sure how to make the .conf
file
work. Is it possible to use DECnet address 1.1010 to try and make
this
work?
Yes. 1.1010 is not used by anyone, so that node number would be ok to
use to test.
But you also need to talk with me (or someone else) with the bridge
running, to act as the remote end.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Johnny Billquist
Verzonden: maandag, juni 2010 11:02
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
DECnet phase IV nodes are backwards compatible with phase III.
Yes. But the question here was if phase V will interoperate with
phase
III. I don't know the answer to that one, but on the other hand, I
don't
think anyone around is running phase III anyway.
There are no restrictions in functionality between phase IV nodes
and
phase
V as seen by the unpriviledged user. Area routing may be an issue on
Alpha,
and of course ncl is more of a pain to remember than ncp ;-)
True, as far as that goes.
However, I am not sure that a phase V node can operate as a phase IV
area router.
Someone else pointed out that although DEC claimed that alphas could
not
be area routers, that information is incorrect, and you can just tell
an
Alpha VMS phase IV node to be an area router, if you want to.
However, DECnet+ is phase V, and all bets are off. :-)
And yes, not only are the NCL commands more difficult to remember
(atleast for me), the node name management is way more difficult as
well. Do anyone know how you copy a nodename database from another
machine with DECnet+?
Two questions:
1-May I use area 44?
Sure.
2-Is there a short guide to set up DECnet over IP to connect to
HECnet?
Not that I know of. Maybe Mark Wickens have something on hecnet.eu?
My page (http://www.update.uu.se/~bqt/hecnet.html) only have
information
about the bridge.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Marc Chametzky
Verzonden: maandag, juni 2010 0:04
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
DECnet-Plus isn't
able to connect, or at least reliably connect to all OS's that can
potentially be on HECnet. I forget what all OS's I was having
issues
with, I know one was RSTS/E v10.1, but I want to say it also
included
VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase
IV,
all these issues went away. These were things as simple as SET
HOST.
It's probably that DECnet-Plus (Phase V) cannot speak with DECnet
Phase
III (such as on RSTS/E and TOPS-10/20). That's my guess anyway.
Phase V should be able to communicate with VAX/VMS since that's
Phase
IV, which is the gold standard of DECnet, IMHO.
--Marc
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte:
06/27/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte:
06/28/10
08:37:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
07/01/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
07/01/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2981 - datum van uitgifte: 07/04/10
08:35:00
OK, i didn t install that package as an add-on. It s probably not a component of Fedora 9.
BTW I have DECnet OSI running on a VAX. It is now a question of figuring out what IP ports it uses and put them in the NAT service list on my ADSL router.
My outside IP address is pointed to by the name osmium.homeip.net (nslookup translates this to an IP address).
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Joe Ferraro Verzonden: zondag, juli 2010 20:06 Aan: hecnet at update.uu.se Onderwerp: Re: [HECnet] Attaching to hecnet
Hans, Make sure you have libpcap-devel installed. I'm not looking at the bridge code at the moment, but you'll obviously want to make sure that you are pointing to your libpcap libraries when you do the compile. $ rpm -qa |grep -i libpcap # determine if packet cap libs are installed Cheers, Joe
On Sun, Jul 4, 2010 at 12:51 PM, H Vlems <hvlems at zonnet.nl> wrote:
Johnny, as soon as I've figured out how this works I'll write a manual for you :-) But you've got to guide me through the entire painful process first. I had to shut down my Fedora 9 workstation because of the heat. The error messages I got while attempting to compile the source were all related to 'pcap'. Any suggestions? Hans PS Later in the evening when the system is up again I'll post more information.
-----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist
Verzonden: vrijdag, juli 2010 9:50
Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet You don't need "your own" port number. You need a port number. You are free to pick any that isn't used by something else on your system. That said, 4744 works just as fine as anything else, including 4711. As Sampsa pointed out, you can use 4711 as well, if you want to. It only needs to be unique on your system. What ports I (or anyone else) is using, does not affect you more than that you have to have that information in your conf-file. Your own port number is specified on the command line, as mentioned as well. Oh, and the reason you haven't seen a manual about the bridge program is because I've never written one. :-) Feel free to contribute... ;-) Johnny H Vlems wrote: > OK, I understand that part (I think) of the bridge program. > I wasn't aware that I'd need my own port number. I'll opt for 4744, if that > is alright. > Do I need to configure this somewhere (like in the .conf file)? > Hans > > PS > My apologies for all these questions but I haven't seen a manual about the > bridge program.... > > > -----Oorspronkelijk bericht----- > Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens > Johnny Billquist > Verzonden: donderdag, juli 2010 15:45 > Aan: hecnet at Update.UU.SE > Onderwerp: Re: [HECnet] Attaching to hecnet > > Hi. > > H Vlems wrote: >> OK, let's try the bridge option first. Could you give me a sample .conf > file >> that I can use? > > Hmm. Not one that you can use straight away, no. > > However, it should look something like this: > ================ > [bridge] > local <your ethernet interface name> > update psilo.update.uu.se:4711 > [decnet] > local > update > ================= > > And that's it. What your local ethernet name is, I have no idea. > >> My external IP address is: >> >> Name: osmium.homeip.net >> Address: 87.209.50.192 > > That is something I need for my side of the bridge. In addition, I also > need to know what port number you will be using. > >> I assume that a NAT entry is needed on my ADSL router, right? Would that > be >> for port 4711 (as in eau de cologne ??) > > Yes, 4711 is named after the water from Cologne. :-) > (Very oldish hacker folklore that I suspect people nowadays might not > know...) > > And yes, if you have NAT running, you will need to forward traffic > between your box, at whatever port you are using, and > psilo.update.uu.se:4711. And this is UDP traffic. > > Johnny > >> Hans >> >> -----Oorspronkelijk bericht----- >> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens >> Johnny Billquist >> Verzonden: woensdag, juni 2010 14:16 >> Aan: hecnet at Update.UU.SE >> Onderwerp: Re: [HECnet] Attaching to hecnet >> >> Hi, Hans. >> >> H Vlems wrote: >>> OK Johnny, talk to me :-) >>> This is my plan: I intend to modify two systems to try the connection to >>> HECnet. >>> 1) I have a linux system under Fedora 9 that will run the bridge software >>> and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address >> 1.1010. >> >> That should work without any strange problems. You'll probably want to >> connect the bridge to me in that case. Let me know when you are ready to >> try. >> >>> 2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in >> area >>> 44. >>> I'd like to try that connection without the linux system. >> You need to find someone who can act as the other end in this case. >> Which I suspect meaning someone running phase V and as an area router. I >> don't know who might be doing this. Maybe someone who do can speak up. >> >> Anyone know if this would be compatible with DECnet over IP as Multinet >> does it? >> >>> Option 2 is my preferred situation since it removes a by and large > unknown >>> factor from the equation (the linux box). >> Sure. We just need to identify someone you can connect to. >> >>> So, what do I need to know and to do to make this work? >> Someone to connect to... >> >> Johnny >> >>> Hans >>> >>> -----Oorspronkelijk bericht----- >>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens >>> Johnny Billquist >>> Verzonden: maandag, juni 2010 21:03 >>> Aan: hecnet at Update.UU.SE >>> Onderwerp: Re: [HECnet] Attaching to hecnet >>> >>> H Vlems wrote: >>>> What I meant with the phase III-IV-V answer is that direct connectivity >>>> between a phase V and phase III system won't work. But poor man's > routing >>>> will work with a phase IV node in between. Functionality of course is >>>> limited by the phase III host :-) >>> I wonder if phase III to phase V neccesarily will not work. However, DEC >>> never guaranteed that it will work, nor did they ever try it. >>> >>>> But you're absolutely right that very few people will have a phase III >>>> system, RT-11 being the most likely candidate? >>> Probably. Or if someone is running some old versions of other systems. >>> >>>> I've seen the bridge program, but am not sure how to make the .conf file >>>> work. Is it possible to use DECnet address 1.1010 to try and make this >>> work? >>> >>> Yes. 1.1010 is not used by anyone, so that node number would be ok to >>> use to test. >>> But you also need to talk with me (or someone else) with the bridge >>> running, to act as the remote end. >>> >>> Johnny >>> >>>> Hans >>>> >>>> -----Oorspronkelijk bericht----- >>>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens >>>> Johnny Billquist >>>> Verzonden: maandag, juni 2010 11:02 >>>> Aan: hecnet at Update.UU.SE >>>> Onderwerp: Re: [HECnet] Attaching to hecnet >>>> >>>> Hi. >>>> >>>> H Vlems wrote: >>>>> DECnet phase IV nodes are backwards compatible with phase III. >>>> Yes. But the question here was if phase V will interoperate with phase >>>> III. I don't know the answer to that one, but on the other hand, I don't > >>>> think anyone around is running phase III anyway. >>>> >>>>> There are no restrictions in functionality between phase IV nodes and >>>> phase >>>>> V as seen by the unpriviledged user. Area routing may be an issue on >>>> Alpha, >>>>> and of course ncl is more of a pain to remember than ncp ;-) >>>> True, as far as that goes. >>>> However, I am not sure that a phase V node can operate as a phase IV >>>> area router. >>>> >>>> Someone else pointed out that although DEC claimed that alphas could not > >>>> be area routers, that information is incorrect, and you can just tell an > >>>> Alpha VMS phase IV node to be an area router, if you want to. >>>> >>>> However, DECnet+ is phase V, and all bets are off. :-) >>>> >>>> And yes, not only are the NCL commands more difficult to remember >>>> (atleast for me), the node name management is way more difficult as >>>> well. Do anyone know how you copy a nodename database from another >>>> machine with DECnet+? >>>> >>>>> Two questions: >>>>> 1-May I use area 44? >>>> Sure. >>>> >>>>> 2-Is there a short guide to set up DECnet over IP to connect to HECnet? >>>> Not that I know of. Maybe Mark Wickens have something on hecnet.eu? >>>> My page (http://www.update.uu.se/~bqt/hecnet.html) only have information > >>>> about the bridge. >>>> >>>> Johnny >>>> >>>>> Hans >>>>> -----Oorspronkelijk bericht----- >>>>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] > Namens >>>>> Marc Chametzky >>>>> Verzonden: maandag, juni 2010 0:04 >>>>> Aan: hecnet at Update.UU.SE >>>>> Onderwerp: Re: [HECnet] Attaching to hecnet >>>>> >>>>>> DECnet-Plus isn't >>>>>> able to connect, or at least reliably connect to all OS's that can >>>>>> potentially be on HECnet. I forget what all OS's I was having issues >>>>>> with, I know one was RSTS/E v10.1, but I want to say it also included >>>>>> VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase > IV, >>>>>> all these issues went away. These were things as simple as SET HOST. >>>>> It's probably that DECnet-Plus (Phase V) cannot speak with DECnet Phase > >>>>> III (such as on RSTS/E and TOPS-10/20). That's my guess anyway. >>>>> >>>>> Phase V should be able to communicate with VAX/VMS since that's Phase >>>>> IV, which is the gold standard of DECnet, IMHO. >>>>> >>>>> --Marc >>>>> Geen virus gevonden in het binnenkomende-bericht. >>>>> Gecontroleerd door AVG - www.avg.com >>>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte: >>>> 06/27/10 >>>>> 08:35:00 >>>>> >>>> Geen virus gevonden in het binnenkomende-bericht. >>>> Gecontroleerd door AVG - www.avg.com >>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte: >>> 06/28/10 >>>> 08:37:00 >>>> >>> Geen virus gevonden in het binnenkomende-bericht. >>> Gecontroleerd door AVG - www.avg.com >>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: >> 06/28/10 >>> 20:35:00 >>> >> Geen virus gevonden in het binnenkomende-bericht. >> Gecontroleerd door AVG - www.avg.com >> Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: > 06/28/10 >> 20:35:00 >> > Geen virus gevonden in het binnenkomende-bericht. > Gecontroleerd door AVG - www.avg.com > Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10 > 08:35:00 > Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10 08:35:00
Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2981 - datum van uitgifte: 07/04/10 08:35:00
Hans,
Make sure you have libpcap-devel installed. I'm not looking at the bridge code at the moment, but you'll obviously want to make sure that you are pointing to your libpcap libraries when you do the compile.
$ rpm -qa |grep -i libpcap # determine if packet cap libs are installed
Cheers,
Joe
On Sun, Jul 4, 2010 at 12:51 PM, H Vlems <hvlems at zonnet.nl> wrote:
Johnny, as soon as I've figured out how this works I'll write a manual for
you :-)
But you've got to guide me through the entire painful process first.
I had to shut down my Fedora 9 workstation because of the heat.
The error messages I got while attempting to compile the source were all
related to 'pcap'. Any suggestions?
Hans
PS
Later in the evening when the system is up again I'll post more information.
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: vrijdag, juli 2010 9:50
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
You don't need "your own" port number. You need a port number. You are
free to pick any that isn't used by something else on your system.
That said, 4744 works just as fine as anything else, including 4711. As
Sampsa pointed out, you can use 4711 as well, if you want to. It only
needs to be unique on your system. What ports I (or anyone else) is
using, does not affect you more than that you have to have that
information in your conf-file.
Your own port number is specified on the command line, as mentioned as well.
Oh, and the reason you haven't seen a manual about the bridge program is
because I've never written one. :-)
Feel free to contribute... ;-)
Johnny
H Vlems wrote:
> OK, I understand that part (I think) of the bridge program.
> I wasn't aware that I'd need my own port number. I'll opt for 4744, if
that
> is alright.
> Do I need to configure this somewhere (like in the .conf file)?
> Hans
>
> PS
> My apologies for all these questions but I haven't seen a manual about the
> bridge program....
>
>
> -----Oorspronkelijk bericht-----
> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
> Johnny Billquist
> Verzonden: donderdag, juli 2010 15:45
> Aan: hecnet at Update.UU.SE
> Onderwerp: Re: [HECnet] Attaching to hecnet
>
> Hi.
>
> H Vlems wrote:
>> OK, let's try the bridge option first. Could you give me a sample .conf
> file
>> that I can use?
>
> Hmm. Not one that you can use straight away, no.
>
> However, it should look something like this:
> ================
> [bridge]
> local <your ethernet interface name>
> update psilo.update.uu.se:4711
> [decnet]
> local
> update
> =================
>
> And that's it. What your local ethernet name is, I have no idea.
>
>> My external IP address is:
>>
>> Name: osmium.homeip.net
>> Address: 87.209.50.192
>
> That is something I need for my side of the bridge. In addition, I also
> need to know what port number you will be using.
>
>> I assume that a NAT entry is needed on my ADSL router, right? Would that
> be
>> for port 4711 (as in eau de cologne ??)
>
> Yes, 4711 is named after the water from Cologne. :-)
> (Very oldish hacker folklore that I suspect people nowadays might not
> know...)
>
> And yes, if you have NAT running, you will need to forward traffic
> between your box, at whatever port you are using, and
> psilo.update.uu.se:4711. And this is UDP traffic.
>
> Johnny
>
>> Hans
>>
>> -----Oorspronkelijk bericht-----
>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
>> Johnny Billquist
>> Verzonden: woensdag, juni 2010 14:16
>> Aan: hecnet at Update.UU.SE
>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>
>> Hi, Hans.
>>
>> H Vlems wrote:
>>> OK Johnny, talk to me :-)
>>> This is my plan: I intend to modify two systems to try the connection to
>>> HECnet.
>>> 1) I have a linux system under Fedora 9 that will run the bridge
software
>>> and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address
>> 1.1010.
>>
>> That should work without any strange problems. You'll probably want to
>> connect the bridge to me in that case. Let me know when you are ready to
>> try.
>>
>>> 2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in
>> area
>>> 44.
>>> I'd like to try that connection without the linux system.
>> You need to find someone who can act as the other end in this case.
>> Which I suspect meaning someone running phase V and as an area router. I
>> don't know who might be doing this. Maybe someone who do can speak up.
>>
>> Anyone know if this would be compatible with DECnet over IP as Multinet
>> does it?
>>
>>> Option 2 is my preferred situation since it removes a by and large
> unknown
>>> factor from the equation (the linux box).
>> Sure. We just need to identify someone you can connect to.
>>
>>> So, what do I need to know and to do to make this work?
>> Someone to connect to...
>>
>> Johnny
>>
>>> Hans
>>>
>>> -----Oorspronkelijk bericht-----
>>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
>>> Johnny Billquist
>>> Verzonden: maandag, juni 2010 21:03
>>> Aan: hecnet at Update.UU.SE
>>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>>
>>> H Vlems wrote:
>>>> What I meant with the phase III-IV-V answer is that direct connectivity
>>>> between a phase V and phase III system won't work. But poor man's
> routing
>>>> will work with a phase IV node in between. Functionality of course is
>>>> limited by the phase III host :-)
>>> I wonder if phase III to phase V neccesarily will not work. However, DEC
>>> never guaranteed that it will work, nor did they ever try it.
>>>
>>>> But you're absolutely right that very few people will have a phase III
>>>> system, RT-11 being the most likely candidate?
>>> Probably. Or if someone is running some old versions of other systems.
>>>
>>>> I've seen the bridge program, but am not sure how to make the .conf
file
>>>> work. Is it possible to use DECnet address 1.1010 to try and make this
>>> work?
>>>
>>> Yes. 1.1010 is not used by anyone, so that node number would be ok to
>>> use to test.
>>> But you also need to talk with me (or someone else) with the bridge
>>> running, to act as the remote end.
>>>
>>> Johnny
>>>
>>>> Hans
>>>>
>>>> -----Oorspronkelijk bericht-----
>>>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
>>>> Johnny Billquist
>>>> Verzonden: maandag, juni 2010 11:02
>>>> Aan: hecnet at Update.UU.SE
>>>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>>>
>>>> Hi.
>>>>
>>>> H Vlems wrote:
>>>>> DECnet phase IV nodes are backwards compatible with phase III.
>>>> Yes. But the question here was if phase V will interoperate with phase
>>>> III. I don't know the answer to that one, but on the other hand, I
don't
>
>>>> think anyone around is running phase III anyway.
>>>>
>>>>> There are no restrictions in functionality between phase IV nodes and
>>>> phase
>>>>> V as seen by the unpriviledged user. Area routing may be an issue on
>>>> Alpha,
>>>>> and of course ncl is more of a pain to remember than ncp ;-)
>>>> True, as far as that goes.
>>>> However, I am not sure that a phase V node can operate as a phase IV
>>>> area router.
>>>>
>>>> Someone else pointed out that although DEC claimed that alphas could
not
>
>>>> be area routers, that information is incorrect, and you can just tell
an
>
>>>> Alpha VMS phase IV node to be an area router, if you want to.
>>>>
>>>> However, DECnet+ is phase V, and all bets are off. :-)
>>>>
>>>> And yes, not only are the NCL commands more difficult to remember
>>>> (atleast for me), the node name management is way more difficult as
>>>> well. Do anyone know how you copy a nodename database from another
>>>> machine with DECnet+?
>>>>
>>>>> Two questions:
>>>>> 1-May I use area 44?
>>>> Sure.
>>>>
>>>>> 2-Is there a short guide to set up DECnet over IP to connect to
HECnet?
>>>> Not that I know of. Maybe Mark Wickens have something on hecnet.eu?
>>>> My page (http://www.update.uu.se/~bqt/hecnet.html) only have
information
>
>>>> about the bridge.
>>>>
>>>> Johnny
>>>>
>>>>> Hans
>>>>> -----Oorspronkelijk bericht-----
>>>>> Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
> Namens
>>>>> Marc Chametzky
>>>>> Verzonden: maandag, juni 2010 0:04
>>>>> Aan: hecnet at Update.UU.SE
>>>>> Onderwerp: Re: [HECnet] Attaching to hecnet
>>>>>
>>>>>> DECnet-Plus isn't
>>>>>> able to connect, or at least reliably connect to all OS's that can
>>>>>> potentially be on HECnet. I forget what all OS's I was having issues
>>>>>> with, I know one was RSTS/E v10.1, but I want to say it also included
>>>>>> VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase
> IV,
>>>>>> all these issues went away. These were things as simple as SET HOST.
>>>>> It's probably that DECnet-Plus (Phase V) cannot speak with DECnet
Phase
>
>>>>> III (such as on RSTS/E and TOPS-10/20). That's my guess anyway.
>>>>>
>>>>> Phase V should be able to communicate with VAX/VMS since that's Phase
>>>>> IV, which is the gold standard of DECnet, IMHO.
>>>>>
>>>>> --Marc
>>>>> Geen virus gevonden in het binnenkomende-bericht.
>>>>> Gecontroleerd door AVG - www.avg.com
>>>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte:
>>>> 06/27/10
>>>>> 08:35:00
>>>>>
>>>> Geen virus gevonden in het binnenkomende-bericht.
>>>> Gecontroleerd door AVG - www.avg.com
>>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte:
>>> 06/28/10
>>>> 08:37:00
>>>>
>>> Geen virus gevonden in het binnenkomende-bericht.
>>> Gecontroleerd door AVG - www.avg.com
>>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
>> 06/28/10
>>> 20:35:00
>>>
>> Geen virus gevonden in het binnenkomende-bericht.
>> Gecontroleerd door AVG - www.avg.com
>> Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
> 06/28/10
>> 20:35:00
>>
> Geen virus gevonden in het binnenkomende-bericht.
> Gecontroleerd door AVG - www.avg.com
> Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
07/01/10
> 08:35:00
>
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10
08:35:00
Hans,
You may have to symbolically link libpcap.so to libpcap.so.<version> or
something like that. That's what I had to do for NetBSD.
-Steve
Johnny, as soon as I've figured out how this works I'll write a manual for
you :-)
But you've got to guide me through the entire painful process first.
I had to shut down my Fedora 9 workstation because of the heat.
The error messages I got while attempting to compile the source were all
related to 'pcap'. Any suggestions?
Hans
PS
Later in the evening when the system is up again I'll post more information.
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: vrijdag, juli 2010 9:50
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
You don't need "your own" port number. You need a port number. You are
free to pick any that isn't used by something else on your system.
That said, 4744 works just as fine as anything else, including 4711. As
Sampsa pointed out, you can use 4711 as well, if you want to. It only
needs to be unique on your system. What ports I (or anyone else) is
using, does not affect you more than that you have to have that
information in your conf-file.
Your own port number is specified on the command line, as mentioned as well.
Oh, and the reason you haven't seen a manual about the bridge program is
because I've never written one. :-)
Feel free to contribute... ;-)
Johnny
H Vlems wrote:
OK, I understand that part (I think) of the bridge program.
I wasn't aware that I'd need my own port number. I'll opt for 4744, if
that
is alright.
Do I need to configure this somewhere (like in the .conf file)?
Hans
PS
My apologies for all these questions but I haven't seen a manual about the
bridge program....
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: donderdag, juli 2010 15:45
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
OK, let's try the bridge option first. Could you give me a sample .conf
file
that I can use?
Hmm. Not one that you can use straight away, no.
However, it should look something like this:
================
[bridge]
local <your ethernet interface name>
update psilo.update.uu.se:4711
[decnet]
local
update
=================
And that's it. What your local ethernet name is, I have no idea.
My external IP address is:
Name: osmium.homeip.net
Address: 87.209.50.192
That is something I need for my side of the bridge. In addition, I also
need to know what port number you will be using.
I assume that a NAT entry is needed on my ADSL router, right? Would that
be
for port 4711 (as in eau de cologne ??)
Yes, 4711 is named after the water from Cologne. :-)
(Very oldish hacker folklore that I suspect people nowadays might not
know...)
And yes, if you have NAT running, you will need to forward traffic
between your box, at whatever port you are using, and
psilo.update.uu.se:4711. And this is UDP traffic.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: woensdag, juni 2010 14:16
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi, Hans.
H Vlems wrote:
OK Johnny, talk to me :-)
This is my plan: I intend to modify two systems to try the connection to
HECnet.
1) I have a linux system under Fedora 9 that will run the bridge
software
and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address
1.1010.
That should work without any strange problems. You'll probably want to
connect the bridge to me in that case. Let me know when you are ready to
try.
2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in
area
44.
I'd like to try that connection without the linux system.
You need to find someone who can act as the other end in this case.
Which I suspect meaning someone running phase V and as an area router. I
don't know who might be doing this. Maybe someone who do can speak up.
Anyone know if this would be compatible with DECnet over IP as Multinet
does it?
Option 2 is my preferred situation since it removes a by and large
unknown
factor from the equation (the linux box).
Sure. We just need to identify someone you can connect to.
So, what do I need to know and to do to make this work?
Someone to connect to...
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: maandag, juni 2010 21:03
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
H Vlems wrote:
What I meant with the phase III-IV-V answer is that direct connectivity
between a phase V and phase III system won't work. But poor man's
routing
will work with a phase IV node in between. Functionality of course is
limited by the phase III host :-)
I wonder if phase III to phase V neccesarily will not work. However, DEC
never guaranteed that it will work, nor did they ever try it.
But you're absolutely right that very few people will have a phase III
system, RT-11 being the most likely candidate?
Probably. Or if someone is running some old versions of other systems.
I've seen the bridge program, but am not sure how to make the .conf
file
work. Is it possible to use DECnet address 1.1010 to try and make this
work?
Yes. 1.1010 is not used by anyone, so that node number would be ok to
use to test.
But you also need to talk with me (or someone else) with the bridge
running, to act as the remote end.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Johnny Billquist
Verzonden: maandag, juni 2010 11:02
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
Hi.
H Vlems wrote:
DECnet phase IV nodes are backwards compatible with phase III.
Yes. But the question here was if phase V will interoperate with phase
III. I don't know the answer to that one, but on the other hand, I
don't
think anyone around is running phase III anyway.
There are no restrictions in functionality between phase IV nodes and
phase
V as seen by the unpriviledged user. Area routing may be an issue on
Alpha,
and of course ncl is more of a pain to remember than ncp ;-)
True, as far as that goes.
However, I am not sure that a phase V node can operate as a phase IV
area router.
Someone else pointed out that although DEC claimed that alphas could
not
be area routers, that information is incorrect, and you can just tell
an
Alpha VMS phase IV node to be an area router, if you want to.
However, DECnet+ is phase V, and all bets are off. :-)
And yes, not only are the NCL commands more difficult to remember
(atleast for me), the node name management is way more difficult as
well. Do anyone know how you copy a nodename database from another
machine with DECnet+?
Two questions:
1-May I use area 44?
Sure.
2-Is there a short guide to set up DECnet over IP to connect to
HECnet?
Not that I know of. Maybe Mark Wickens have something on hecnet.eu?
My page (http://www.update.uu.se/~bqt/hecnet.html) only have
information
about the bridge.
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
Namens
Marc Chametzky
Verzonden: maandag, juni 2010 0:04
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Attaching to hecnet
DECnet-Plus isn't
able to connect, or at least reliably connect to all OS's that can
potentially be on HECnet. I forget what all OS's I was having issues
with, I know one was RSTS/E v10.1, but I want to say it also included
VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase
IV,
all these issues went away. These were things as simple as SET HOST.
It's probably that DECnet-Plus (Phase V) cannot speak with DECnet
Phase
III (such as on RSTS/E and TOPS-10/20). That's my guess anyway.
Phase V should be able to communicate with VAX/VMS since that's Phase
IV, which is the gold standard of DECnet, IMHO.
--Marc
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte:
06/27/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte:
06/28/10
08:37:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte:
06/28/10
20:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte:
07/01/10
08:35:00
Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10
08:35:00
