On 09 Feb 2004, Olivier M. wrote:
A session @swinog8 would surely be interesting, but I guess
the main issue would be the time such an operation requires:
for 50-80 people, an hour or more would be necessary. Maybe
there is some space left in the agenda... ?
Up to now, if I have counted
Marcel Stutz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi to all,
Has somewehre Infos about the Harddisk Crash on the Zebra Root Server ?
The System come up today again ?
What harddisk crash? It has an uptime of 223 days... Are you talking
about 194.42.48.126 (the TIX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Andre,
I talk about the .126 Server since the 6.2.2004 my BGP Session is not up anymore.
The Info about the Harddrive Crash i got Friday night from a Frind in Zürich by a Beer.
Mit freundlichen Grüssen
Marcel Stutz
Unix Administrator
-
me too
sh ip bgp su
[...]
194.42.48.126 4 8235 223301 141366 0 0 0 3d21h Idle (PfxCt)
[...]
Rog
Roman Hochuli schrieb:
What harddisk crash? It has an uptime of 223 days... Are
you talking about 194.42.48.126 (the TIX route server) or the
Netlantis stuff also located at TIX?
I have
Roman Hochuli wrote:
I have an uptime of something over 3 days a the moment. Anyway I am
missing ~300 prefixes from the routeserver since that time.
May there be some guys who have to clear their bgp-sessions...?
I remember I had to clear our session to .126 recently due reaching the
max-prefix.
Roger Buchwalder wrote:
194.42.48.126 4 8235 223301 141366 0 0 0 3d21h Idle (PfxCt)
you need to 'clear ip bgp 194.42.48.126' on your end
F.
--
[EMAIL PROTECTED]
I have a script which checks received prefixes againts a minimum-limit. Since Wed Feb
4 15:36:27 CET 2004 it's running wild because since I miss the mentioned ~300
prefixes. I receive at the moment ~580 prefixes. When I configured my script there
were more than 850...
--
Kind regards,
Roman
hi
my routeserver got:
194.42.48.126 4 8235 224108 141379 10281423 0 0 00:08:16 791
^^^
(I've cleared the bgp-session few minutes ago :)=) )
rog
Roman Hochuli schrieb:
I have a script which checks received prefixes
194.42.48.126 4 8235 224108 141379 10281423 0 0 00:08:16 791
Hmm... Maybe I should also clear my session once again...? I still receive less than
you. :)
194.42.48.126 4 8235 122624 80022 899978000 3d22h 586
--
Kind regards,
Roman Hochuli
CCNP, CQS Cable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert,
| From 217.26.52.23:
| Trying 62.2.95.11...
| Connected to mx.hispeed.ch.
| Escape character is '^]'.
| 220 mx.hispeed.ch ESMTP Sendmail 8.12.6/8.12.6/tornado-1.0; Thu, 29 Jan
| 2004 15:53:30 +0100
|
| From 217.26.52.15:
| Trying 62.2.95.11...
Daniel Lorch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert,
| From 217.26.52.23:
| Trying 62.2.95.11...
| Connected to mx.hispeed.ch.
| Escape character is '^]'.
| 220 mx.hispeed.ch ESMTP Sendmail 8.12.6/8.12.6/tornado-1.0; Thu, 29 Jan
| 2004 15:53:30 +0100
|
| From
Andre Oppermann wrote:
Daniel Lorch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert,
| From 217.26.52.23:
| Trying 62.2.95.11...
| Connected to mx.hispeed.ch.
| Escape character is '^]'.
| 220 mx.hispeed.ch ESMTP Sendmail 8.12.6/8.12.6/tornado-1.0; Thu, 29 Jan
Now the users think their mails have been succesfully delivered
because they won't receive a bounce mail until the mail expires
in the queue (1 week). Quite frankly, that sucks.
Uhm, normally they should get warning mails in between, unless
you have changed common settings? At least that
On 09 Feb 2004, Daniel Lorch wrote:
Now the users think their mails have been succesfully delivered
because they won't receive a bounce mail until the mail expires
in the queue (1 week). Quite frankly, that sucks.
Is it still necessary to keep mails in the queue for one week nowadays?
User
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
| If you don't have enough capacity to do the 5xx errors on the main
| mail servers then setup another (small) machine and redirect (instead
| of blocking) all connections to that box and let it emit 5xx errors.
| That can be a very small and fast
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
| | If you don't have enough capacity to do the 5xx errors on the main
| | mail servers then setup another (small) machine and redirect (instead
| | of blocking) all connections to that box and let it emit 5xx errors.
| | That can be a very small
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi
| http://www.cryptnet.net/fdp/crypto/gpg-party.html
to summarize, and please correct me if I omitted anything:
Preparation
===
- - Send your fingerprint to coordinator. You can retrieve
~ your ID with the following command:
~ gpg
17 matches
Mail list logo