From: drechsau@Geeks.ORG (Mike Horwath)
Newsgroups: winternet.general,winternet.gripes
Subject: My reasons for posting... (Was - Re: can't we just get along?)
Date: 29 Jul 1996 05:33:42 GMT
Lines: 848
Distribution: world
Message-ID: <4thifm$cqq@blackice.winternet.com>
NNTP-Posting-Host: jacobs.geeks.org
Mike Horwath (drechsau@Geeks.ORG) wrote:
: Later, I will explain why I have been the way I have been for the last
: 2 weeks, and it should clear up a lot of miscommunications people seem
: to have.
And as promised, here is my statement.
Long ago, I was in control of Winternet, by the whims of both Michael
and Kevin. I did not ask to be in control, but I did not turn it down
when it was offered either. I had the time, determination and the
willingness to learn how to make things work. I was scared out of my
wits to be in charge of a company, to make things work and to admit to
my failures.
This was originally my dream to do: to get an ISP online in Minnesota
where previously there wasn't one. I spent 18 months prior to the
first day of business planning for it.
This was all over 2 1/2 years ago.
For 2 years, 6 months and 5 days, that was my job, to operate the day
to day business and act as primary administrator.
I made mistakes, I errored, I swore, I was not always nice, but I got
the job done, and I treated people like people, not necessarily as
customers.
Also, long ago, someone made mention that it was time for Winternet to
decide if it was to be a business or a hobby. At that time, I was
unsure what I wanted and strived to find a middle ground between the
two. To that end, I think I was successful. I had fun, I enjoyed all
kinds of different customers, and I did my best to keep things
operating.
Since July 5, 1996, I have watched my dream go down the toilet because
of people who refused to listen, who lie through their teeth, and are
generally acting in terms of 'greed' and 'profit'.
I have been wrongfully accused of:
hiring high school kids, under-paying and overworking them
hiring high school kids, over-paying and underworking them
misappropiation of funds (like, Friday night movies and
dinner)
$100,000 US West bill (it was about $40,000 on July 5th)
paying employees before paying our required bills
making this company a reflection of myself and not the
business
unwilling to give up accounting records to both Michael and
Kevin
hacking the system I and my staff put together
misconfiguration of equipment on the internal network
I have been rightfully accused of:
holding a large accounts receivable (estimations of about
$60,000-$70,000)
hating business for the sake of business
hiring high-school people
holding internal employee meetings and buying lunch/dinner for
all of them
being a damn fine admin and employer
Yes, I hired some people who were still in high school, like Kevin
Brintnall, Scott Morford and Jonah Klevesahl. Why not ask them if
they were under or over paid, or if they were under or over worked.
Friday night movies were always out of pocket with each of us helping
to pull the load. Customers were welcome to come with us and many
have over the last 1 1/2 years we have been doing this.
There has never been a $100,000 US West bill. The move was an
expensive operation costing us approximately $60K in just phone costs.
I had already talked with US West about the billing *before* we
actually moved to make sure that I did not step out of bounds and made
sure that things would be okay while we recover.
If paying employee salaries before finishing off the US West bill is a
crime, then I am guilty of it. Then again, I did make sure we could
pay the bill over time...
If the company became a reflection of myself, it was not because that
is the way I promoted it. I was the one who sent email to everyone, I
was the one that went in most nights after hours to fix problems, I
was the one that took responsibility for most problems as they
occurred. Maybe that is how it happened, but it wasn't planned.
Michael and Kevin were given access to the accounting records when
they first asked for them, which was June 19th. In fact, Kevin left
his wife Diane here for the 2+ weeks prior to the firing of all of the
then current staff. She had the full customer list, accounting
records, receipts and invoices, both paid and unpaid.
And finally, hacking... This is something I would never bring myself
to do. My ethics stand in the way of this. There has not been a
reason to hack into the system *except* if I wanted to help bring them
back from the brink of ridicule or even bankruptcy. I have not felt
the urge to do so, and I don't expect I will. I have decided it is
not my place to break into the system, even if it would be to help. I
am not in charge anymore, and they obviously refuse to listen to
myself, or any of *our* customers, based on their responses to date.
The misconfiguration of equipment is probably the funniest accusation
of all of them. If we had done so poorly, why did things work prior
to 7/5/96? It wasn't an hour after I left the offices that dryice was
power cycled (I was on when it happened). I mean, come on, power
cycling UNIX servers does not fix any problems whatsoever. Look after
my signature for a log of what occurred that very first weekend. I
will include my commentary to help explain things. Routing worked,
why did it have to be messed with? Jeez...such utter lies told to
customers.
My main reason for trying to stay active within the winternet.* groups
was to help keep people informed of the problems, and to help fight a
fight that they may not be able to fight by themselves. I bring up
topics that they can't bring up. I bring up facts that they may not
know. I know how these systems operate, and I could probably rebuild
most of them from scratch if that was asked of me to do so. Bringing
the system back into some resemblance of reliability could be done,
but I feel the reputation that has now been created by the new staff,
and the other 2 owners, is just too bad to rectify.
I have made offers to the new 'staff' and to the other 2 owners of
Winternet to help them. They have ignored my offer to this day.
You are not alone out there. I feel horrible for what has happened,
and I feel ashamed as to what it has come down to. I wish I could
help, I really do, but until the current management decides to bite
the bullet, admit that they can't operate a sophisticated network like
Winternet and ask me for help, I am like you, my hands are tied and
nothing I can do will make a difference.
I miss working for Winternet and its customers.
I miss my old staff.
I miss my feeling of accomplishment.
I miss the community I strived to build and the people that were
brought into it for whatever reason they decided to join.
I wish everyone luck, even the new staff, and I hope the future will
be bright at some point.
--
Mike Horwath IRC: Drechsau LIFE: Lover drechsau@Geeks.ORG
Home: 612-588-7740 3000 James Ave N, Minneapolis, MN 55411
---- Log of the weekend beginning Friday, 7/5/96 ----
On July 5th, 1996, the whole (then current) staff of Winternet was
fired outright without reason, notice, severence, or offer of
continued health insurance.
It all started...
2:00pm-4:30pm
Kevin asked me for the root passwords for the machines. As I
was walking down the hall to my office, I told him that I
would give him the root passwords when I was leaving. At that
time, he screamed (very loudly) to 'take the system down,
now!', and repeated it to make sure he was heard. Some
unknown people went into the equipment room at that time.
At this time, one of the *new* employees went into the
equipment room and started pulling all of the ethernet cabling
(speculation, from reading the logs, there were many NFS
errors and password errors while this was going on -
assumption that they had pulled the cabling from the hubs and
switches).
(Later, I noticed they had also pulled all of the modem racks
a couple feet away from their resting positions, stretching
cabling until it was taught. Not a good thing to do in my
opinion.)
(not perfect time estimates above, but close :)
Evidence of incompetence and total disregard for customer service and
respect for the ISP business, in a timeline format:
07/05/96 14:15 Kevin Mathison screams to take the systme down. At
this time, no customers where able to use the services
offered by Winternet.
07/05/96 19:10 unable for normal users to do a normal log in, either
to the shell machines or the dialins.
My password had been changed as well but I use SSH
(secure shell) for my interactive logins, a system
that uses RSA encryption end to end, as well as
offering higher security between hosts. I was able
to log in because of this.
ypbind was not bound (authentication client)
ypserv was not operational on dryice (authentication
server)
07/05/96 19:15 I noticed dryice is down (authentication server)
(I had been logged in)
07/05/96 19:26 Chad Trost noticed that he was unable to log into any
server or dialin on the network.
07/05/96 19:45 Chad Trost tested log ins on tundra, parka, subzero,
siberia, and snowflake. He failed on each of them.
07/05/96 19:52 I noticed dryice is up (authentication server)
(I had already logged back in)
07/05/96 19:57 Chad Trost noticed that everything was back online.
Logfile from dryice: (reformatted to fit your terminal width)
Jul 5 13:18:27 dryice vmunix: NFS server icicle not responding
still trying
Jul 5 13:18:27 dryice vmunix: NFS server icicle ok
Jul 5 14:41:21 dryice in.rlogind[7185]: twist
mfrankow@cube.winternet.com to /etc/scripts/deny-rlogin
Jul 5 15:06:27 dryice in.telnetd[8005]: twist
mfrankow@localhost.winternet.com to
/etc/scripts/deny-telnet
Jul 5 15:07:27 dryice yppasswdd[67]: yppasswdd: ravirai:
bad password
Jul 5 17:40:56 dryice in.rlogind[12148]: twist
root@slush.winternet.com to /etc/scripts/deny-rlogin
Jul 5 17:41:04 dryice in.telnetd[12154]: twist
root@slush.winternet.com to /etc/scripts/deny-telnet
Jul 5 18:49:29 dryice login: REPEATED LOGIN FAILURES ON console,
root
Jul 5 18:51:48 dryice last message repeated 2 times
Jul 5 18:54:22 dryice login: REPEATED LOGIN FAILURES ON console,
root
Jul 5 18:58:47 dryice login: REPEATED LOGIN FAILURES ON console,
root
Jul 5 19:02:37 dryice login: REPEATED LOGIN FAILURES ON console,
root
Jul 5 19:03:43 dryice login: REPEATED LOGIN FAILURES ON console,
root
1 Jul 5 19:04:32 dryice login: REPEATED LOGIN FAILURES ON console,
root
2 Jul 5 19:52:21 dryice vmunix: Using SunDBE 1.4
Jul 5 19:52:21 dryice vmunix: VAC ENABLED
Jul 5 19:52:21 dryice vmunix: SunOS Release 4.1.4_DBE1.4
(DRYICE) #1: Wed Jun 12 18:57:46 CDT 1996
Jul 5 19:52:21 dryice vmunix: Copyright (c) 1983-1993, Sun
Microsystems, Inc.
Jul 5 19:52:21 dryice vmunix: cpu = SUNW,SPARCstation-5
As you can see from the log above, between positions 1 and 2, we have
48 minutes without any logs at all, including the omission of a
shutdown log message that is logged when the shutdown, reboot, or halt
commands are issued.
In my opinion, they forgot their root password (Michael Frankowski set
it himself), or they had killed 'ypserv', the process that services
all requests for usernames and passwords, and at that time, they
decided to shut off the UNIX server known as dryice. It is *NEVER*
good to just shut off a UNIX server, ever!
During this time, 373 email messages were lost due to an 'Unknown
User...' error caused by the inability to verify account names from
the authentication server. This is according to the logs from both
icicle and absolut-zero.
I was forcibly logged off of dryice many times. I had asked whoever
was logged in as root as to why my sessions were being killed and why
the machine had been power cycled. Here is the interaction between
myself and whoever was on the console as root:
[8:18pm] 8 [~]:dryice%
Message from root@dryice on console at 20:18 ...
Your assistance is no longer necessary...
EOF
I then explained that the logs showed that it had been power cycled
and was wondering why it was done. His/her response was...
[8:22pm] 15 [~]:dryice%
Message from root@dryice on console at 20:23 ...
There was no crash... We took it down for maint...
EOF
I am appalled at this time at how things are being handled in the
Winternet offices by the *new* employees.
07/06/96 04:21 I was foribly logged out of all systems and I am now
unable to log in at all. I had just gotten home from
going to the movies, and then out to a very late
dinner with his friends and had just gotten home.
07/06/96 04:29 I noticed that absolut-zero had been rebooted (mail
server). Reason is unknown since I was unable to log
in to check the logs.
07/06/96 05:26 MRNet says that routing to and from Winternet was not
operational.
Michael Frankowski never asked me for the router
passwords. At about this time, Michael (or someone
else who knows how to do this) 'broke' into the main
router from the console port and wiped the
configuration NVRAM. They told customers that I was
to blame for the 'router crash' when infact, there
never had been a crash at all.
None of the *new* employees or *new* management know
how to configure a router for EIGRP and BGP routing.
At this time, AlterNet (UUNet) connectivity is gone
and redundancy is no longer an option for the
Winternet network. Basically, one third of our
bandwidth is missing from the network because of this.
07/06/96 09:30 Doug McIntyre states: MRNet calls our home and asks
why no data is traversering the T1s between Winternet
and MRNet. (Doug McIntyre is my roommate)
Approximately 9 other customers have also called our
home for the next 45 minutes asking why they can not
log in or do anything.
Reports from other customers of not being able to log
in at all in general at various times over the
previous 18 hours. These calls continue throughout
the day and the rest of the weekend.
07/06/96 10:30 They have broken the routing between our home and the
downtown offices, our network is routing back to MRNet
then back to Winternet, and back to MRNet, in an
endless loop.
Routing to Vector Internet Services is still broken as
well, and had been since the afternoon on 7/5/96.
07/06/96 11:00 Doug McIntyre and myself check the routing of Winternet
networks to customers connected via digital leased
lines between the Winternet offices and theirs.
Looping routing was seen on these networks:
204.246.86.0 All Systems Go
204.246.101.0 Sterling Automation
204.246.105.0 Ensodex
204.246.106.0 HockeyNet (an ISP)
204.246.107.0 CitiLink (an ISP)
204.246.108.0 Barr Engineering
204.246.117.0 CitiLink 2 (an ISP)
204.246.119.0 Silicon Biology
204.246.127.0 Geeks Organizations (our home network)
Also, routing of our new netblock (206.145.128 through
206.145.159.0) was looping between Winternet and
MRNet. This also broke all ISDN connectivity. This
includes:
206.145.128.0 Start of a 16 class C netblock
allocated for ISDN
206.145.143.0 End of a 16 class C netblock allocated
for ISDN
206.145.144.0 Infinity Access Net (an ISP)
206.145.145.0 Computer Aid, Inc.
07/06/96 11:45 UseNet News articles from Winternet to the rest of the
Internet is being blocked.
Both cross-posted and non-cross-posted articles from
the winternet.* groups are not making it to our peers
that have exchanges with Winternet for the local
winternet.* groups.
07/06/96 12:00 mpls-u-2 (nu-2.winternet.net terminal server) is
offline. All routing for all terminal servers has
disappeared. Authentication is failing because of
this.
07/06/96 12:22 All terminal servers are still not authenticating.
07/06/96 12:24 All routing is down. Winternet is off of the Internet
and no traffic can be sent or received from Winternet.
07/06/96 12:33 All routing is still down. Winternet is still off of
the Internet.
07/06/96 12:48 All routing is still down. Winternet is still off of
the Internet.
07/06/96 12:52 Core network (198.174.169.0) is back up, all other
networks are down.
07/06/96 13:09 NNTP (news server) on blackice is down.
07/06/96 13:10 NNTP (news server) on blackice is up.
07/06/96 13:14 Routing for digital line customers is still down.
Routing for Vector Internet Services is still down.
07/06/96 13:50 While talking with Dan Boehlke from MRNet, the router
outages and reconfiguration that occured at Winternet
caused an EIGRP routing storm, breaking connectivity
for all MRNet customers.
07/06/96 15:15 All routing of the digital line customer networks is
still broken.
All commercial web service is down (and looks like
that it had been down since the 5:2x time frame when
the router was taken down and the NVRAM configuration
was wiped).
bobsled (core webserver) had been rebooted
approximately 13:15 on 7/6/96. No reason is known.
icicle (main fileserver, DNS server, secondary mail
server) had been rebooted approximately 13:13 on
7/6/96. No reason is known.
My files were modified and my .ssh directory (which
controls Secure Shell configurations and
authorizations) had been removed without my
permission. Many weird files were made
world-writable, including my private PGP (Pretty Good
Privacy) directory. PGP is a strong encryption
system.
07/06/96 15:25 While I was using Doug McIntyre's account, I removed
as many of my personal files from my own home
directory.
07/06/96 15:30 The 'root' account is logged into the console and
running Xwindows on abominable, my previous console
machine that was on my desk. Doug McIntyre's normal
user access has been removed from abominable as well.
'tundra' is having NFS difficulties with icicle since
icicle had been rebooted at approximately 13:13 on
7/6/96. This is still occuring at 01:16 7/7/96.
Speculation that the internal cabling between tundra
or icicle, into the switch, is now substandard from
being yanked out on the afternoon of 7/5/96.
Directories in /priv have been touched for unknown
reasons.
07/06/96 16:00 Mark Steiger from Hockey Net was told that it was
a hardware and software problem that was preventing
the networking to operate like it had previously.
Whoever he had talked to at the Winternet office said
it would be fixed in 2 to 3 hours from now (now as in
16:00 on 7/6/96). He was also told that they were
'bringing in more people' and that there had been
'problems with their upstream provider and they are
working with them...'.
(the problems that had occured earlier were caused by
the current Winternet employee(s) that had decided to
'break' into the main router and wipe the NVRAM
configuration, there were no hardware or software
problems prior to their invasion)
The console machine named 'outhouse' was powered off
and removed from the internal network.
07/06/96 16:30 Current Winternet employee(s) are unplugging and then
replugging in the cables to the CSU/DSUs on frame-1,
the customer Frame-Relay router.
US West Trouble Ticket #228872 @ 16:16 07/96/96
Circuit ID 15HCGL98279
07/06/96 16:44 mcia-gw (the Minneapolis NAP project) was taken down.
No clue if it was unplugged from the T1 or if the
router was being rebooted and/or reconfigured.
07/06/96 16:50 Both mcia-gw and frame-1 routers are down and are no
longer accessible from the Internet. Customer routes
are still broken.
07/06/96 16:53 Michael Frankowski attempts to post to
winternet.announce and fails to follow moderator format.
I received the complete message from the newsserver
(since I am still listed as the 'moderator').
It is a copy of the press release that was faxed to
all of the news stations in the Twin Cities area.
Here is the press release:
------------------------------------------------------------------------
Press Release
On Friday, July 5, 1996, Mike Horwath was removed from day to day
operations by the board of directors. He remains an owner and retains
his position on the board of directors. The other Winternet employees
made the decision to leave with Mike Horwath. They had the
opportunity to remain employees.
Currently we are experiencing technical difficulties. The Domain Name
Server (DNS) has been unstable for approximately a week. Saturday
morning around 5am our router crashed and one of our providers was
having router trouble as we tried to bring the system back. At this
time, one router is still not connecting. We should have this well on
the way to being solved, but completion may take us 3 hours. The
email system also seems to be unstable. We cannot pinpoint when this
instability originated. We are reconfiguring the mail server and the
DNS to resolve the system inconsistencies. We apologize for the
inconvenience the downtime has caused our clients. We plan to have
the system fully operational sometime this evening.
Thank you for your patience.
Michael Frankowski
Board of Directors
------------------------------------------------------------------------
Now some commentary on the press release from myself...
--
First, Kevin Mathison attempted to fire me unilaterally. I left the
winternet offices on the advice of my attorney. There was no board
meeting to determine this decision. Michael Frankowski was not in the
room at the time of Kevin's statement of:
Mike, you are fired. I am the president now.
Second, Kevin Mathison attempted to unilaterally fire my employees,
they were never offered any reasons, compensation, or the chance at
continuing their health insurance. Most of the employees were not
even notifed and had to hear about this second hand from other
employees.
Third, the DNS server has been stable for many, many months, there
were no problems prior to 7/5/96 when Michael Frankowski and Kevin
Mathison decided to take over the office by force with several other
individuals without any board meeting determining this plan of action.
Forth, email service has been without a problem for over a month. The
previous problems were determined to be a hardware problem with a new
machine that had been put online and then swapped back out.
Fifth, the above does not explain the problems that have occured over
the last 24+ hours since Michael and Kevin thrust themselves into
power. This includes problems with authentication and unable to
utilize SLIP or PPP connections, or the problems with digital line
customer connections.
--
07/06/96 17:46 !nterprise Networking Services (division of US West)
called Doug McIntyre to notify him that he was no
longer listed as the technical contact for the
Frame-Relay circuits (digital leased lines). The new
contact is Carl Mathison, Kevin Mathison's brother.
By his own admission, Carl Mathison knows nothing
about the technical aspects of the business. He has
stated this numerous times to customers when they have
called for help.
07/06/96 18:00 slush, the equipment room console machine, was rebooted
into Windows approximately 3 hours ago. Probably to
prevent both myself and Doug McIntyre from monitoring
what the new employees were doing. (Doug McIntyre
could see a little glimpse when it was booted into
Linux.)
Routing updates:
Some digital line customer networks are working!
199.199.121.0 not working
199.199.122.0 internal network for commercial web
servers, this is still down.
199.199.123.0 internal sub-network for digital line
interconnection points.
199.199.127.0 not working
204.246.64.0 not working, dialup PPP won't work
204.246.65.0 not working, dialup PPP won't work
204.246.66.0 not working, dialup PPP won't work
204.246.67.0 not working, dialup PPP won't work
204.246.68.0 not working, dialup PPP won't work
204.246.69.0 not working, dialup PPP won't work
204.246.70.0 not working, dialup PPP won't work
204.246.71.0 not working, dialup PPP won't work
204.246.75.0 not working
204.246.76.0 not working
204.246.77.0 not working
204.246.86.0 looping All Systems Go
204.246.87.0 looping
204.246.88.0 not working
204.246.94.0 not working
204.246.96.0 not working
204.246.98.0 not working
204.246.99.0 not working
204.246.103.0 not working
204.246.110.0 not working
204.246.113.0 not working
204.246.115.0 not working
204.246.116.0 not working
204.246.118.0 not working
204.246.119.0 looping
204.246.120.0 not working
204.246.121.0 looping
204.246.125.0 looping
204.246.126.0 not working
204.246.127.0 looping Geeks Organizations
206.145.128.0 working, some ISDN customers can now
utilize their service.
206.145.129.0 looping
206.145.130.0 looping
206.145.131.0 looping
206.145.132.0 looping
206.145.133.0 looping
206.145.134.0 looping
206.145.135.0 looping
206.145.136.0 looping
206.145.137.0 looping
206.145.138.0 looping
206.145.139.0 goes to i-1 then routes over T1s to
Vector Internet Services and starts
looping.
206.145.140.0 goes to i-1 then routes over T1s to
Vector Internet Services and starts
looping.
206.145.141.0 goes to i-1 then routes over T1s to
Vector Internet Services and starts
looping.
206.145.142.0 goes to i-1 then routes over T1s to
Vector Internet Services and starts
looping.
206.145.143.0 goes to i-1 then routes over T1s to
Vector Internet Services and starts
looping.
206.145.144.0 looping Infinity Access Net
206.145.145.0 looping Computer Aid, Inc.
206.145.146.0 not working
206.145.150.0 looping
206.145.151.0 looping
206.145.152.0 looping
206.145.153.0 looping
206.145.154.0 looping
206.145.155.0 looping
206.145.156.0 looping
206.145.157.0 looping
206.145.158.0 looping
206.145.159.0 looping
07/06/96 18:30 The *new* employees have replaced the secure FTP server
on icicle with an unknown, and slower responding,
daemon.
07/06/96 19:52 Routing problems still exist. PPP and commercial web
service is still down.
204.246.64.0 not working
204.246.65.0 not working
204.246.66.0 routing to mogul, one of the commercial
web servers. Very odd...
204.246.67.0 not working
Commercial web servers are still in a routing loop
between luge, the primary commercial web server, and
the main router. This is network 199.199.122.0.
07/06/96 20:30 I heard a rumor that a press release had been done by
Michael Frankowski, and that it had been faxed over to
all of the news stations in the Twin Cities area.
To substantiate this rumor, I called the Winternet
offices and talked with Carl Mathison, Kevin
Mathison's brother. Carl was extremely rude with me
while I was asking him questions about the press
release.
These questions included questions on who had written
the press release, who faxed it out, where was Kevin
Mathison, where was Michael Frankowski. Carl told
Mike that Kevin was on his way back to Phoenix. After
further checking a couple hours later, it was noticed
that Kevin was indeed still in the area and logged
into tundra from lutefisk, a Windows 95 machine in the
reception area.
Carl told told that he was not going to answer any
more questions and asked him why he [myself] was
calling anyway.
07/06/96 20:48 I called back again, after calling all of the TV
stations in the area, to confirm that the fax had been
sent. Michael Frankowski was back in the office by
that time. I then asked for him and was given the
runaround by one of the *new* employees. I then asked
again, politely, to speak with him immediately. I was
then put on hold and later, Michael picked up the
phone.
I then proceeded to ask him a few questions:
When could I get a copy of the new keys for the
office. Michael answered that he should be able to
have a key available for him me possibly on Monday.
(I never received this key, ever)
Who wrote the press release. Michael answered that it
was a community effort by all that were present in the
office at the time. [the documents on the web server
states that it was a board of directors announcement.
Um, I was never notified of a board meeting, and by
their own admission, I am still an owner and a board
member as of the time of their posting.]
07/06/96 21:00 Still no SLIP/PP access for customers. Commercial
web servers are working.
07/06/96 21:08 'slush' is back online and running Linux again.
07/06/96 21:16 absolut-zero, the main mail server, was reboot again.
Reason is unknown.
07/06/96 21:30 Doug McIntyre just received the 16:00 status monitoring
message and the 18:00 status monitoring message.
Status monitoring service occurs from 'slush'.
The *new* employees removed the admins mailing list
off of absolut-zero, the main mail server. icicle
still has the list in place. The *new* employees
finally changed the support email aliases to point to
mfrankow, Michael Frankowski.
07/06/96 22:21 Still logging NFS errors from icicle on tundra.
07/07/96 01:12 Routing check:
Still no SLIP/PPP dialins possible.
204.246.64.0 not working
204.246.65.0 not working
204.246.66.0 not working
204.246.67.0 not working
204.246.75.0 looping not used
204.246.86.0 looping All Systems Go
204.246.119.0 looping Silicon Biology
204.246.121.0 looping Tek-Intl
204.246.125.0 looping ITC
204.246.127.0 looping Geeks Organizations
206.145.129.0 looping ISDN CIDR block
206.145.130.0 looping ISDN CIDR block
206.145.131.0 looping ISDN CIDR block
206.145.132.0 looping ISDN CIDR block
206.145.133.0 looping ISDN CIDR block
206.145.134.0 looping ISDN CIDR block
206.145.135.0 looping ISDN CIDR block
206.145.136.0 looping ISDN CIDR block
206.145.137.0 looping ISDN CIDR block
206.145.138.0 looping ISDN CIDR block
206.145.139.0 looping ISDN CIDR block
weird route through i-1
to Vector Internet
Services.
206.145.140.0 looping
206.145.141.0 looping
206.145.142.0 looping
206.145.143.0 looping
206.145.144.0 looping Infinity Access Net
206.145.145.0 looping Computer Aid, Inc.
206.145.146.0 not working
206.145.147.0 looping
206.145.148.0 looping
206.145.149.0 looping
206.145.150.0 looping
206.145.151.0 looping
206.145.152.0 looping
206.145.153.0 looping
206.145.154.0 looping
206.145.155.0 looping
206.145.156.0 looping
206.145.157.0 looping
206.145.158.0 looping
206.145.159.0 looping
Both Ascend Pipelines (for All Systems Go and Computer
Aid, Inc.) are off of the internal network.
07/07/96 05:37 I noticed that authentication was down again.
07/07/96 05:38 authentication is definitely down.
[unkown time] authenticaion is back online since sometime this
morning.
07/07/96 13:48 Routing between Vector and Winternet is still down.
07/07/96 15:00 At about this time, parka and subzero were rebooted
because of CPU data faults in the CPU from a full
temporary filespace filesystem. This should not have
happened with proactive maintainance.
There are no reboot messages in parka's log files
though, which is downright strange.
postmaster alias is updated to point to mfrankow
(Michael Frankowski), tomkat (Thomas Keeley) and Mike
Pate (who's account name escapes me at the moment).
PPP is mostly working, almost all routing is working,
but still some looping routes for ISDN customers, like
All Systems Go and Computer Aid, Inc. Their routers
are still missing from the local network.
07/07/96 21:00 Called in through 336-9999 dialup pool. The 333-2001
dialup pool is not working at all.
Delays in typing any characters. The delay is between
5 seconds and 20 seconds.
From the traceroutes we saw, all terminal server
traffic is on the same network segment as the core
network. We are not able to substantiate this because
we do not have physical access to the equipment room
at this time.
Previously, our network was segmented across 4
segments to handle the traffic load of combined speeds
of 10-12Mbps. (theoretically, an ethernet segment
should be able to handle between 6-8Mbps before it
does a meltdown)
Major problems with dropped network packets and DNS
resolution because of the amount of traffic being
loaded on this *new* network.
07/07/96 23:30 336-9999 is busy for some time, and the 333-2001 dialup
pool is still broken.
New web pages are online for www.winternet.com.
07/08/96 02:38 I noticed that the MCIA router (mcia-gw) is back
online. The extra routing that is needed to be fully
operational as a network exchange point is not
available at this time.
07/08/96 04:30 Most of the broken MCIA routing is back in place, but
Vector Internet Services, Inc. is still inaccessable
from Winternet.
Please note that the content below was last updated on 14 October 1996; the content of this page is being preserved as-is for posterity. The only changes made since that time were (a) to update the page markup to current standards, (b) to update internal links as hosting platforms changed or to point to archive.org when available, and (c) to obscure email addresses located throughout these pages (except for USENET postings). Needless to say, many of the links to external sites are no longer functional after 20+ years.