| |
PA2AGA > TCPDIG 19.02.97 16:38l 158 Lines 5589 Bytes #-10716 (0) @ EU
BID : TCP_97_19
Read: DG7DAH GUEST
Subj: TCP-Group Digest 97/19
Path: DB0AAB<DB0KCP<DB0ULM<DB0LX<DB0RBS<DB0SEL<DB0ZDF<DB0HOM<LX0PAC<ON7RC<
ON4RAT<DB0ACC<DB0OBK<DB0SM<PI8DAZ<PI8GCB<PI8HGL<PI8VNW
Sent: 970219/0814Z @:PI8VNW.#ZH2.NLD.EU #:43925 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA29320 ; Wed, 19 Feb 97 08:02:55 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.62/7.1) with SMTP
id AA00001637 ; Tue, 18 Feb 97 09:32:14 MET
Received: from pa2aga-1 by pa2aga with SMTP
id AA00001632 ; Tue, 18 Feb 97 09:17:06 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.62/7.6) with SMTP
id AA00009175 ; Tue, 18 Feb 97 09:16:59 MET
Date: Tue, 18 Feb 97 09:14:22 MET
Message-Id: <tcp_97_19>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 97/19
X-BBS-Msg-Type: B
TCP-Group Digest Mon, 17 Feb 97 Volume 97 : Issue 19
Today's Topics:
One ip address for each interface. (3 msgs)
tcpip
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: Sun, 16 Feb 1997 21:00:18 +0100
From: Simon J Mudd <sjmudd@phoenix.ea4els.ampr.org>
Subject: One ip address for each interface.
In article <199702152002.UAA26631@nothing.ucsd.edu>, Brian Kantor wrote:
>
> What we do here in the San Diego central IP switch is assume a default
> route of the interface that lives on the 144.76/145.36 packet repeater,
> and use broadcast unsolicited ARP responses to override that default
> for specific stations who are operating on other frequencies.
Brian,
I think I misread this first time. The "packet repeater" works like a
normal voice repeater? I don't know how many stations are in your
area, though I imagine that there are more than here. Does the packet
repeater talk to any other "repeaters" or nodes, or is it simply the
centre of activity, and due to its location a simple "hub"?
If you have any routing to other stations (hubs which are linked to
stations further away or on other bands) how do you distribute the
routing information, or do you simply not do this?
Sorry if I'm asking a stupid question, but I'm curious as to how the
larger "ham nets" are connected together.
--
regards,
Simon J Mudd, EA4ELS / G0FNB +34-1-559 2854 Madrid, Spain
sjmudd@redestb.es
ea4els@phoenix.ea4els.ampr.org [short messages - radio hams only]
------------------------------
Date: Sun, 16 Feb 1997 22:49:30 +0100 (MET)
From: Julian Munoz <julian@nos.ea4rct.ampr.org>
Subject: One ip address for each interface.
Hello Brian, thanks for the fast answer.
> What we do here in the San Diego central IP switch is assume a default
> route of the interface that lives on the 144.76/145.36 packet repeater,
> and use broadcast unsolicited ARP responses to override that default
> for specific stations who are operating on other frequencies.
I don't understand. A packet repeater, you mean an "analog duplex"
repeater (why then the 600 hz shift???). Is there a default router ? In
the qrg of the repeater ?? I don't understand, sorry !! :-)
Saludos de Julian Amateur Radio Operator License: EA n 53-37081-VI
@ ea4abb
------------------------------
Date: Mon, 17 Feb 1997 12:48:46 +0000 (GMT)
From: Alan Cox <alan@cymru.net>
Subject: One ip address for each interface.
> can't hear after a certain period of time. This sounds like the function
> used by ethernet bridges. Does software for this exist, or is this
> similar to the functionality existed by other software for other "network
> types"?
Linux already supports proxy ARP. It won't help you for some of this
kind of stuff as many hosts don't believe random ARP responses that are
just broadcast at them.
> ideally here the type of activity of the load balancing for multiple
> ppp-connections available in the linux kernel might be useful if that
> funcionality were availalbe, even allowing "load balancing" between
different
> links of different speeds. Does the linux stuff cope with line speeds which
> are different?
It will do load balancing over multiple AX.25 links in datagram mode. I
doubt it helps much.
> My networking knowledge is very limited. Are the any reasons to prefer one
> level over the other, apart from requiring multiple ip addresses if routing
> at the ip level between different hosts in different bands?
Trying to route AX.25 is a nightmare as its not designed to be routeable.
Tools like rip98d and rspfd make clean dyanmic routing of IP networks over
AX.25 quite feasible.
Alan
------------------------------
Date: Mon, 17 Feb 97 01:11:09 EST
From: "Pablo F [BNXNET.NET [198.102.66.43] ]" <n2meg@nyc-gw.kb2vlx.ampr.org>
Subject: tcpip
add tcp-group
-----
73 de Pablo n2meg...
AX25 BBS: n2meg@n2meg.#bronx.ny.usa.na
Amprnet: n2meg@vanbbs.n2meg.ampr.org
n2meg@nyc-gw.kb2vlx.ampr.org
Internet: n2meg@bnxnet.net
http://maestro.com/~n2meg
------------------------------
End of TCP-Group Digest V97 #19
******************************
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
| |
