Re:[enterasys] Matrix(R) X-Series BGP 4-Byte ASN Support
issue was resolved with firmware update, thanks! 2015-10-07 10:30 GMT-03:00 Gustavo Veras <gustavo@gmail.com>: > Hi all, > > We've been recently assigned our own PI space and a 4byte AS number for > our organization. We now have a requirement to peer with two ISP's for > redundancy etc. > > However, we currently have 2 Matrix X8 routers on the outside which don't > support 4byte AS numbers, the first ISP I need to peer with also does not > provide current support for 4byte AS's. > > matrix-x(router-config)# > > matrix-x(router-config)# router bgp ? > > <1-65535> Autonomous system number --> Only 16bits > > matrix-x(router-config)# router bgp 262477 > ^ > % Invalid input detected at '^' marker > > I'm fine with traditional peering, acceptance of default and customer > routes, RFC1918 filtering and path manipulation, however, how do I inform > the Internet about our AS when nothing in the path seems to support it, is > there any way around this? > > All assistance greatly received. > --- To unsubscribe from enterasys, send email to lists...@unc.edu with the body: unsubscribe enterasys arch...@mail-archive.com
[enterasys] Matrix(R) X-Series BGP 4-Byte ASN Support
Hi all, We've been recently assigned our own PI space and a 4byte AS number for our organization. We now have a requirement to peer with two ISP's for redundancy etc. However, we currently have 2 Matrix X8 routers on the outside which don't support 4byte AS numbers, the first ISP I need to peer with also does not provide current support for 4byte AS's. matrix-x(router-config)# matrix-x(router-config)# router bgp ? <1-65535> Autonomous system number --> Only 16bits matrix-x(router-config)# router bgp 262477 ^ % Invalid input detected at '^' marker I'm fine with traditional peering, acceptance of default and customer routes, RFC1918 filtering and path manipulation, however, how do I inform the Internet about our AS when nothing in the path seems to support it, is there any way around this? All assistance greatly received. --- To unsubscribe from enterasys, send email to lists...@unc.edu with the body: unsubscribe enterasys arch...@mail-archive.com
Re: [enterasys] VLAN Configuration - Email found in subject
Build 1: Router has two vlans: VLAN 100: 192.168.1.1/24 (ISP1) VLAN 200: 192.168.2.1/24 (ISP2) Have to see these addresses by VLAN management (11) port 43,44. 2012/7/11 Patrick Printz ppri...@qcc.mass.edu Where is the routing being done for these vlan’s? ** ** *Patrick Printz* *Network Infrastructure* ** ** Quinsigamond Community College 670 West Boylston Street Worcester, MA 01606-2092 w. 508-854-7517 c. 508-726-9529 ** ** ** ** If a man is called a street sweeper, he should sweep streets even as Michelangelo painted, or Beethoven composed music, or Shakespeare wrote poetry. He should sweep streets so well that all the hosts of heaven and Earth will pause to say, Here lived a great street sweeper who did his job well. ~Martin Luther King, Jr. ** ** *From:* Gustavo Veras [mailto:gustavo@gmail.com] *Sent:* Wednesday, July 11, 2012 11:04 AM *To:* Enterasys Customer Mailing List *Subject:* Re: [enterasys] VLAN Configuration - Email found in subject ** ** Thanks, Erik! Is working well, but VLAN 11 is not working properly. the vlan 11 is only seeing the switches, do not see the vlan100, vlan200. Build 1: Switch IP: 172.16.0.1 Build 2: Switch IP: 172.16.0.2 43 44 was used as a port of management. The following configuration of the switch ports of the second building: B3(su)-show vlan port Port VLAN Ingress Egress Filter Vlan - ge.1.1 11 N tagged: 11,100,200 ge.1.2 100N untagged: 100 ge.1.3 100N untagged: 100 ge.1.4 100N untagged: 100 ge.1.5 100N untagged: 100 ge.1.6 100N untagged: 100 ge.1.7 200N untagged: 200 ge.1.8 200N untagged: 200 ge.1.9 200N untagged: 200 ge.1.10200N untagged: 200 ge.1.11200N untagged: 200 . ge.1.4311 N untagged: 11,100,200 ge.1.4411 N untagged: 11,100,200 Do you know what might be happening? 2012/7/10 Erik Phillips ephill...@ewrsd.k12.nj.us What about: building 1 set vlan create 11,100,200 set vlan egress 100 ge.1.1 tagged set vlan egress 200 ge.1.2 tagged set host vlan 11 building 2 set vlan create 11,100,200 set port vlan ge.1.1-6 100 modify-egress set port vlan ge.1.7-11 200 modify-egress set host vlan 11 Also, netsight (if you have it) can probably do this as well. Check out the enterasys channel on youtube, http://www.youtube.com/watch?v=HbStJOT_m08 and http://www.youtube.com/watch?v=q4VNhLbrmcUfeature=results_mainplaynext=1list=PLD0A4267BC50654DB. I think it provides a good start for setups. Erik Phillips East Windsor Regional Schools (p) 609.443.7738 x1725 (f) 609.443.7861 From: Gustavo Veras [gustavo@gmail.com] Sent: Tuesday, July 10, 2012 6:55 PM To: Enterasys Customer Mailing List Subject: [enterasys] VLAN Configuration - Email found in subject How can I create this setup VLANs on Enterasys? There are two building: Building 1: VLAN 100 - Link1 (Link ISP1) VLAN 200 - Link2 (Link ISP2) Management VLAN 11 (Sees ISP1, ISP2, Switches) The two links come into port 1 and 2 on the switch Enterasys B3G124-48. The buildings are connected by the port 3. Building 2: 1 - Switch Enterasys B3G124-48 12 - PC The first vlan (100) would be distributed to 6 computers and vlan 200 for the other 6. Vlan11 management. Is there an easy way to do this? * --To unsubscribe from enterasys, send email to lists...@unc.edu mailto:lists...@unc.edu with the body: unsubscribe enterasys ephill...@ewrsd.k12.nj.us --- To unsubscribe from enterasys, send email to lists...@unc.edu with the body: unsubscribe enterasys gustavo@gmail.com ** ** - --To unsubscribe from enterasys, send email to lists...@unc.edu with the body: unsubscribe enterasys ppri...@qcc.mass.edu - --To unsubscribe from enterasys, send email to lists...@unc.edu with the body: unsubscribe enterasys gustavo@gmail.com --- To unsubscribe from enterasys, send email to lists...@unc.edu with the body: unsubscribe enterasys arch...@mail-archive.com
[enterasys] VLAN Configuration
How can I create this setup VLANs on Enterasys? There are two building: Building 1: VLAN 100 - Link1 (Link ISP1) VLAN 200 - Link2 (Link ISP2) Management VLAN 11 (Sees ISP1, ISP2, Switches) The two links come into port 1 and 2 on the switch Enterasys B3G124-48. The buildings are connected by the port 3. Building 2: 1 - Switch Enterasys B3G124-48 12 - PC The first vlan (100) would be distributed to 6 computers and vlan 200 for the other 6. Vlan11 management. Is there an easy way to do this? --- To unsubscribe from enterasys, send email to lists...@unc.edu with the body: unsubscribe enterasys arch...@mail-archive.com
[slack-users] Re: Ulimit + Squid
Bem, olhem os resultados: # squidclient -h 127.0.0.1 -p 8080 mgr:dns | more ... Dnsserver Statistics: program: /usr/libexec/squid/dnsserver number running: 100 of 100 requests sent: 408734 replies received: 408734 queue length: 0 avg service time: 82.93 msec # FD PID # Requests # Pending Flags Time Offset Request 1 10 23389 106251 0 0.000 0 (none) 2 11 23390 26402 0 0.000 0 (none) 3 12 233917887 0 0.000 0 (none) 4 13 233922408 0 0.000 0 (none) 5 14 23393 892 0 0.000 0 (none) 6 15 23395 411 0 0.000 0 (none) 7 16 23396 229 0 0.000 0 (none) 8 17 23398 126 0 0.000 0 (none) 9 18 23399 82 0 0.000 0 (none) 10 19 23400 39 0 0.000 0 (none) 11 20 23401 42 0 0.000 0 (none) 12 21 23402 20 0 0.000 0 (none) 13 22 23403 10 0 0.000 0 (none) 14 23 23404 9 0 0.000 0 (none) 15 24 23405 5 0 0.000 0 (none) 16 25 23406 11 0 0.000 0 (none) ... Service Time 14/06/2009 - Nativo Med. Duração Resposta Cache Hit : 2.44 segundos Med. Duração Resposta Cache Miss: 18.51 segundos 15/06/2009 - Nativo Med. Duração Resposta Cache Hit : 5.72 segundos Med. Duração Resposta Cache Miss: 16.79 segundos 16/06/2009 - Nativo Med. Duração Resposta Cache Hit : 1.55 segundos Med. Duração Resposta Cache Miss: 14.11 segundos habilitando a consulta de DNS externa -–disable-internal-dns 17/06/2009 - DNS Externo / Bind9 Med. Duração Resposta Cache Hit : 0.76 segundos Med. Duração Resposta Cache Miss: 0.87 segundos 18/06/2009 - DNS Externo / Bind9 Med. Duração Resposta Cache Hit : 0.73 segundos Med. Duração Resposta Cache Miss: 0.87 segundos 19/06/2009 - DNS Externo / Bind9 Med. Duração Resposta Cache Hit : 1.03 segundos Med. Duração Resposta Cache Miss: 6.62 segundos On 17 jun, 17:19, Herbert Faleiros herb...@faleiros.eti.br wrote: Em Qua 17 Jun 2009, às 11:59:10, Cara Magro escreveu: Tenho outra dúvida: recompilei o squid habilitando a consulta de DNS externa -–disable-internal-dns setei o dns_children em 100 # ps aux | grep dnsserver | grep -v grep | wc -l 100 Tenho informações que é mais lenta do que a nativa interna. Por enquanto está dando conta do recado, em horário de pico eu não tenho o que reclamar. Pelos testes ele resolve mais rápido que o nativo do squid. Nunca usei o Squid com esse DNS interno dele. Sempre deixo ele usar os DNS's do resolv.conf, como aqui tem vários servidores recursivos internos (obviamente não na mesma máquina) é bem tranqüilo usar um DNS externo no proxy's p/ recursão. O Squid cria um socket e faz cache das consultas, olha só: udp 0 0 x.y.z.k:59420 0.0.0.0:* 19640/(squid) e do cache.log: 2009/06/17 17:02:03| DNS Socket created at 187.49.0.28, port 59420, FD 12 note que é a mesma porta (59420). -- Herbert --~--~-~--~~~---~--~~ GUS-BR - Grupo de Usuários de Slackware Brasil http://www.slackwarebrasil.org/ http://groups.google.com/group/slack-users-br Antes de perguntar: http://www.istf.com.br/perguntas/ Para sair da lista envie um e-mail para: slack-users-br+unsubscr...@googlegroups.com -~--~~~~--~~--~--~---
[slack-users] Re: Ulimit + Squid
Bem, habilitando a consulta externa tive respostas mais rápidas do que a nativa... http://wiki.squid-cache.org/Features/Dnsserver mesmo obsoleto, continua ativo ... vou continuar fazendo testes, Abs, Gustavo. --~--~-~--~~~---~--~~ GUS-BR - Grupo de Usuários de Slackware Brasil http://www.slackwarebrasil.org/ http://groups.google.com/group/slack-users-br Antes de perguntar: http://www.istf.com.br/perguntas/ Para sair da lista envie um e-mail para: slack-users-br+unsubscr...@googlegroups.com -~--~~~~--~~--~--~---
[slack-users] Re: layer7 + iptables 1.4.2
Ja tenho L7 rodando faz uns 4 meses aqui na empresa, apliquei no 12.1 (2.6.24.5) 2009/3/18 Igor Gentil igor...@gmail.com vc ja verificou se tem todas as libs apontadas nos #include ? sei que é muita mao, mas se nao tem essa informação no site do L7... Brute force dude! xD MfG -- Igor Gentil Linux user #471248 -- Slackware 2009/3/17 Hellânio Costa jerry.mch...@gmail.com: Boa noite, Bem, antes de qq coisa eu gostaria de dizer q tentei seguir os tutoriais da web antes de estar aqui. seguinte: Estou querendo utilizar o layer7 (http://l7-filter.sourceforge.net/) no meu firewall, mas ha um pequeno detalhe só da erro no meu slackware!! :'( em outras distros deu certo, mas nao serve pro slack, nao me perguntem o pq.. heheeh seguinte: resumidamente: apliquei o patch no meu kernel 2.6.28 (ate ai tudo ok, compilei, reiniciei e tudo certo) # patch -p1 ../netfilter-layer7-v2.21/iptables-1.4-for-kernel-2.6.20forward-layer7-2.21.patch # chmod +x extensions/.layer7-test aplico o patch no iptables e com os passos magicos: ./configure --with-ksource=/usr/src/linux-2.6.28/ make . . . . Making all in extensions make[2]: Entering directory `/usr/src/iptables-1.4.2/extensions' CC libipt_layer7.oo libipt_layer7.c: In function 'help': libipt_layer7.c:41: error: 'IPTABLES_VERSION' undeclared (first use in this function) libipt_layer7.c:41: error: (Each undeclared identifier is reported only once libipt_layer7.c:41: error: for each function it appears in.) libipt_layer7.c: At top level: libipt_layer7.c:52: warning: no previous prototype for 'parse_protocol_file' libipt_layer7.c: In function 'parse_protocol_file': libipt_layer7.c:55: warning: declaration of 'line' shadows a global declaration ../include/iptables.h:16: warning: shadowed declaration is here libipt_layer7.c: In function 'pre_process': libipt_layer7.c:152: warning: declaration of 'rindex' shadows a global declaration /usr/include/string.h:313: warning: shadowed declaration is here libipt_layer7.c: At top level: libipt_layer7.c:52: warning: no previous prototype for 'parse_protocol_file' libipt_layer7.c: In function 'parse_protocol_file': libipt_layer7.c:55: warning: declaration of 'line' shadows a global declaration ../include/iptables.h:16: warning: shadowed declaration is here libipt_layer7.c: In function 'pre_process': libipt_layer7.c:152: warning: declaration of 'rindex' shadows a global declaration /usr/include/string.h:313: warning: shadowed declaration is here libipt_layer7.c: At top level: libipt_layer7.c:205: warning: no previous prototype for 'readl7dir' libipt_layer7.c:377: error: variable 'layer7' has initializer but incomplete type libipt_layer7.c:378: error: unknown field 'name' specified in initializer libipt_layer7.c:378: warning: excess elements in struct initializer libipt_layer7.c:378: warning: (near initialization for 'layer7') libipt_layer7.c:379: error: unknown field 'version' specified in initializer libipt_layer7.c:379: error: 'IPTABLES_VERSION' undeclared here (not in a function) libipt_layer7.c:379: warning: excess elements in struct initializer libipt_layer7.c:379: warning: (near initialization for 'layer7') libipt_layer7.c:380: error: unknown field 'size' specified in initializer libipt_layer7.c:380: warning: excess elements in struct initializer libipt_layer7.c:380: warning: (near initialization for 'layer7') libipt_layer7.c:381: error: unknown field 'userspacesize' specified in initializer libipt_layer7.c:381: warning: excess elements in struct initializer libipt_layer7.c:381: warning: (near initialization for 'layer7') libipt_layer7.c:382: error: unknown field 'help' specified in initializer libipt_layer7.c:382: warning: excess elements in struct initializer libipt_layer7.c:382: warning: (near initialization for 'layer7') libipt_layer7.c:383: error: unknown field 'parse' specified in initializer libipt_layer7.c:383: warning: excess elements in struct initializer libipt_layer7.c:383: warning: (near initialization for 'layer7') libipt_layer7.c:384: error: unknown field 'final_check' specified in initializer libipt_layer7.c:384: warning: excess elements in struct initializer libipt_layer7.c:384: warning: (near initialization for 'layer7') libipt_layer7.c:385: error: unknown field 'print' specified in initializer libipt_layer7.c:385: warning: excess elements in struct initializer libipt_layer7.c:385: warning: (near initialization for 'layer7') libipt_layer7.c:386: error: unknown field 'save' specified in initializer libipt_layer7.c:386: warning: excess elements in struct initializer libipt_layer7.c:386: warning: (near initialization for 'layer7') libipt_layer7.c:387: error: unknown field 'extra_opts' specified in initializer libipt_layer7.c:388: warning: excess elements in struct initializer libipt_layer7.c:388:
