[GTER] Problemas com rotas para: nfe.sefaz.ba.gov.br
Eduardo Schoedler
eschoedler at viavale.com.br
Wed Mar 11 15:17:33 -03 2009
Utilize tracepath, que faz via udp.
Abraços,
Eduardo.
--------------------------------------------------
From: "mantunes" <mantunes.listas at gmail.com>
Sent: Wednesday, March 11, 2009 2:44 PM
To: "Grupo de Trabalho de Engenharia e Operacao de Redes"
<gter at eng.registro.br>
Subject: Re: [GTER] Problemas com rotas para: nfe.sefaz.ba.gov.br
> Hehehe. realmente ele esta filtrando.. porem como tudo na vida tem um
> jeitinho.. nada como um utilitário para burlar essa
> filtragem - tcptraceroute..
>
>
> tcptraceroute -i eth1 nfe.sefaz.ba.gov.br
> tcptraceroute: Symbol `pcap_version' has different size in shared
> object, consider re-linking
> Selected device eth1, address XXX.XXX.XXX.XXX, port 57118 for outgoing
> packets
> Tracing the path to nfe.sefaz.ba.gov.br (200.223.31.86) on TCP port
> 80, 30 hops max
> 1 XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX) 0.680 ms 0.645 ms 0.606 ms
> 2 serial2-0-0-0-igaw-ba-rota-h02.telemar.net.br (201.18.234.213)
> 313.444 ms 8.362 ms 13.476 ms
> 3 20118092010.host.telemar.net.br (201.18.92.10) 12.509 ms
> 20118012086.host.telemar.net.br (201.18.12.86) 94.237 ms
> 20118092010.host.telemar.net.br (201.18.92.10) 96.235 ms
> 4 * * *
> 5 nfe.sefaz.ba.gov.br (200.223.31.86) [open] 282.813 ms 85.745 ms *
> ..
>
> 2009/3/11 MARLON BORBA <mborba at trf3.jus.br>:
>> Via CTBC (e PTT-Metro SP):
>>
>> marlon:~ # traceroute 200.223.31.86
>> traceroute to 200.223.31.86 (200.223.31.86), 30 hops max, 40 byte
>> packets
>> 1 201-48-129-254.jfsp.jus.br (201.48.129.254) 1.788 ms 2.164 ms
>> 1.867 ms
>> 2 201-048-128-050.static.ctbctelecom.com.br (201.48.128.50) 6.077 ms
>> 6.735 ms 7.113 ms
>> 3 telemar.ptt.ansp.br (200.136.34.24) 7.888 ms 7.510 ms 8.309
>> ms
>> 4 200.223.44.181 (200.223.44.181) 8.284 ms 7.318 ms 9.661 ms
>> 5 ge-8-1-0-100-vlm-sp-rotn-01.telemar.net.br (200.164.197.206)
>> 49.853 ms 42.495 ms 200.223.43.194 (200.223.43.194) 35.685 ms
>> 6 fastethernet2-1-0-bdea-ba-rota-01.telemar.net.br (200.164.60.5)
>> 36.647 ms 200223045154.host.telemar.net.br (200.223.45.154) 28.761 ms
>> 24.668 ms
>> 7 200.223.32.94 (200.223.32.94)(N!) 37.552 ms
>> pos6-0-bdea-ba-rotn-01.telemar.net.br (200.223.131.49) 40.253 ms
>> 200.223.32.94 (200.223.32.94)(N!) 35.914 ms
>> marlon:~ #
>>
>>
>>
>> Abraços,
>>
>> Marlon Borba, CISSP, APC DataCenter Associate
>> Técnico Judiciário - Segurança da Informação
>> IPv6 Evangelist - MoReq-Jus Evangelist
>> TRF 3a Região
>> (11) 3012-1581
>> --
>> Practically no IT system is risk free.
>> (NIST Special Publication 800-30)
>> --
>>
>>
>>>>> On Wed, Mar 11, 2009 at 12:08 PM, Humberto Galiza
>> <humbertogaliza at gmail.com>
>> wrote:
>>> Cara, estou aqui no PoP-BA da RNP, testei e tbm não vai...veja:
>>>
>>> # tracert nfe.sefaz.ba.gov.br
>>>
>>> Rastreando a rota para nfe.sefaz.ba.gov.br [200.223.31.86]
>>> com no máximo 30 saltos:
>>>
>>> 2 1 ms 1 ms 1 ms ge-2-0-0-r1-ba.bkb.rnp.br
>> [200.143.252.x]
>>> 3 1 ms 1 ms 1 ms 200.219.145.2
>>> 4 1 ms 1 ms 1 ms 200.223.254.214
>>> 5 2 ms 1 ms 1 ms
>>> fastethernet2-1-0-bdea-ba-rota-01.telemar.net.br
>>> [200.164.60.5]
>>> 6 200.223.8.30 relatórios: Rede de destino inacessível.
>>>
>>> Rastreamento concluído.
>>>
>>> Att,
>>>
>>>
>>> mantunes escreveu:
>>>> deve ser problema de lá.. veja o meu
>>>>
>>>> (Embratel..)
>>>> traceroute nfe.sefaz.ba.gov.br
>>>> traceroute to nfe.sefaz.ba.gov.br (200.223.31.86), 30 hops max, 38
>> byte
>>> packets
>>>> 3 peer-P2-1-gacc01.sdr.embratel.net.br (200.211.219.142) 4.005
>> ms
>>>> 4.076 ms 3.762 ms
>>>> 4 200.223.254.214 (200.223.254.214) 28.421 ms 28.216 ms 28.856
>> ms
>>>> 5 fastethernet2-1-0-bdea-ba-rota-01.telemar.net.br (200.164.60.5)
>>>> 31.379 ms 30.822 ms
>> fastethernet9-0-0-bdea-ba-rota-01.telemar.net.br
>>>> (200.164.60.69) 30.462 ms
>>>> 6 200.223.8.30 (200.223.8.30) 30.167 ms !X * *
>>>>
>>>>
>>>> (via web) -
>>>>
>>>
>> http://www.fifi.org/services/traceroute?hostname=nfe.sefaz.ba.gov.br&nprobes=1
>>> &resolved=yes&submit=Traceroute
>>>>
>>>>
>>>>
>>>> 2009/3/11 Rafael Andrade <rafael at riosulense.com.br>:
>>>>> Bom dia a Todos,
>>>>>
>>>>>
>>>>> Possuo NF-e sendo utilizado na empresa, e estou com dificuldade em
>> chegar ao
>>>>> destino, no caso nfe.sefaz.ba.gov.br.
>>>>>
>>>>> Gostaria de saber como posso estar resolvendo isso, pois é uma
>> situação
>>>>> crítica, e mesmo utilizando links distintos não consigo chegar ao
>> destino.
>>>>>
>>>>> Obrigado a todos.
>>>>>
>>>>>
>>>>> Segue Abaixo Traceroute:
>>>>>
>>>>> ( Origem: BrasilTelecom )
>>>>>
>>>>> [root at gw ~]# traceroute nfe.sefaz.ba.gov.br
>>>>> traceroute to nfe.sefaz.ba.gov.br (200.223.31.86), 30 hops max, 40
>> byte
>>>>> packets
>>>>> 1 router.riosulense.com (200.215.81.97) 11.902 ms 12.042 ms
>> 12.239 ms
>>>>> 2 200.193.87.253 (200.193.87.253) 4.103 ms 4.136 ms 4.434 ms
>>>>> 3 201.10.250.162 (201.10.250.162) 20.673 ms 20.867 ms 20.925
>> ms
>>>>> 4 pos2-1-vlm-sp-rotb-01.telemar.net.br (201.18.24.33) 33.658 ms
>> 34.101 ms
>>>>> 33.748 ms
>>>>> 5 200.223.44.1 (200.223.44.1) 30.841 ms 32.803 ms 32.098 ms
>>>>> 6 ge-8-1-0-100-gua-sp-rotn-01.telemar.net.br (200.164.197.205)
>> 30.796 ms
>>>>> 29.180 ms 29.739 ms
>>>>> 7 200.223.43.194 (200.223.43.194) 57.909 ms 57.421 ms 57.806
>> ms
>>>>> 8 fastethernet9-0-0-bdea-ba-rota-01.telemar.net.br (200.164.60.69)
>> 58.221
>>>>> ms 200223045154.host.telemar.net.br (200.223.45.154) 75.321 ms
>> 75.826 ms
>>>>> 9 200.223.8.30 (200.223.8.30) 60.135 ms !X
>>>>> pos6-0-bdea-ba-rotn-01.telemar.net.br (200.223.131.49) 61.014 ms
>>>>> 200.223.32.94 (200.223.32.94) 66.110 ms !X
>>>>>
>>>>> ( Origem: Embratel )
>>>>>
>>>>> [root at gw backupcp]# traceroute nfe.sefaz.ba.gov.br
>>>>> traceroute to nfe.sefaz.ba.gov.br (200.223.31.86), 30 hops max, 40
>> byte
>>>>> packets
>>>>> 1 200.245.253.201 (200.245.253.201) 2.435 ms 3.284 ms 4.039 ms
>>>>> 2 embratel-F1-1-3-152-gacc01.fns.embratel.net.br (201.90.169.105)
>> 16.667
>>>>> ms 18.609 ms 19.022 ms
>>>>> 3 200.230.245.79 (200.230.245.79) 41.232 ms 43.209 ms 44.795
>> ms
>>>>> 4 ebt-T0-5-0-0-tcore01.ctamr.embratel.net.br (200.230.251.214)
>> 46.151 ms
>>>>> 47.746 ms 49.045 ms
>>>>> 5 ebt-T0-3-0-0-tcore01.spo.embratel.net.br (200.230.251.10)
>> 50.635 ms
>>>>> 51.997 ms 55.883 ms
>>>>> 6 ebt-C2-gacc01.spo.embratel.net.br (200.230.243.10) 57.099 ms
>> 33.589 ms
>>>>> 36.075 ms
>>>>> 7 peer-P4-0-gacc01.spo.embratel.net.br (200.211.219.226) 35.630
>> ms 39.077
>>>>> ms 39.642 ms
>>>>> 8 200.223.44.1 (200.223.44.1) 42.555 ms 44.109 ms 45.479 ms
>>>>> 9 ge-8-1-0-100-gua-sp-rotn-01.telemar.net.br (200.164.197.205)
>> 46.337 ms
>>>>> 46.923 ms 47.321 ms
>>>>> 10 ge-8-1-0-100-vlm-sp-rotn-01.telemar.net.br (200.164.197.206)
>> 78.371 ms
>>>>> 200.223.43.194 (200.223.43.194) 72.271 ms 72.771 ms
>>>>> 11 fastethernet9-0-0-bdea-ba-rota-01.telemar.net.br
>> (200.164.60.69) 75.252
>>>>> ms 76.211 ms fastethernet2-1-0-bdea-ba-rota-01.telemar.net.br
>>>>> (200.164.60.5) 76.718 ms
>>>>> 12 200.223.32.94 (200.223.32.94) 98.807 ms !X
>>>>> 20118234158.host.telemar.net.br (201.18.234.158) 92.200 ms !X
>>>>> (200.223.131.49) 127.863 ms
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> gter list https://eng.registro.br/mailman/listinfo/gter
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>> --
>> gter list https://eng.registro.br/mailman/listinfo/gter
>>
>
>
>
> --
> Marcio Antunes
> Powered by FreeBSD
> ==================================
> * Windows: "Where do you want to go tomorrow?"
> * Linux: "Where do you want to go today?"
> * FreeBSD: "Are you, guys, comming or what?"
> --
> gter list https://eng.registro.br/mailman/listinfo/gter
More information about the gter
mailing list