- UANOG - uanog.one

Гм
by Vladimir Melnik 18 Jun '04

18 Jun '04

У кого-нибудь наблюдается в почтовых логах нечто подобное? Jun 18 14:07:13 nadegda postfix/smtpd[26136]: connect from mxsf08.cluster1.charter.net[209.225.28.208] Jun 18 14:07:13 nadegda postfix/smtpd[26133]: connect from mxsf14.cluster1.charter.net[209.225.28.214] Jun 18 14:07:13 nadegda postfix/smtpd[26137]: connect from mxsf08.cluster1.charter.net[209.225.28.208] Jun 18 14:07:14 nadegda postfix/smtpd[26139]: connect from mxsf06.cluster1.charter.net[209.225.28.206] Jun 18 14:07:14 nadegda postfix/smtpd[26140]: connect from mxsf28.cluster1.charter.net[209.225.28.228] И вот этого - полный лог. $ grep 'smtpd.*: connect from.*cluster1\.charter\.net' /var/log/maillog | wc -l 20767 Это лог в полночь отротейтился. -- V.Melnik =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

3 2

�� CT-300 ...
by Yury Yaroshevsky 17 Jun '04

17 Jun '04

Добрый вечер. Нет ли у кого прошивки посвежее для CT-300: Hardware rev 05b Firmware version 2.38 А то не хочет дружить с DSLAM от Looptelecom H3780/U 1000 :( -- YY18-RIPE =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

1 0

[fwd] Re: Fwd: RIPE NCC Managing Director's e-mail to UANOG to clarify how RIPE NCC policies are developed
by George L. Yermulnik 17 Jun '04

17 Jun '04

Hello! Вопрос AS'ов в биллинговой процедуре RIPE. Eamonn предлагает придумать альтернативу текущему скорингу AS'ов и заслать для обсуждения в ncc-services-wg(a)ripe.net ----- Forwarded message from Eamonn McGuinness <eamonn(a)ripe.net> ----- Date: Thu, 17 Jun 2004 13:50:05 +0200 From: Eamonn McGuinness <eamonn(a)ripe.net> To: "George L. Yermulnik" <yz(a)iptcom.net> Cc: Andrey Blochintsev <bag(a)iptcom.net>, "Peter V. Metalnikov" <pete(a)lucky.net>, Galina Davydenko <galka(a)lucky.net>, Igor Khasilev <igor(a)paco.net>, Mitrofanov Maxim <mmitrof(a)svitonline.com>, Eugene N Drachenko <geka(a)relc.com> Subject: Re: Fwd: RIPE NCC Managing Director's e-mail to UANOG to clarify how RIPE NCC policies are developed User-Agent: Mutt/1.4.2.1i Hi George, On Thu, Jun 17, 2004 at 01:06:28PM +0300, George L. Yermulnik wrote: > Hello! > On Thu, 17 Jun 2004 at 11:44:57 (+0200), Eamonn McGuinness wrote: > > Thank you for participating at last week's RIPE NCC LIR Training > > course. During our course there was a discussion about Provider > > Independent (PI) requests and routing consequences as well as how the > > RIPE NCC charges its members. I am forwarding you an e-mail sent by > > our Managing Director to the UANOG mailing list a few weeks ago. This > Thanx. Guess all of us are subscribed to UANOG mailing list =) > > is to remind members that it is essential to hear feedback if current > > policies or procedures are unfair and if you wish to see changes. > As I can see the main problem for LIR's (at least hear in Kiev) with RIPE Billing Procedure is that it takes into accont all of AS Numbers registered by the LIR for its customers disregarding if the customer has gone to an other LIR. > So the LIR has to pay for "other LIR's" Customer's ASN. > During the discussion you said it's possible to "transfer" Customer's ASN to another LIR if they agree to "accept" it. But what if they don't? The LIR _has_ to continue paying for "other LIR's" Customer's ASN =( That is correct. This is why you need to generate support to expose this and suggest an alternative. This can be done on the UANOG list and consensus be sent to the NCC Services Working Group mailing list or back to Axel. Was there much discussion on UANOG since Axel's e-mail ? Ciao, Eamonn McGuinness RIPE NCC ----- End forwarded message ----- -- George L. Yermulnik [YZ-RIPE] =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

2 1

оборудование ECI Telecom
by Dmitry Cherkasov 17 Jun '04

17 Jun '04

Hi people, Использует ли кто-либо в Украине оборудование компании ECI Telecom? Интересует информация, в частности, по SDH-мультиплексорам mSDM-1 -- доступность, цены, отзывы. В России, судя по всему ECI используют активно, хотя цен я там тоже не нашел. -- ------------------------------------------------------- Dmitry Cherkasov ISP "Intercom" (380)44 251-12-88 http://www.intercom.net.ua DC1-UANIC CHD1-RIPE =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

2 1

сертификаты для Cisco
by Maks Nefedchenko 16 Jun '04

16 Jun '04

Привет! Вот что удалось узнать. Все сертификаты действуют. Даты, которые на них - для растаможки. Модели, снятые с производства сертифицировать не будут. Киевский офис больше этим не занимается - дали телефон в Москве. Вот список всего, что есть на данный момент: UA1.065.37564-02 08.07.2002 AIR-PCM350/LMC350 UA1.065.37568-02 08.07.2002 AIR-BR350 UA1.065.62079-02 08.10.2002 3620,3640,3661,3662 UA1.065.62081-02 08.10.2002 7505,7507,7513,7576 UA1.065.62085-02 08.10.2002 7204VXR,7206VXR UA1.065.62112-02 08.10.2002 2610,2611,2620,2621 UA1.065.62113-02 08.10.2002 AS5300 UA1.065.30293-03 14.05.2003 2610XM,2611XM,2620XM,2621XM,2650XM,2651XM,2650,2651 UA1.065.44658-03 30.05.2003 IGX8410,IGX8420 UA1.065.44661-03 30.05.2003 BPX8620 UA1.065.92183-03 23.10.2003 C3550-12T,C3550-12G,C3550-24,C3550-48 UA1.065.92189-03 23.10.2003 C2950-12,C2950-24,C2950-48 UA1.030.0000993-04 09.01.2004 AIR-PCM352/LMC350 UA1.030.0000997-04 09.01.2004 AIR-BR350 UA1.030.0019259-04 18.03.2004 AIR-AP1120B UA1.030.0019260-04 18.03.2004 AIR-AP1220B/AIR-MP20B,AIR1230B/AIR-MP20B UA1.030.0019263-04 18.03.2004 PGW2200 UA1.030.0019264-04 18.03.2004 AS5850 Експертний висновок СБУ про IDS4210, IDS4235, IDS4250, PIX515, PIX525. Все доступно на ftp://ftp.viaduk.net/pub/cisco/ -- WB, Maks Nefedchenko NM17-RIPE =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

1 2

SQUID+WCCP+FreeBSD(IPFW)
by Lyubomyr Ferents 16 Jun '04

16 Jun '04

Добрый день, пиплы, вот начинаю внедрять у себя новый сервер под кэш. что приятнее, 5.2.1 или 4.10 для этого? я где-то в районе 4.8-4.9 наткнулся на странные глюки с "pseudo-device gre" или рядом .... пришлось вернуться на FreeBSD с патчем для GRE. а хочется родного "pseudo-device gre" кстати, IPFW использую для перехвата пакетов. в последних версиях с GRE-туннелями под WCCP все нормально? у кого работает такое и счастье приносит? Любомир Ференц =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

2 1

wireless q (802.11)
by Paul Arakelyan 15 Jun '04

15 Jun '04

Сижу я на стуле, в ласты обутый, то ль воды не хватает.... Я типа об-Заурусился наконец. Ну и решил дома в 802.11b peer-to-peer поиграть с ноутом и заурусом. В ноуте - winXP+ proxim rangelan2, driver version 1.4b4, rom version 2.7L4/0+. Впридачу оно умеет snoop и рисовать чудные столбики зелёного цвета (типа частотный спектр чего оно наловило) Когда я на заурусе пинги пускаю - вроде _иногда_ появляются зелёные столбики... В заурусе - linux+ Netgear ma701 - вроде чудно поднимается как eth0, но чего я только не пробовал в комбинациях настроек - никак пинги не проезжают между заурусом и ноутом. Насколько я понимаю - мне или нужно из notebook+proxim сделать master (netgear&zaurus такое точно не могут), или поднять peer-to-peer, но пока ни то ни другое не получилось. Или на расстоянии в пару метров такое не работает? Вобщем - чего кто может посоветовать? А куда можно прийти, чтоб там 802.11b было и можно было поиграться с этим дабы разобраться и по? -- Best regards, Paul Arakelyan. =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

2 1

5300 and Callback-Number
by Alexander Karptsov 15 Jun '04

15 Jun '04

Hi, Никто не подскажет можно ли каким-нибудь образом заставить кошку выслать в сторону радиуса Callback-Number, вбитый юзеровыми руками? =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

2 4

Clarification on PI and AS Number assignments
by Axel Pawlik 14 Jun '04

14 Jun '04

Dear Colleagues, The RIPE NCC has recently received questions about migrating customers with PI and AS Number assignments from one LIR to another. The purpose of the sections below is to clarify this procedure and to remind RIPE NCC Members that the RIPE NCC does not make or change policies. The RIPE NCC follows the decisions and policies set by the community through participation in RIPE Working Groups and RIPE mailing lists. PROVIDER INDEPENDENT (PI) ADDRESS SPACE & AUTONOMOUS SYSTEM (AS) NUMBER RECORDS: There is no need to renumber from one PI address block to another block of the same size when migrating a customer from one LIR to another. Additionally, there is no need to renumber AS Numbers. When migrating a customer from one LIR to another they should always be able to keep the same PI address block. Currently it is not possible for the LIR to "return" the PI address space or AS Number while it is still in use by a customer. Only the user of the PI address space or AS Number can initiate its return. You can approach <lir-help(a)ripe.net> and ask to transfer a resource record from one registry file to another. The RIPE NCC can only transfer records when the transfer is agreed by both LIRs. THE RIPE NCC CHARGING SCHEME: The RIPE NCC 2004 Charging Scheme was approved by the RIPE NCC Members at the General Meeting, September 2003. More information about this meeting is available at: http://www.ripe.net/ripencc/about/gm/gm2003/highlights.html RIPE NCC General Meetings are open to all RIPE NCC Members. At the General Meetings, RIPE NCC Members can vote on the RIPE NCC Charging Scheme for the following year. This ensures that the RIPE NCC uses a Charging Scheme approved by its members. Please note that the RIPE NCC Charging Scheme disregards PI assignments. The RIPE NCC Charging Scheme uses a billing score algorithm to determine billing categories. The algorithm can be modified according to RIPE NCC Members' feedback. RIPE NCC Members can give their feedback to the RIPE NCC Management. They can also give their feedback at RIPE NCC General Meetings. RIPE NCC REGIONAL MEETING, MOSCOW: The RIPE NCC is pleased to invite you to the RIPE NCC Regional Meeting which will take place in Moscow from 16 to 18 June 2004. Please note that registration for the meeting is free. Presentations at the meeting will be both in Russian and English. Simultaneous translation services will be provided. More information is available at: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/ CONTACT INFORMATION: You can send any comments you have about these issues to: Axel Pawlik, Managing Director, RIPE NCC <axel.pawlik(a)ripe.net> OR Jochem de Ruig, Chief Financial Officer, RIPE NCC <jochem(a)ripe.net> Kind regards, Axel Pawlik Managing Director RIPE NCC =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

6 6

Fedora chainik Q
by Alexander Yeremenko 14 Jun '04

14 Jun '04

Обьясните профессиональному BSDшнику, как в этом клятом Subj повесить демона при буте ? А то от этих клятых rc и прочих глазенки разбегаются. И вааще ткните меня носом в mailing lists и handbooks. -- AY7-UANIC || AY15-RIPE =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo(a)uanog.kiev.ua with "unsubscribe uanog" in the body of the message

2 3