Date: Sat, 27 Nov 93 04:30:09 PST
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #307
To: tcp-group-digest


TCP-Group Digest            Sat, 27 Nov 93       Volume 93 : Issue  307

Today's Topics:
              An attitude problem in Germany about 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 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: Fri, 26 Nov 93 16:59:33 CET
From: BARRY TITMARSH <BTITMARS%ESOC.BITNET@vm.gmd.de>
Subject: An attitude problem in Germany about TCPIP
To: TCP-GROUP <TCP-GROUP@ucsd.edu>,

Organization: Barry's Linux Box Darmstadt.
Summary: use of tcpip


Can users of tcpip please explain why in the Rhine Mainz one sysop decides
that he will go against the use of tcpip in that location, well he is not
the only one there are others in the Rhine Mainz.  Below is a list of DB0xyz
bbs that fully support the use of TCPIP you will note that NONE of these
BBS's are in the Rhine Mainz area, So if a user of tcpip wants his smtp mail
or nntp news, and lives in the Rhine Mainz. has to go to extream measures to
fight off the BULL-SHIT that is constantly excreating from sysops of the
Rhine Mainz digis. The only exception to the Rule is the SYSOP of DB0DA, who
operates and does not care as to the mode of traffic obver the digi. same as
can be said with the digi sysops in general in EU.



AX25: DB0ZDF->DF4WJ I NR=7 NS=3 pid=Text
<11 DB0ZDF>DF4WJ-14 I41^>:
 411: S5      P1 : DB0ZDF>DK7WJ
 489: S5  U4  P1 : DB0ZDF>DF4WJ

 460: S5  U7  P1 : DB0ZDF>DB8PP
 493: S7  U7  P1 : DK0MTV>DL8FCK v DB0ZDF*
 469: S5      P1 : DB0ZDF>DG7FF
 273: S2      P1 : DB0RT-10>DC0HK v DB0ZDF* ---------------00
 272: S5      P1 : DD8NE>DC0HK v DB0BBG* ------------------00
uhf recv (Thu Nov 25 22:05:07 1993):
AX25: DB0ZDF->DB8PP I NR=0 NS=5 pid=Text
G2FBH 10.11.93 19:00   4046  day=313 2line Set #290 glonass.290
  55 DG2FBH 10.11.93 19:01   4681  day=313 2line Set #290 gorizont.290
  56 DG2FBH 10.11.93 19:02   5586  day=313 2line Set #290 gps.290

<11 DF4WJ-14>DB0ZDF I34^>: k 273 --------------------------00

<11 DB0ZDF>DF4WJ-14 I53^>:
=>
<11 DF4WJ-14>DB0ZDF I45^>: k 272 --------------------------00

<11 DB0ZDF>DB0RPL SABM+>
<11 DB0ZDF>DF4WJ-14 I64^>:
=>
The above trace is repeated nonstop now for the past 3 days.!
and the sysop is still attempting to stop TCPIP in this area.
but the PC allways wins HI.

NOTE: the ---00 these mark the points where sysop of DB0ZDF kills the VC
for the tcpip ccts on the network.


here is a list of db0... bbs that support tcpip

44.130.0.9 db0dj.test
44.130.0.10 db0hb.test
44.130.0.100 db0sef
44.130.0.200 db0hhs
44.130.1.100 db0hhn
44.130.4.1 db0oq
44.130.5.1 db0hes
44.130.8.100 db0acm
44.130.9.2 db0fc
44.130.9.15 db0abz
44.130.9.16 db0dni
44.130.11.26 db0cel-2
44.130.11.100 db0ner
44.130.13.100 db0uhi
44.130.13.200 db0war
44.130.14.20 db0kg
44.130.15.2 db0hsk
44.130.15.4 db0hsk-2
44.130.16.10 db0bq
44.130.17.111 db0hag
44.130.18.30 db0dv
44.130.18.100 db0qs
44.130.18.101 db0qs-svr
44.130.18.102 db0qs-mail
44.130.20.5 db0pra-5
44.130.20.50 db0pra
44.130.20.51 db0pra-9
44.130.20.78 db0bm
44.130.21.64 db0ghh
44.130.21.128 db0net-8
44.130.22.22 db0msc
44.130.22.44 db0msc-svr
44.130.23.1 db0mkn
44.130.24.30 db0tcp
44.130.27.80 db0eam
44.130.27.90 db0vfk
44.130.27.100 db0kh
44.130.29.1 db0rot-c
44.130.29.5 db0ie-u
44.130.29.18 db0rot
44.130.34.1 db0nws
44.130.41.8 db0cpu
44.130.41.64 db0aac
44.130.41.65 db0aac-svr
44.130.41.86 db0dig-11
44.130.41.89 db0dig-12
44.130.42.3 db0lj
44.130.48.3 db0sao
44.130.48.10 db0id
44.130.48.36 db0pig
44.130.48.60 db0aaa-1
44.130.48.61 db0aaa
44.130.48.64 db0aau
44.130.48.65 db0sao-u
44.130.48.66 db0id-u
44.130.48.123 db0adf
44.130.48.143 db0adf-u
44.130.48.244 db0wan
44.130.56.4 db0mwe
44.130.56.5 db0lan
44.130.56.25 db0pv
44.130.56.53 db0ffb
44.130.56.56 db0uni
44.130.56.100 db0mfg
44.130.56.111 db0mws
44.130.58.1 db0zka
44.130.58.2 db0zka-test
44.130.59.21 db0ev
44.130.60.25 db0ova
44.130.60.100 db0rt
44.130.60.101 db0rt-test ftp.db0rt
44.130.63.100 db0aja

So haveing read the list, it can be clearly seen that TCPIP is on the
increase generally in germany.!

So why is DF4WJ on a personal crusade to stop TCPIP on DB0ZDF.?

In the past 4 years i have been BANNED fro local BBS's Banned from local
digis, sent abusive letters! Threatend by powerless non tcpip users to have
my License removed Hi Hi.. [thats a good one] and even called up on the
telephone in the night [my fax/modem loves it]

read the posting containg a trace on db0zdf>df4wj killing Virtual Circuits
thats only a small trace i have it traced on 70cm 23cm and via other digis
as we all know that a node-op and can login from any other node as a sysop

My thoughts on all this is Im Glad im not permanently liveing in Germany.!
and haveing lived in many places and countries i find that in particular the
Rhine Mainz area of Germany the most HOSTILE place, and i feel sorry for the
HAM Operators that have to by their own choice have to live there.

Flame on.


Barry..  there will be more,



--
Barry Titmarsh  GM8SAU sysop GB7SAU Scotland.
btitmars@esoc.bitnet dc0hk@db0lj g8sau@db0lj
--

------------------------------

End of TCP-Group Digest V93 #307
******************************
******************************