On Mon, 7 Feb 2000, Stephan Loges wrote:
> Trying to get NetROM via TCP/IP up with kernel 2.2.13 (SuSE 6.3).
> Until now without success.
> After a ping from a remote machine, which frames are forwarded
> by my NetROM neighbour, ifconfig nr0 looks like this:
> slclx:~ # ifconfig nr0
> nr0 Link encap:AMPR NET/ROM HWaddr DB0SUE-9
> inet addr:44.130.127.141 Mask:255.0.0.0
> UP RUNNING MTU:512 Metric:1
> RX packets:3 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:3 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> It received the 3 packets and answered them as they should, but they
> are not visible at the ax0 port.
> A ping from this machine to the remote end counts one error more.
>
> This is my routing table:
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 44.130.127.141 * 255.255.255.255 UH 0 0 0 nr0
This shouldn't be necessary.
> 44.130.127.129 * 255.255.255.255 UH 0 0 0 nr0
> loopback * 255.0.0.0 U 0 0 0 lo
>
> and this my arp entries:
> Address HWtype HWaddress Flags Mask Iface
> 44.130.127.129 netrom 88:84:60:A6:AA:8A:00CM nr0
I suppose 44.130.127.129 is the remote host you are talking about? The
one that is pinging you?
88:84:60:A6:AA:8A:00 translates to DB0SUE-0 if I managed to do it right.
Is that the correct NET/ROM address of 44.130.127.129 ? Also do you have a
NET/ROM route to DB0SUE-0 ? Ie. if you run node, what does
"nodes DB0SUE-0" command tell you? Or "grep DB0SUE-0 /proc/net/nr_nodes"
from shell?
> What im doing wrong, or does the current state of NetROM
> interface with new kernel not support this ?
I just verified, it works for me.
--
Tomi Manninen Internet: [EMAIL PROTECTED]
OH2BNS AX.25: [EMAIL PROTECTED]
KP20ME04 Amprnet: [EMAIL PROTECTED]
