linux-decnet-user Mailing List for DECnet for Linux
Brought to you by:
chrissie_c,
ph3-der-loewe
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(8) |
Jun
(39) |
Jul
(30) |
Aug
(23) |
Sep
(9) |
Oct
(9) |
Nov
(30) |
Dec
(24) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(12) |
Feb
(4) |
Mar
(21) |
Apr
|
May
(3) |
Jun
(3) |
Jul
(13) |
Aug
(13) |
Sep
(18) |
Oct
(10) |
Nov
(25) |
Dec
(2) |
| 2002 |
Jan
(7) |
Feb
(14) |
Mar
(15) |
Apr
(29) |
May
(10) |
Jun
(23) |
Jul
(76) |
Aug
(52) |
Sep
(15) |
Oct
(47) |
Nov
(12) |
Dec
(1) |
| 2003 |
Jan
(5) |
Feb
(12) |
Mar
(21) |
Apr
(26) |
May
(66) |
Jun
(16) |
Jul
(13) |
Aug
(7) |
Sep
(21) |
Oct
(11) |
Nov
(4) |
Dec
(11) |
| 2004 |
Jan
(18) |
Feb
(1) |
Mar
(1) |
Apr
(20) |
May
(10) |
Jun
(4) |
Jul
(9) |
Aug
(9) |
Sep
|
Oct
(5) |
Nov
(13) |
Dec
(8) |
| 2005 |
Jan
(23) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(11) |
Jun
(3) |
Jul
(5) |
Aug
(15) |
Sep
(3) |
Oct
(13) |
Nov
(2) |
Dec
(7) |
| 2006 |
Jan
(5) |
Feb
(8) |
Mar
(6) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(5) |
Sep
(2) |
Oct
(6) |
Nov
|
Dec
(3) |
| 2007 |
Jan
|
Feb
(6) |
Mar
(3) |
Apr
(1) |
May
|
Jun
(5) |
Jul
(7) |
Aug
|
Sep
(7) |
Oct
(7) |
Nov
(4) |
Dec
(2) |
| 2008 |
Jan
(10) |
Feb
(5) |
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
(14) |
Aug
(3) |
Sep
(6) |
Oct
(7) |
Nov
|
Dec
|
| 2009 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
(2) |
May
(2) |
Jun
(1) |
Jul
(3) |
Aug
(15) |
Sep
(9) |
Oct
(1) |
Nov
(2) |
Dec
|
| 2010 |
Jan
|
Feb
(5) |
Mar
(2) |
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
(2) |
Sep
(6) |
Oct
(1) |
Nov
(15) |
Dec
|
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(11) |
Apr
|
May
|
Jun
(17) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(8) |
| 2012 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(12) |
Feb
(15) |
Mar
(11) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(5) |
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2016 |
Jan
|
Feb
(14) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2017 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
|
2
|
3
|
4
(1) |
5
|
6
(1) |
7
(1) |
|
8
|
9
(1) |
10
(2) |
11
|
12
|
13
|
14
|
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
|
29
|
30
|
31
|
|
|
|
|
|
From: Larry B. <ba...@us...> - 2006-10-10 20:13:50
|
There is a previous thread from earlier this year dealing with DECnet =20=
routing and SuSE 10.0, subject "Decnet-Linux under SUSE 10.0", that =20
may be relevant. Here's the instructions I used on my SuSE 9.3 =20
system to properly configure the DECnet interface for multicast and =20
the removal of the routing hack in /etc/init.d/decnet (SuSE names the =20=
ifcfg-eth-XXX files by MAC address, which must be changed for DECnet; =20=
other Linux's just name the files ifcfg-eth0, etc., so the rename =20
step is unnecessary):
Fixup the installation so dnetd can find fal:
# ln -s /usr/sbin/fal /usr/local/sbin/fal
Edit the DECnet startup/shutdown script, /etc/init.d/decnet:
#daemons=3D"dnetd phoned"
daemons=3D"dnetd"
Also, remove the DECnet routing hack, which is fixed by enabling the =20
allmulticast interface option, below:
# FIXME dirty hack for SUSE 9.1 kernel.
# Add all known nodes to neighbor list
# comments to st...@op...
for NODE in $(grep ^node /etc/decnet.conf| awk '{print $2}')
do
/sbin/ip -f dnet neigh add $NODE dev $CCT
done
# end of dirty hack
Configure the Ethernet MAC address and enable the allmulticast =20
interface option in /etc/sysconfig/network/ifcfg-eth0:
# cd /etc/sysconfig/network
# mv ifcfg-eth-id-00:07:e9:16:b5:94 ifcfg-eth0
# vi ifcfg-eth0
# DECnet host address 54.145
LLADDR=3DAA:00:04:00:91:D8
# DECnet needs =93allmulticast on=94
LINK_OPTIONS=3D=94allmulticast on=94
Larry Baker
US Geological Survey
650-329-5608
ba...@us...
On Oct 10, 2006, at 12:12 PM, Steven Whitehouse wrote:
> Hi,
>
> On Fri, Oct 06, 2006 at 01:26:04PM -0400, Alan Kemmerer wrote:
>> Hi,
>> My last message was premature. The problem is not the packet =
size.
>> It is in the routing code.
>> I need to get the routing code working correctly for our network.
>> Since it is segmented by L1 routes
>> What I need to do is have the endnode populate its neighbors from =20
>> the hello
>> messages.
>> If the destination is not on the local segment, send the packet to =20=
>> the L1
>> Router
>> Or if the packets source is the L1 Router send the reply to the L1 =20=
>> router
>> and not the destination.
>>
>> Below is the tcpdump of a ping from 1.43(VMS) to 1.99(linux)
>> from linux.
>>
>> 1.99 is on a segment by itself with the router 1.405
>>
>> 1.43 is on a different segment with router 1.405
>>
> Would it be possible for you to do the tcpdump again, but with the -e
> flag so that we get the link layer headers too? Also if you could send
> the content of /proc/net/decnet_neigh it would be very helpful. If the
> router doesn't appear there, then that would explain the problem.
>
> Since the endnode hello you included doesn't include the router it
> would appear that this is the reason for the routing problem.
>
> Since the router hello is multicasted, the things to check are
> that Linux is listening on the correct address and that your network
> card is set up to receive multicast. The command
>
> /sbin/ip link ls
>
> will tell you that and
>
> /sbin/ip maddr ls
>
> well tell you if its listening to the correct multicast address. You
> could also try /sbin/ip link set eth0 promisc on just to see if it
> makes any difference. It will take a few seconds for Linux to pick
> up the router in any case,
>
> Steve.
>
> ----------------------------------------------------------------------=20=
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =20
> share your
> opinions on IT & business topics through brief surveys -- and earn =20
> cash
> http://www.techsay.com/default.php?=20
> page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV
> _______________________________________________
> Linux-decnet-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
|
|
From: Steven W. <st...@ch...> - 2006-10-10 19:18:45
|
Hi, On Fri, Oct 06, 2006 at 01:26:04PM -0400, Alan Kemmerer wrote: > Hi, > My last message was premature. The problem is not the packet size. > It is in the routing code. > I need to get the routing code working correctly for our network. > Since it is segmented by L1 routes > What I need to do is have the endnode populate its neighbors from the hello > messages. > If the destination is not on the local segment, send the packet to the L1 > Router > Or if the packets source is the L1 Router send the reply to the L1 router > and not the destination. > > Below is the tcpdump of a ping from 1.43(VMS) to 1.99(linux) > from linux. > > 1.99 is on a segment by itself with the router 1.405 > > 1.43 is on a different segment with router 1.405 > Would it be possible for you to do the tcpdump again, but with the -e flag so that we get the link layer headers too? Also if you could send the content of /proc/net/decnet_neigh it would be very helpful. If the router doesn't appear there, then that would explain the problem. Since the endnode hello you included doesn't include the router it would appear that this is the reason for the routing problem. Since the router hello is multicasted, the things to check are that Linux is listening on the correct address and that your network card is set up to receive multicast. The command /sbin/ip link ls will tell you that and /sbin/ip maddr ls well tell you if its listening to the correct multicast address. You could also try /sbin/ip link set eth0 promisc on just to see if it makes any difference. It will take a few seconds for Linux to pick up the router in any case, Steve. |
|
From: Patrick C. <pa...@ty...> - 2006-10-09 09:15:43
|
Alan Kemmerer wrote: > I have tried dnroute is does not function correctly. > Specifically on inbound traffic i.e. a request from non-local segment. > Linux wants to put it out to the local net. > Another thing I have see is that a cache entry is made prior to a valid link > to an address. > > Adding routes manually is a bit difficult since the DECnet is complicated. I suspect it's a lot easier than going into the kernel code ;-) eg: # ip -D route add 3.35 dev eth0 # ip -D route add to 1.15 via 3.35 dev eth0 protocol static -- patrick |
|
From: Patrick C. <pa...@ty...> - 2006-10-07 01:24:11
|
Alan Kemmerer wrote: > Hi, > My last message was premature. The problem is not the packet size. > It is in the routing code. > I need to get the routing code working correctly for our network. > Since it is segmented by L1 routes > What I need to do is have the endnode populate its neighbors from the hello > messages. > If the destination is not on the local segment, send the packet to the L1 > Router > Or if the packets source is the L1 Router send the reply to the L1 router > and not the destination. > > Below is the tcpdump of a ping from 1.43(VMS) to 1.99(linux) > from linux. > > 1.99 is on a segment by itself with the router 1.405 > > 1.43 is on a different segment with router 1.405 > Have you tried the dnroute program? It's slightly simplistic but it does pretty much what you outlined there. Alternatively you could manually add the routes using the "ip" program. -- patrick |
|
From: Alan K. <ala...@mi...> - 2006-10-06 17:29:19
|
Hi,
My last message was premature. The problem is not the packet size.
It is in the routing code.
I need to get the routing code working correctly for our network.
Since it is segmented by L1 routes
What I need to do is have the endnode populate its neighbors from the hello
messages.
If the destination is not on the local segment, send the packet to the L1
Router
Or if the packets source is the L1 Router send the reply to the L1 router
and not the destination.
Below is the tcpdump of a ping from 1.43(VMS) to 1.99(linux)
from linux.
1.99 is on a segment by itself with the router 1.405
1.43 is on a different segment with router 1.405
13:23:27.426007 router-hello l1rout vers 2 eco 0 ueco 0 src 1.405 blksize
1498 pri 64 hello 15
0x0000: ab00 0004 0000 aa00 0400 9505 6003 1b00 ............`...
0x0010: 0b02 0000 aa00 0400 9505 02da 0540 000f .............@..
0x0020: 000f 0800 0000 0000 0000 0000 0000 0000 ................
0x0030: 0000 0000 0000 0000 0000 0000 ............
13:23:31.325083 1.43 > 1.99 49 conn-initiate 24936>0 ver 4.1 segsize 1459
0x0000: aa00 0400 6304 aa00 0400 9505 6003 3100 ....c.......`.1.
0x0010: 810e 0000 aa00 0400 6304 0000 aa00 0400 ........c.......
0x0020: 2b04 0001 0000 1800 0068 6101 03b3 0500 +........ha.....
0x0030: 1902 00b4 0a00 0004 5354 4d38 2700 0000 ........STM8'...
0x0040: 00 .
13:23:31.325208 1.99 > 1.43 30 disconn-initiate 0>24936 no link terminate
0x0000: aa00 0400 2b04 aa00 0400 6304 6003 1e00 ....+.....c.`...
0x0010: 8126 0000 aa00 0400 2b04 0000 aa00 0400 .&......+.......
0x0020: 6304 0000 0000 3868 6100 0029 0000 c.....8ha..)..
13:23:32.819131 endnode-hello endnode vers 2 eco 0 ueco 0 src 1.99 blksize
1498
rtr 0.0 hello 0 data 0
0x0000: ab00 0003 0000 aa00 0400 6304 6003 2200 ..........c.`.".
0x0010: 0d02 0000 aa00 0400 6304 03da 0500 0000 ........c.......
0x0020: 0000 0000 0000 aa00 0400 9505 0f00 0002 ................
0x0030: aaaa ..
Alan J. Kemmerer
Technical Engineer
Mittal Steel USA - Sparrows Point
|
|
From: Alan K. <ala...@mi...> - 2006-10-04 20:10:55
|
Hi,
I have discovered a flaw in the decnet code I'm not quite sure where it is
but here are the
tcpdumps from our network. The network is segmented with L1 routes between
segments.
segment 1 nodes 1.43,1.42 OpenVMS
L1 router 1.405
segment 2 nodes 1.30 Linux 2.6.18
1.25,1.31,1.33 OpenVMS
L1 Router 1.401
1.401 is connected to 1.405
the problem is with the Linux packet length being less than the Ethernet
minimum of 60 octets
which prevents it from crossing the routers I think.
This concussion is from being able to 'dnping (ncp loop node)' local nodes
but not remotes from Linux
Where as from VMS I can 'dnping (ncp loop node )' any where
08:49:10.455860 1.43 > 1.42 49 conn-initiate 24792>0 ver 4.1 segsize 1459
3100 812e 0000 aa00 0400 2a04 0000 aa00
0400 2b04 0000 0000 1800 00d8 6001 03b3
0500 1902 00a8 2100 0004 5354 4d38 2700
0000 00
08:49:10.485026 1.43 > 1.42 33 link-service 24792>8614 ack 0 seg 1 dat seg
count 0
2100 8126 0000 aa00 0400 2a04 0000 aa00
0400 2b04 0000 0000 10a6 21d8 6000 8001
0000 0000 0000 0000 0000 0000 0000
08:49:10.485026 1.43 > 1.42 71 data 24792>8614 ack 0 seg 1
4700 8126 0000 aa00 0400 2a04 0000 aa00
0400 2b04 0000 0000 60a6 21d8 6000 8001
1000 5555 5555 5555 5555 5555 5555 5555
5555 5555 5555 5555 5555 5555 5555 5555
5555 5555 5555 5555 55
08:49:10.485026 1.43 > 1.42 29 ils-ack 24792>8614 ack 1
1d00 8126 0000 aa00 0400 2a04 0000 aa00
0400 2b04 0000 0000 14a6 21d8 6001 8000
0000 0000 0000 0000 0000 0000 0000
08:49:10.493359 1.43 > 1.42 30 disconn-initiate 24792>8614 object rejected
connect
1e00 8126 0000 aa00 0400 2a04 0000 aa00
0400 2b04 0000 0000 38a6 21d8 6000 0000
0000 0000 0000 0000 0000 0000 0000
15:48:23.620618 1.30 > 1.31 35 link-service 8197>24665 ack 1 ackdat 8 seg
2017 dat seg count 0
0x0000: 2300 8126 0000 aa00 0400 1f04 0000 aa00 #..&............
0x0010: 0400 1e04 0000 0000 1059 6005 2001 8008 .........Y`.....
0x0020: a0e1 0700 00 .....
15:48:23.623771 1.31 > 1.30 29 ils-ack 24665>8197 ack 2017
0x0000: 1d00 8126 0000 aa00 0400 1e04 0000 aa00 ...&............
0x0010: 0400 1f04 0000 0000 1405 2059 60e1 8700 ...........Y`...
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
15:48:26.193445 endnode-hello endnode vers 2 eco 0 ueco 0 src 1.33 blksize
1498 rtr 0.0 hello 0 data 0
0x0000: 2200 0d02 0000 aa00 0400 2104 03da 0500 ".........!.....
0x0010: 0000 0000 0000 0000 aa00 0400 9105 0f00 ................
0x0020: 0002 aaaa 0000 0000 0000 0000 0000 ..............
15:48:26.720649 endnode-hello endnode vers 2 eco 0 ueco 0 src 1.30 blksize
1498 rtr 0.0 hello 0 data 0
0x0000: 2200 0d02 0000 aa00 0400 1e04 03da 0500 "...............
0x0010: 0000 0000 0000 0000 aa00 0400 9105 0a00 ................
0x0020: 0002 aaaa ....
15:48:27.332669 1.30 > 1.26 35 link-service 8199>8430 ack 1 ackdat 0 seg
2019 dat seg count 0
0x0000: 2300 8126 0000 aa00 0400 1a04 0000 aa00 #..&............
0x0010: 0400 1e04 0000 0000 10ee 2007 2001 8000 ................
0x0020: a0e3 0700 00 .....
15:48:27.333512 1.26 > 1.30 29 ils-ack 8430>8199 ack 2019
0x0000: 1d00 8126 0000 aa00 0400 1e04 0000 aa00 ...&............
0x0010: 0400 1a04 0000 0000 1407 20ee 20e3 8700 ................
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
15:48:27.575012 endnode-hello endnode vers 2 eco 0 ueco 0 src 1.27 blksize
1498 rtr 0.0 hello 0 data 0
0x0000: 2100 0d02 0000 aa00 0400 1b04 03da 0500 !...............
0x0010: 0000 0000 0000 0000 aa00 0400 9105 1e00 ................
0x0020: 0001 aa20 2000 0081 9200 00ff 534d 4225 ............SMB%
0x0030: 0000 ..
15:48:29.982596 endnode-hello endnode vers 2 eco 0 ueco 0 src 1.25 blksize
1498 rtr 0.0 hello 0 data 0
0x0000: 2200 0d02 0000 aa00 0400 1904 03da 0500 "...............
0x0010: 0000 0000 0000 0000 aa00 0400 9105 0f00 ................
0x0020: 0002 aaaa 0000 0000 0000 0000 0000 ..............
15:48:30.570235 endnode-hello endnode vers 2 eco 0 ueco 0 src 1.26 blksize
1498 rtr 0.0 hello 0 data 0
0x0000: 2200 0d02 0000 aa00 0400 1a04 03da 0500 "...............
0x0010: 0000 0000 0000 0000 aa00 0400 9105 0f00 ................
0x0020: 0002 aaaa 0000 0000 0000 0000 0000 ..............
15:48:33.620813 1.30 > 1.31 35 link-service 8197>24665 ack 1 ackdat 8 seg
2018 dat seg count 0
0x0000: 2300 8126 0000 aa00 0400 1f04 0000 aa00 #..&............
0x0010: 0400 1e04 0000 0000 1059 6005 2001 8008 .........Y`.....
0x0020: a0e2 0700 00 .....
15:48:33.625205 1.31 > 1.30 29 ils-ack 24665>8197 ack 2018
0x0000: 1d00 8126 0000 aa00 0400 1e04 0000 aa00 ...&............
0x0010: 0400 1f04 0000 0000 1405 2059 60e2 8700 ...........Y`...
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
15:48:34.838871 endnode-hello endnode vers 2 eco 0 ueco 0 src 1.31 blksize
1498 rtr 0.0 hello 0 data 0
0x0000: 2200 0d02 0000 aa00 0400 1f04 03da 0500 "...............
0x0010: 0000 0000 0000 0000 aa00 0400 9105 0f00 ................
0x0020: 0002 aaaa 0000 0000 0000 0000 0000 ..............
|