| |
PA2AGA > TCPDIG 19.02.97 16:28l 98 Lines 3680 Bytes #-10716 (0) @ EU
BID : TCP_97_20
Read: DG7DAH GUEST
Subj: TCP-Group Digest 97/20
Path: DB0AAB<DB0KCP<DB0ZKA<DB0LX<DB0RBS<DB0SEL<DB0ZDF<DB0SRS<DB0MW<DB0ERF<
DB0SHG<DB0SM<PI8DAZ<PI8GCB<PI8HGL<PI8VNW
Sent: 970219/0831Z @:PI8VNW.#ZH2.NLD.EU #:43931 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA29322 ; Wed, 19 Feb 97 08:18:58 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.62/7.1) with SMTP
id AA00001644 ; Tue, 18 Feb 97 23:51:26 MET
Received: from pa2aga-1 by pa2aga with SMTP
id AA00001641 ; Tue, 18 Feb 97 23:50:22 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.62/7.6) with SMTP
id AA00009177 ; Tue, 18 Feb 97 23:50:19 MET
Date: Tue, 18 Feb 97 23:42:36 MET
Message-Id: <tcp_97_20>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 97/20
X-BBS-Msg-Type: B
TCP-Group Digest Tue, 18 Feb 97 Volume 97 : Issue 20
Today's Topics:
One ip address for each interface.
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from ftp.UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Mon, 17 Feb 1997 23:55:57 +0100 (MET)
From: Julian Munoz <julian@nos.ea4rct.ampr.org>
Subject: One ip address for each interface.
> From: brian@nothing.UCSD.EDU (Brian Kantor)
>
> Two ports may have the same address if
[..]
>
> Note that both of these are rare use of interfaces in this way. In almost
> all other applications, each interface will have its own address.
>
> Unfortunately, in the ham world, a lot of people want to do IP routing
> between different frequencies and assign separate addresses to each,
> since on first thought that seems the best way to go. The immediate
> implication of this is that every frequency in an area has to be a
> separate subnet, and you have to change addresses every time you change
> frequencies, and there has to be routers between all the freqs.
The need of changing of frequency mean that in fact we need mobility
"mobility of frequency". How works ip in mobile networks ?? A mobile host
must change its ip address dynamicaly ?? I thinked that a router with
something like rspfd could have 2 ports with the same ip and make dynamic
routes to other routers with rspfd, including in the case of the ip address
of the other router is not in our same network.
> Better to treat the whole area as one subnet and use AX.25 routing to
> select which interface to send a packet - i.e, the interface is chosen
> from information in the 'wiretap' and/or 'arp' tables. I don't think
> any of the ham software packages do this yet.
That's a little frustating to hear that !!
How is it solved in lan-radio networks ??
Isn't it a good solution for us ?
I think that protocols must adapt to us, and not viceversa (we have needs,
computers are here to solve them ! :-)
I think a lot of people is using the same ip address on 2 or more ports,
and that's working. So, if that's working, what is bad ? Us or ip (or
the rfcs) ??
Saludos de Julian Amateur Radio Operator License: EA n 53-37081-VI
@ ea4abb
------------------------------
End of TCP-Group Digest V97 #20
******************************
You can send your message for this bulletin
to: tcp-group@pa2aga on .AMPR.ORG-net
or: tcpaga@pi8vnw.#zh2.nld.eu on BBS-net
------
NOT TO: pa2aga@pa2aga or pa2aga@pi8vnw.#zh2.nld.eu PLEASE!!
It will get posted automatically within a few days
Read previous mail | Read next mail
| |
