On Wed, 17 Sep 2008 21:50:57 +0100, you wrote:
Yeah, that went really smoothly. Btw, I've got a spare hardware raid
controller I bought off ebay for some random reason.
I'd be willing to trade it for say a SCSI drive with a SCA connector..
Another couple of links for you, the second might be especially interesting:
http://starlet.deltatel.ru/~Laishev/kits/cc073.dcx_axpexehttp://starlet.deltatel.ru/~Laishev/kits/hp-i64vms-c-v0703-018-1.pcsi$compr…
My Itanium friend will be back tomorrow and said that he will tell me/you
which disk+tray model you'll have to look for on ebay for your system. If I
did understand it right, there are many HP disk models suitable for it because
they're the same used by HP for one of their most common storage arrays. The
only nuisance is the colour: white instead of black... Will you bare that? :-P
Unfortunately he hasn't any spare SCA disk to exchange. Speaking about the
RAID controller: when back at home he'll check if it is a model he is
interested in, then maybe he'll contact you directly to ask if you will sell
it for money or to find something interesting for you to make a deal.
BTW, where are you located? London?
G.
P.S.: Is my English understandable? I'm constantly trying to improve it and to
write as correctly as I can, but sometimes I feel very bad at writing... :-)
Yeah, that went really smoothly. Btw, I've got a spare hardware raid controller I bought off ebay for some random reason.
I'd be willing to trade it for say a SCSI drive with a SCA connector..
Sampsa
On 17 Sep 2008, at 21:46, gerry77 at mail.com wrote:
On Wed, 17 Sep 2008 14:29:23 +0100, you wrote:
No sorry, didn't realise I needed any licenses for those. I run KZPACs
(DRxx devices) on both my Alphas, and just use the AlphaBIOS
management utility when I need it.
Evidently DEC used the same device designation for more than one device type.
So DRxx are both hardware and software RAID devices (and I suspect they were
also some very old device designation back when disks were removable).
Obviously the harware feature doesn't need any PAK, but the software one...
G.
P.S.: Did you succeed in installing I64 OpenVMS via InfoServer?
On Wed, 17 Sep 2008 14:29:23 +0100, you wrote:
No sorry, didn't realise I needed any licenses for those. I run KZPACs
(DRxx devices) on both my Alphas, and just use the AlphaBIOS
management utility when I need it.
Evidently DEC used the same device designation for more than one device type.
So DRxx are both hardware and software RAID devices (and I suspect they were
also some very old device designation back when disks were removable).
Obviously the harware feature doesn't need any PAK, but the software one...
G.
P.S.: Did you succeed in installing I64 OpenVMS via InfoServer?
On 17 Sep 2008, at 13:42, gerry77 at mail.com wrote:
On Tue, 16 Sep 2008 20:15:48 +0100, you wrote:
I'm tempted to ask on c.o.v. but am a bit worried people would take it
the wrong way.
I do agree with you. Some people seems to say "I do not want to understand".
Months ago I asked something about V5.5-2 and they did not ansewer my question
but suggested to upgrade to Alpha... :-P
Yeah, I got a right bollocking for summarising the DEFCON slides in the wrong way or something. There are some grumpy grumpy old men on that group, but overall they can be very helpful and friendly.
I think it's insane that they hand out all these licenses but then no
software, what's the point?
Yes, quite strange. Not only they do offer licenses for layered products not
easily available to Hobbyists, but even the operating system itself is not
officially available. A strange position indeed. BTW, speaking about licenses:
do you happen to have any licenses not present in the usual Hobbyist offering?
E.g. we are looking for host based RAID licenses (DRxx: devices) since about
two years, to no avail! :-|
No sorry, didn't realise I needed any licenses for those. I run KZPACs (DRxx devices) on both my Alphas, and just use the AlphaBIOS management utility when I need it.
Sampsa
On Tue, 16 Sep 2008 20:15:48 +0100, you wrote:
I'm tempted to ask on c.o.v. but am a bit worried people would take it
the wrong way.
I do agree with you. Some people seems to say "I do not want to understand".
Months ago I asked something about V5.5-2 and they did not ansewer my question
but suggested to upgrade to Alpha... :-P
I think it's insane that they hand out all these licenses but then no
software, what's the point?
Yes, quite strange. Not only they do offer licenses for layered products not
easily available to Hobbyists, but even the operating system itself is not
officially available. A strange position indeed. BTW, speaking about licenses:
do you happen to have any licenses not present in the usual Hobbyist offering?
E.g. we are looking for host based RAID licenses (DRxx: devices) since about
two years, to no avail! :-|
G.
Yeah, sorry, forgot the question mark :)
I'm tempted to ask on c.o.v. but am a bit worried people would take it the wrong way.
I think it's insane that they hand out all these licenses but then no software, what's
the point?
Sampsa
On 16 Sep 2008, at 20:12, gerry77 at mail.com wrote:
On Tue, 16 Sep 2008 18:39:11 +0100, you wrote:
Your friend with the I64 on your retro network wouldn't be willing to
share some layered product installers (i.e. compilers etc), I've got
the paks but again no install media.
Is that a question? :-)
BTW, my friend actually is abroad and will be back on Thursday. Up until then
I cannot say nothing for sure, but - if I remember correctly - we do not have
anything more that what you can find on the images from HP.
Maybe, MAYBE, he found the C compiler (or was he looking for it?) but I do not
remember where, when and how :-P
I'll tell you something in the next days. If you'll not hear anything from me
write me back on Friday! :-)
G.
On Tue, 16 Sep 2008 18:39:11 +0100, you wrote:
Your friend with the I64 on your retro network wouldn't be willing to
share some layered product installers (i.e. compilers etc), I've got
the paks but again no install media.
Is that a question? :-)
BTW, my friend actually is abroad and will be back on Thursday. Up until then
I cannot say nothing for sure, but - if I remember correctly - we do not have
anything more that what you can find on the images from HP.
Maybe, MAYBE, he found the C compiler (or was he looking for it?) but I do not
remember where, when and how :-P
I'll tell you something in the next days. If you'll not hear anything from me
write me back on Friday! :-)
G.
Gerry,
Your friend with the I64 on your retro network wouldn't be willing to share some layered product installers (i.e. compilers etc), I've got the paks but again no install media.
Sampsa
On 15 Sep 2008, at 22:11, gerry77 at mail.com wrote:
On Mon, 15 Sep 2008 20:52:24 +0100, you wrote:
Yeah, the EFI stuff is ACTUALLY quite self explanatory, I think I
should be able to get the Netboot working. Now I don't actually have
a SCSI drive to do the install onto, so will have fun seeing what USB
devices will work :)
Are you sure you do want to go with a USB disk? Reading around about either
VMS or EFI USB support, it appears that it could be a nightmare... Wouldn't be
better to spend your efforts looking for a SCSI disk instead? :)
G.
Oh of course I'll get a SCSI disk in due time, like a week or so :)
But for now I'll try a USB drive, I think VMS on a pendrive would be a nice little hack.
Sampsa
On 15 Sep 2008, at 22:11, gerry77 at mail.com wrote:
On Mon, 15 Sep 2008 20:52:24 +0100, you wrote:
Yeah, the EFI stuff is ACTUALLY quite self explanatory, I think I
should be able to get the Netboot working. Now I don't actually have
a SCSI drive to do the install onto, so will have fun seeing what USB
devices will work :)
Are you sure you do want to go with a USB disk? Reading around about either
VMS or EFI USB support, it appears that it could be a nightmare... Wouldn't be
better to spend your efforts looking for a SCSI disk instead? :)
G.
On Mon, 15 Sep 2008 20:52:24 +0100, you wrote:
Yeah, the EFI stuff is ACTUALLY quite self explanatory, I think I
should be able to get the Netboot working. Now I don't actually have
a SCSI drive to do the install onto, so will have fun seeing what USB
devices will work :)
Are you sure you do want to go with a USB disk? Reading around about either
VMS or EFI USB support, it appears that it could be a nightmare... Wouldn't be
better to spend your efforts looking for a SCSI disk instead? :)
G.
Yeah, the EFI stuff is ACTUALLY quite self explanatory, I think I should be able to get the Netboot working. Now I don't actually have a SCSI drive to do the install onto, so will have fun seeing what USB devices will work :)
Sampsa
On 15 Sep 2008, at 20:50, gerry77 at mail.com wrote:
On Mon, 15 Sep 2008 14:57:25 +0100, you wrote:
You seemed to know a bit about the integrity boxes, I've just got an
rx2600, but have NO idea what to do next.
I've hooked up the management processor to a DHCP-serving LAN, but
it's not picking up an IP address. Any idea how to reset it to factory
defaults?
I've seen on comp.os.vms that you've managed to resolve your problems and I'm
glad about that because I do not know anything about Itanium hardware: I'm an
Italian DECnet group member, that's true, and we do have an Itanium system on
our network, but... That system is in Rome and I'm in Bologna (about 500 km
north of Rome), so I've never put my hands on it! :-P
If I remember correctly you'll have to fiddle with EFI menus to start a PXE
network boot (a combination of bootp and tftp) and then using InfoServer you
should be able to start OpenVMS 8.x installation, then you'll have to fiddle
again with EFI to set back boot from a local disk or you can use the SETBOOT
command procedure (maybe in SYS$MANAGER or SYS$UPDATE) which should help you
in changing EFI setting quite easily...
Let me know!
G.
On Mon, 15 Sep 2008 14:57:25 +0100, you wrote:
You seemed to know a bit about the integrity boxes, I've just got an
rx2600, but have NO idea what to do next.
I've hooked up the management processor to a DHCP-serving LAN, but
it's not picking up an IP address. Any idea how to reset it to factory
defaults?
I've seen on comp.os.vms that you've managed to resolve your problems and I'm
glad about that because I do not know anything about Itanium hardware: I'm an
Italian DECnet group member, that's true, and we do have an Itanium system on
our network, but... That system is in Rome and I'm in Bologna (about 500 km
north of Rome), so I've never put my hands on it! :-P
If I remember correctly you'll have to fiddle with EFI menus to start a PXE
network boot (a combination of bootp and tftp) and then using InfoServer you
should be able to start OpenVMS 8.x installation, then you'll have to fiddle
again with EFI to set back boot from a local disk or you can use the SETBOOT
command procedure (maybe in SYS$MANAGER or SYS$UPDATE) which should help you
in changing EFI setting quite easily...
Let me know!
G.
"Zane" == Zane H Healy <healyzh at aracnet.com> writes:
Zane> Stupid question, is it possible the SET HOST is connecting via
Zane> LAT rather than DECnet?
I wouldn't think so.
paul
Gerry,
You seemed to know a bit about the integrity boxes, I've just got an rx2600, but have NO idea what to do next.
I've hooked up the management processor to a DHCP-serving LAN, but it's not picking up an IP address. Any idea how to reset it to factory defaults?
Sampsa
On 15 Sep 2008, at 01:25, gerry77 at mail.com wrote:
On Sun, 14 Sep 2008 21:17:06 +0100, you wrote:
Anyone know where I could borrow this, I'm picking up an rx2600
tomorrow?
There are two somewhat "secret" URLs from which you can download BACKUP/IMAGE
copies of the original installation DVDs for V8.3 and V8.3-1H1.
The most curious thing is that they're directly from HP, obviously not as an
official distribution, but maybe to informally spread new Itanium releases
among Hobbyists. Anyway, no one really knows why those files are there, so
it's better to keep their URLs reserved and not so publicly available.
ftp://ftp.hp.com/pub/openvms/private/I640831H1.BCK-GZ (1.8GB)
ftp://ftp.hp.com/pub/openvms/private/I64083.BCK-GZ (1.6GB)
They were made with BACKUP/IMAGE (and not BACKUP/PHYSICAL), so they're not
directly bootable from EFI because they lack the FAT partition which is
present in the original DVD outside the ODS-2 volume. The easiest way to boot
and install from those images is to use an Alpha system with OpenVMS V8.3 to
serve them using the new InfoServer function. You'll need GZIP too.
http://docs.hp.com/en/BA322-90077/apb.html
We [1] used the InfoServer method and were up'n'running in a matter of
minutes. If you'll need further assistance (except on EFI) I'm here! :-)
If someone else offers you off-list something like Layered Products for
OpenVMS on Itanium, we'll be very grateful if you'll share with us! :-)
HTH,
G.
[1] http://decnet.ipv7.net
On Sun, 14 Sep 2008 21:17:06 +0100, you wrote:
Anyone know where I could borrow this, I'm picking up an rx2600
tomorrow?
There are two somewhat "secret" URLs from which you can download BACKUP/IMAGE
copies of the original installation DVDs for V8.3 and V8.3-1H1.
The most curious thing is that they're directly from HP, obviously not as an
official distribution, but maybe to informally spread new Itanium releases
among Hobbyists. Anyway, no one really knows why those files are there, so
it's better to keep their URLs reserved and not so publicly available.
ftp://ftp.hp.com/pub/openvms/private/I640831H1.BCK-GZ (1.8GB)
ftp://ftp.hp.com/pub/openvms/private/I64083.BCK-GZ (1.6GB)
They were made with BACKUP/IMAGE (and not BACKUP/PHYSICAL), so they're not
directly bootable from EFI because they lack the FAT partition which is
present in the original DVD outside the ODS-2 volume. The easiest way to boot
and install from those images is to use an Alpha system with OpenVMS V8.3 to
serve them using the new InfoServer function. You'll need GZIP too.
http://docs.hp.com/en/BA322-90077/apb.html
We [1] used the InfoServer method and were up'n'running in a matter of
minutes. If you'll need further assistance (except on EFI) I'm here! :-)
If someone else offers you off-list something like Layered Products for
OpenVMS on Itanium, we'll be very grateful if you'll share with us! :-)
HTH,
G.
[1] http://decnet.ipv7.net
Stupid question, is it possible the SET HOST is connecting via LAT rather than DECnet?
Zane
At 10:02 PM +0200 9/13/08, Johnny Billquist wrote:
Which all, in my eye, points to that klh10 decides to drop DECnet packets.
Johnny
Mark Abene wrote:
I admit, the fact that LAT "just works" is very puzzling to me.
Enabling debugging on dpni20 isn't very helpful, as I don't see evidence
of anything failing. The thing just doesn't transmit any DECnet traffic
over ethernet. I can SET HOST to my own machine, so I know at least in
principle the protocol is up, however only locally.
Johnny Billquist wrote:
One important detail you left out Mark, is that LAT traffic is working
fine from your klh10 machine.
Do you see any of those multicast addresses? Otherwise I think that's a
red herring.
Since LAT works, we can really narrow things down quite a lot.
Johnny
Mark Abene skrev:
So, as for my problem with Johnny's bridge, I discovered the write(2) to
bridge 0 was failing because I was compiling and linking to an outdated
libpcap. That was easily remedied and now I have DECnet traffic on my
bridged-tap. Yay. However, the problem I detailed below is still
plaguing me, and still after digging through klh10 source it remains a
mystery. Apparently the DECnet multicast addresses are maintained in
the emulated pdp10's memory, in a table called MCAT. This occurs in the
dpni20's function eth_mcatset() which calls osn_ifmcset() in osdnet.c.
Strangely, it thinks it's succeeding, and though the multicast addresses
don't appear in "netstat -ani", a "vmstat -m | grep ether_multi" shows
the in-use counter is incrementing each time, including when I add them
manually with mtest. I highly suspect that the dpni20 driver is getting
confused somewhere, since with the bridged-tap setup it maintains an
internal "10-side" IP and MAC address which is not visible to the OS's
interface table, and only manifests in the ARP table. Presently,
klh10's "enaddr" command-line utility stopped giving errors on adding
the requisite multicast addresses, but ether_multi is *not* incremented,
and the warning enaddr: No EN addr in iftab for "tap0" is given, telling
me that nothing is really happening. This is telling, since enaddr
exercises the same functions in osdnet.c that the emulator itself uses.
As a test I think I may try setting the dedicated interface to a real
ethernet instead of the virtual tap, to see if I can resolve the
multicast issues. At the moment this seems to be the show stopper.
Mark
Mark Abene wrote:
I wanted to be doing a netstat -ani, (-g only shows multicast for
ipv4/6), but the result is the same. None of the DECnet multicast
addresses are being added, most notably (and absolutely necessary) are:
ab:0:0:3:0:0 - type 6003 - for DECnet Phase IV end node Hello packets
from each host, and
ab:0:0:4:0:0 - type 6003 - for DECnet Phase IV router Hello packets from
the router.
I've tried adding these with both enaddr from KLH10 and FreeBSD's
built-in "mtest", but both return errors. This seems to be a
FreeBSD-specific problem which so far I'm unable to find the reason for.
Mark
Mark Abene wrote:
Mark Abene wrote:
I've actually made a new discovery... looking at "netstat -g", I'm
seeing that none of the multicast addresses exist that DECnet uses and
requires! This would explain why I don't see any DECnet traffic at
all.
I compiled KLH10's enaddr utility in an attempt to add the multicast
addresses manually, and I get failures for all attempts...
"SIOCADDMULTI failed - Can't assign requested address". My server's
kernel wasn't built with multicast routing enabled, which is not a
default. I'm wondering if this is the cause of the error. I'm
going to
do some further testing.
Regards
Mark
Well I was mistaken about the multicast routing, that's only for doing
DVMRP with mrouted (MBONE, etc). Local LAN multicast should work "out
of the box" on FreeBSD. Still trying to track down why this is
failing,
since it's my primary candidate for DECnet not working...
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com (primary) | OpenVMS Enthusiast |
| MONK::HEALYZH (DECnet) | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| PDP-10 Emulation and Zane's Computer Museum. |
| http://www.aracnet.com/~healyzh/ |
Which all, in my eye, points to that klh10 decides to drop DECnet packets.
Johnny
Mark Abene wrote:
I admit, the fact that LAT "just works" is very puzzling to me.
Enabling debugging on dpni20 isn't very helpful, as I don't see evidence
of anything failing. The thing just doesn't transmit any DECnet traffic
over ethernet. I can SET HOST to my own machine, so I know at least in
principle the protocol is up, however only locally.
Johnny Billquist wrote:
One important detail you left out Mark, is that LAT traffic is working
fine from your klh10 machine.
Do you see any of those multicast addresses? Otherwise I think that's a
red herring.
Since LAT works, we can really narrow things down quite a lot.
Johnny
Mark Abene skrev:
So, as for my problem with Johnny's bridge, I discovered the write(2) to
bridge 0 was failing because I was compiling and linking to an outdated
libpcap. That was easily remedied and now I have DECnet traffic on my
bridged-tap. Yay. However, the problem I detailed below is still
plaguing me, and still after digging through klh10 source it remains a
mystery. Apparently the DECnet multicast addresses are maintained in
the emulated pdp10's memory, in a table called MCAT. This occurs in the
dpni20's function eth_mcatset() which calls osn_ifmcset() in osdnet.c.
Strangely, it thinks it's succeeding, and though the multicast addresses
don't appear in "netstat -ani", a "vmstat -m | grep ether_multi" shows
the in-use counter is incrementing each time, including when I add them
manually with mtest. I highly suspect that the dpni20 driver is getting
confused somewhere, since with the bridged-tap setup it maintains an
internal "10-side" IP and MAC address which is not visible to the OS's
interface table, and only manifests in the ARP table. Presently,
klh10's "enaddr" command-line utility stopped giving errors on adding
the requisite multicast addresses, but ether_multi is *not* incremented,
and the warning enaddr: No EN addr in iftab for "tap0" is given, telling
me that nothing is really happening. This is telling, since enaddr
exercises the same functions in osdnet.c that the emulator itself uses.
As a test I think I may try setting the dedicated interface to a real
ethernet instead of the virtual tap, to see if I can resolve the
multicast issues. At the moment this seems to be the show stopper.
Mark
Mark Abene wrote:
I wanted to be doing a netstat -ani, (-g only shows multicast for
ipv4/6), but the result is the same. None of the DECnet multicast
addresses are being added, most notably (and absolutely necessary) are:
ab:0:0:3:0:0 - type 6003 - for DECnet Phase IV end node Hello packets
from each host, and
ab:0:0:4:0:0 - type 6003 - for DECnet Phase IV router Hello packets from
the router.
I've tried adding these with both enaddr from KLH10 and FreeBSD's
built-in "mtest", but both return errors. This seems to be a
FreeBSD-specific problem which so far I'm unable to find the reason for.
Mark
Mark Abene wrote:
Mark Abene wrote:
I've actually made a new discovery... looking at "netstat -g", I'm
seeing that none of the multicast addresses exist that DECnet uses and
requires! This would explain why I don't see any DECnet traffic at
all.
I compiled KLH10's enaddr utility in an attempt to add the multicast
addresses manually, and I get failures for all attempts...
"SIOCADDMULTI failed - Can't assign requested address". My server's
kernel wasn't built with multicast routing enabled, which is not a
default. I'm wondering if this is the cause of the error. I'm
going to
do some further testing.
Regards
Mark
Well I was mistaken about the multicast routing, that's only for doing
DVMRP with mrouted (MBONE, etc). Local LAN multicast should work "out
of the box" on FreeBSD. Still trying to track down why this is
failing,
since it's my primary candidate for DECnet not working...
I admit, the fact that LAT "just works" is very puzzling to me.
Enabling debugging on dpni20 isn't very helpful, as I don't see evidence
of anything failing. The thing just doesn't transmit any DECnet traffic
over ethernet. I can SET HOST to my own machine, so I know at least in
principle the protocol is up, however only locally.
Johnny Billquist wrote:
One important detail you left out Mark, is that LAT traffic is working
fine from your klh10 machine.
Do you see any of those multicast addresses? Otherwise I think that's a
red herring.
Since LAT works, we can really narrow things down quite a lot.
Johnny
Mark Abene skrev:
So, as for my problem with Johnny's bridge, I discovered the write(2) to
bridge 0 was failing because I was compiling and linking to an outdated
libpcap. That was easily remedied and now I have DECnet traffic on my
bridged-tap. Yay. However, the problem I detailed below is still
plaguing me, and still after digging through klh10 source it remains a
mystery. Apparently the DECnet multicast addresses are maintained in
the emulated pdp10's memory, in a table called MCAT. This occurs in the
dpni20's function eth_mcatset() which calls osn_ifmcset() in osdnet.c.
Strangely, it thinks it's succeeding, and though the multicast addresses
don't appear in "netstat -ani", a "vmstat -m | grep ether_multi" shows
the in-use counter is incrementing each time, including when I add them
manually with mtest. I highly suspect that the dpni20 driver is getting
confused somewhere, since with the bridged-tap setup it maintains an
internal "10-side" IP and MAC address which is not visible to the OS's
interface table, and only manifests in the ARP table. Presently,
klh10's "enaddr" command-line utility stopped giving errors on adding
the requisite multicast addresses, but ether_multi is *not* incremented,
and the warning enaddr: No EN addr in iftab for "tap0" is given, telling
me that nothing is really happening. This is telling, since enaddr
exercises the same functions in osdnet.c that the emulator itself uses.
As a test I think I may try setting the dedicated interface to a real
ethernet instead of the virtual tap, to see if I can resolve the
multicast issues. At the moment this seems to be the show stopper.
Mark
Mark Abene wrote:
I wanted to be doing a netstat -ani, (-g only shows multicast for
ipv4/6), but the result is the same. None of the DECnet multicast
addresses are being added, most notably (and absolutely necessary) are:
ab:0:0:3:0:0 - type 6003 - for DECnet Phase IV end node Hello packets
from each host, and
ab:0:0:4:0:0 - type 6003 - for DECnet Phase IV router Hello packets from
the router.
I've tried adding these with both enaddr from KLH10 and FreeBSD's
built-in "mtest", but both return errors. This seems to be a
FreeBSD-specific problem which so far I'm unable to find the reason for.
Mark
Mark Abene wrote:
Mark Abene wrote:
I've actually made a new discovery... looking at "netstat -g", I'm
seeing that none of the multicast addresses exist that DECnet uses and
requires! This would explain why I don't see any DECnet traffic at
all.
I compiled KLH10's enaddr utility in an attempt to add the multicast
addresses manually, and I get failures for all attempts...
"SIOCADDMULTI failed - Can't assign requested address". My server's
kernel wasn't built with multicast routing enabled, which is not a
default. I'm wondering if this is the cause of the error. I'm
going to
do some further testing.
Regards
Mark
Well I was mistaken about the multicast routing, that's only for doing
DVMRP with mrouted (MBONE, etc). Local LAN multicast should work "out
of the box" on FreeBSD. Still trying to track down why this is
failing,
since it's my primary candidate for DECnet not working...
One important detail you left out Mark, is that LAT traffic is working fine from your klh10 machine.
Do you see any of those multicast addresses? Otherwise I think that's a red herring.
Since LAT works, we can really narrow things down quite a lot.
Johnny
Mark Abene skrev:
So, as for my problem with Johnny's bridge, I discovered the write(2) to
bridge 0 was failing because I was compiling and linking to an outdated
libpcap. That was easily remedied and now I have DECnet traffic on my
bridged-tap. Yay. However, the problem I detailed below is still
plaguing me, and still after digging through klh10 source it remains a
mystery. Apparently the DECnet multicast addresses are maintained in
the emulated pdp10's memory, in a table called MCAT. This occurs in the
dpni20's function eth_mcatset() which calls osn_ifmcset() in osdnet.c.
Strangely, it thinks it's succeeding, and though the multicast addresses
don't appear in "netstat -ani", a "vmstat -m | grep ether_multi" shows
the in-use counter is incrementing each time, including when I add them
manually with mtest. I highly suspect that the dpni20 driver is getting
confused somewhere, since with the bridged-tap setup it maintains an
internal "10-side" IP and MAC address which is not visible to the OS's
interface table, and only manifests in the ARP table. Presently,
klh10's "enaddr" command-line utility stopped giving errors on adding
the requisite multicast addresses, but ether_multi is *not* incremented,
and the warning enaddr: No EN addr in iftab for "tap0" is given, telling
me that nothing is really happening. This is telling, since enaddr
exercises the same functions in osdnet.c that the emulator itself uses.
As a test I think I may try setting the dedicated interface to a real
ethernet instead of the virtual tap, to see if I can resolve the
multicast issues. At the moment this seems to be the show stopper.
Mark
Mark Abene wrote:
I wanted to be doing a netstat -ani, (-g only shows multicast for
ipv4/6), but the result is the same. None of the DECnet multicast
addresses are being added, most notably (and absolutely necessary) are:
ab:0:0:3:0:0 - type 6003 - for DECnet Phase IV end node Hello packets
from each host, and
ab:0:0:4:0:0 - type 6003 - for DECnet Phase IV router Hello packets from
the router.
I've tried adding these with both enaddr from KLH10 and FreeBSD's
built-in "mtest", but both return errors. This seems to be a
FreeBSD-specific problem which so far I'm unable to find the reason for.
Mark
Mark Abene wrote:
Mark Abene wrote:
I've actually made a new discovery... looking at "netstat -g", I'm
seeing that none of the multicast addresses exist that DECnet uses and
requires! This would explain why I don't see any DECnet traffic at all.
I compiled KLH10's enaddr utility in an attempt to add the multicast
addresses manually, and I get failures for all attempts...
"SIOCADDMULTI failed - Can't assign requested address". My server's
kernel wasn't built with multicast routing enabled, which is not a
default. I'm wondering if this is the cause of the error. I'm going to
do some further testing.
Regards
Mark
Well I was mistaken about the multicast routing, that's only for doing
DVMRP with mrouted (MBONE, etc). Local LAN multicast should work "out
of the box" on FreeBSD. Still trying to track down why this is failing,
since it's my primary candidate for DECnet not working...
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
So, as for my problem with Johnny's bridge, I discovered the write(2) to
bridge 0 was failing because I was compiling and linking to an outdated
libpcap. That was easily remedied and now I have DECnet traffic on my
bridged-tap. Yay. However, the problem I detailed below is still
plaguing me, and still after digging through klh10 source it remains a
mystery. Apparently the DECnet multicast addresses are maintained in
the emulated pdp10's memory, in a table called MCAT. This occurs in the
dpni20's function eth_mcatset() which calls osn_ifmcset() in osdnet.c.
Strangely, it thinks it's succeeding, and though the multicast addresses
don't appear in "netstat -ani", a "vmstat -m | grep ether_multi" shows
the in-use counter is incrementing each time, including when I add them
manually with mtest. I highly suspect that the dpni20 driver is getting
confused somewhere, since with the bridged-tap setup it maintains an
internal "10-side" IP and MAC address which is not visible to the OS's
interface table, and only manifests in the ARP table. Presently,
klh10's "enaddr" command-line utility stopped giving errors on adding
the requisite multicast addresses, but ether_multi is *not* incremented,
and the warning enaddr: No EN addr in iftab for "tap0" is given, telling
me that nothing is really happening. This is telling, since enaddr
exercises the same functions in osdnet.c that the emulator itself uses.
As a test I think I may try setting the dedicated interface to a real
ethernet instead of the virtual tap, to see if I can resolve the
multicast issues. At the moment this seems to be the show stopper.
Mark
Mark Abene wrote:
I wanted to be doing a netstat -ani, (-g only shows multicast for
ipv4/6), but the result is the same. None of the DECnet multicast
addresses are being added, most notably (and absolutely necessary) are:
ab:0:0:3:0:0 - type 6003 - for DECnet Phase IV end node Hello packets
from each host, and
ab:0:0:4:0:0 - type 6003 - for DECnet Phase IV router Hello packets from
the router.
I've tried adding these with both enaddr from KLH10 and FreeBSD's
built-in "mtest", but both return errors. This seems to be a
FreeBSD-specific problem which so far I'm unable to find the reason for.
Mark
Mark Abene wrote:
Mark Abene wrote:
I've actually made a new discovery... looking at "netstat -g", I'm
seeing that none of the multicast addresses exist that DECnet uses and
requires! This would explain why I don't see any DECnet traffic at all.
I compiled KLH10's enaddr utility in an attempt to add the multicast
addresses manually, and I get failures for all attempts...
"SIOCADDMULTI failed - Can't assign requested address". My server's
kernel wasn't built with multicast routing enabled, which is not a
default. I'm wondering if this is the cause of the error. I'm going to
do some further testing.
Regards
Mark
Well I was mistaken about the multicast routing, that's only for doing
DVMRP with mrouted (MBONE, etc). Local LAN multicast should work "out
of the box" on FreeBSD. Still trying to track down why this is failing,
since it's my primary candidate for DECnet not working...