Here's another thing to note, the fixed route put in that you use ip over
netrom
will drop out from your nodes list as the obsolesance count decreases. So
when the route drops off the nodes list so does your route.
Unless the station your routing to gets a node broadcast back to you,on a
regular basis the route will drop.
The only way I found round this is to put the fixed netrom routes, as per
ax25 howto,into an executable file and use Cron to execute it say every
hour, its also worth if your using TNC's in Kiss mode refreshing the
kissparms at the same
time.
I have to do this with one of my users you is 100 miles and 4 hops via
netrom away. And to make matters worse, his ip address is so out of date, if
I tried normal routing who knows where his packets would go.
Quick explanation:-
The UK started to renumber its regions about 7 years ago, from the original
20 ish to 255, sorta starts in the NW of Scotland with reg 1 and ends in SE
England with region 255.
However, the UK is a funny place, and although most has renumbered, there is one
large area South WALES which has'nt, and is hogging addresses that belong to
Scotland !.
OK while I'm at it !
there is a little trick that can be used with ip/netrom routing to reach
users with strange ip addresess, and where ip is not supported in their areas.
allocate an address from your own block which they use as their kernel address,
set the port address, or link address if a nos user to their current weird
address, and with something like
route add -host 44.131.10.59 nr0
route add -net 44.131.90.155 netmask 255.255.255.255 gw 44.131.10.59
dont forget to put a fixed arp enry
so you now have a user in your own subnet a long distance away !
like this one,,which I'm hoping to get this sorted permantly, as this user
actually lives in England (Glos) but because he has a S.Wales post code
(zip), he has a GW callsign.
But he's really a G and in I think region 200. The ip cordinator for that region
refuses to acknowledge this , so the poor guys stuck with an obsolete ip
address.
At 05:07 AM 1/25/00 +0000, you wrote:
>Hans-Peter Zorn wrote:
>
>> Why do I need a route to the interface ip address? Shouldn't that be
>> a network route (which is set up automagically with 2.2)
>
>A nuance I missed the first time around. NetRom has no facility for
>automatically mapping IP address to NetRom node (nothign like ARP for
>example) so a network route is useless, you'll have to manually map each
>IP address anyway.
>
>Terry
>
>
Richard Bown G8JVM sysop GB7IPT
Work: 0117 906 6200 etx 302
Home:weekends and Eves. 01952 502550
pager 01523 523523 pager number 819977 (please dont use between 2300 - 0700)
Alternative e-mail [EMAIL PROTECTED]
Amprnet [EMAIL PROTECTED] [44.131.90.1]
NTS g8jvm@gb7ipt.#28.gbr.eu
