Página 1 de 3 123 ÚltimoÚltimo
+ Responder ao Tópico



  1. Galera bom dia!

    Está ocorrendo algo estranho no meu servidor proxy, nele tenho 2 placas de rede, eth0 e eth1.
    Estando em uma estação windows e pingando a eth0 e eth1 do proxy que estão neste momento com os ip 192.168.0.38 e 192.168.0.37 respectivamente os mesmos respondem, agora se eu baixo a eth1 que teoricamente está com o ip 192.168.37 e pingo este IP o proxy continua respondendo o ping, porque disto?

    Abraços

  2. apresente:
    ifconfig do proxy

    faça:

    tcpdump -v host maquina.rwindows.que.vai.pingar.no.proxy



  3. eth0 Link encap:Ethernet HWaddr 00:50A6:05:AA
    inet addr:192.168.0.38 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::250:daff:fed6:5aa/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:12448 errors:0 dropped:0 overruns:1 frame:0
    TX packets:2800 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2288206 (2.1 MiB) TX bytes:366928 (358.3 KiB)
    Interrupt:18 Base address:0xe800

    eth1 Link encap:Ethernet HWaddr 00:16:EC:30:F7:76
    inet addr:192.168.0.37 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::216:ecff:fe30:f776/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:6748 errors:0 dropped:0 overruns:0 frame:0
    TX packets:184 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1807318 (1.7 MiB) TX bytes:16488 (16.1 KiB)
    Interrupt:19 Base address:0xec00

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:6 errors:0 dropped:0 overruns:0 frame:0
    TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:952 (952.0 b) TX bytes:952 (952.0 b)



    Resulado do Tcpdump

    tcpdump -v host 192.168.0.2

    13:24:19.097481 IP (tos 0x0, ttl 64, id 63236, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.0.2.device2 > 192.168.0.37.ssh: ., cksum 0x20ce (correct), ack 19833048 win 63027
    13:24:19.097523 IP (tos 0x10, ttl 64, id 34376, offset 0, flags [DF], proto: TCP (6), length: 268) 192.168.0.37.ssh > 192.168.0.2.device2: P 19834572:19834800(228) ack 97449 win 283
    13:24:19.097557 IP (tos 0x0, ttl 64, id 63237, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.0.2.device2 > 192.168.0.37.ssh: ., cksum 0x20ce (correct), ack 19833888 win 62187
    13:24:19.097572 IP (tos 0x10, ttl 64, id 34377, offset 0, flags [DF], proto: TCP (6), length: 460) 192.168.0.37.ssh > 192.168.0.2.device2: P 19834800:19835220(420) ack 97449 win 283
    13:24:19.097602 IP (tos 0x0, ttl 64, id 63238, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.0.2.device2 > 192.168.0.37.ssh: ., cksum 0x20ce (correct), ack 19834344 win 61731

    [2]+ Stopped tcpdump -v host 192.168.0.2

    Obrigado.

  4. esta seria a condição normal, com ambas as placas em funcionamento; como vc diz que BAIXANDO a placa AINDA continua pingango,, isso é MUITO estranho; então, façamos assim:

    ifconfig eth1 down

    e repita os testes acima, pls.



  5. root@uniinteer:~# ifconfig eth0 down
    root@uniinteer:~# ifconfig
    eth1 Link encap:Ethernet HWaddr 00:16:EC:30:F7:76
    inet addr:192.168.0.37 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::216:ecff:fe30:f776/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:12638 errors:0 dropped:0 overruns:0 frame:0
    TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:3440058 (3.2 MiB) TX bytes:20312 (19.8 KiB)
    Interrupt:19 Base address:0xec00

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:12 errors:0 dropped:0 overruns:0 frame:0
    TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1660 (1.6 KiB) TX bytes:1660 (1.6 KiB)

    root@uniinteer:~#


    15:16:03.624876 IP (tos 0x10, ttl 64, id 3280, offset 0, flags [DF], proto: TCP (6), length: 268) 192.168.0.37.ssh > 192.168.0.2.3199: P 1392920:1393148(228) ack 6813 win 283
    15:16:03.624913 IP (tos 0x0, ttl 64, id 23095, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.0.2.3199 > 192.168.0.37.ssh: ., cksum 0x538a (correct), ack 1390448 win 63431
    15:16:03.624916 IP (tos 0x10, ttl 64, id 3281, offset 0, flags [DF], proto: TCP (6), length: 268) 192.168.0.37.ssh > 192.168.0.2.3199: P 1393148:1393376(228) ack 6813 win 283
    15:16:03.624970 IP (tos 0x10, ttl 64, id 3282, offset 0, flags [DF], proto: TCP (6), length: 268) 192.168.0.37.ssh > 192.168.0.2.3199: P 1393376:1393604(228) ack 6813 win 283
    15:16:03.625016 IP (tos 0x10, ttl 64, id 3283, offset 0, flags [DF], proto: TCP (6), length: 444) 192.168.0.37.ssh > 192.168.0.2.3199: P 1393604:1394008(404) ack 6813 win 283
    15:16:03.625062 IP (tos 0x10, ttl 64, id 3284, offset 0, flags [DF], proto: TCP (6), length: 444) 192.168.0.37.ssh > 192.168.0.2.3199: P 1394008:1394412(404) ack 6813 win 283
    15:16:03.625068 IP (tos 0x0, ttl 64, id 23096, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.0.2.3199 > 192.168.0.37.ssh: ., cksum 0x538a (correct), ack 1391780 win 62099
    15:16:03.625103 IP (tos 0x0, ttl 64, id 23097, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.0.2.3199 > 192.168.0.37.ssh: ., cksum 0x538a (correct), ack 1392236 win 61643
    15:16:03.625108 IP (tos 0x10, ttl 64, id 3285, offset 0, flags [DF], proto: TCP (6), length: 444) 192.168.0.37.ssh > 192.168.0.2.3199: P 1394412:1394816(404) ack 6813 win 283
    15:16:03.625149 IP (tos 0x0, ttl 64, id 23098, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.0.2.3199 > 192.168.0.37.ssh: ., cksum 0x538a (correct), ack 1392692 win 61187
    15:16:03.625164 IP (tos 0x10, ttl 64, id 3286, offset 0, flags [DF], proto: TCP (6), length: 268) 192.168.0.37.ssh > 192.168.0.2.3199: P 1394816:1395044(228) ack 6813 win 283
    15:16:03.625201 IP (tos 0x0, ttl 64, id 23099, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.0.2.3199 > 192.168.0.37.ssh: ., cksum 0x538a (correct), ack 1393148 win 60731

    [1]+ Stopped tcpdump -v host 192.168.0.2


    ---------

    Ping da estação na interface do proxy após baixar a mesma


    Microsoft Windows XP [versão 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    c:\>ping 192.168.0.38

    Disparando contra 192.168.0.38 com 32 bytes de dados:

    Resposta de 192.168.0.38: bytes=32 tempo<1ms TTL=64
    Resposta de 192.168.0.38: bytes=32 tempo<1ms TTL=64
    Resposta de 192.168.0.38: bytes=32 tempo<1ms TTL=64
    Resposta de 192.168.0.38: bytes=32 tempo<1ms TTL=64

    Estatísticas do Ping para 192.168.0.38:
    Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de perda),
    Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 0ms, Máximo = 0ms, Média = 0ms

    c:\>






Tópicos Similares

  1. heartbeat+drdb+mon em várias eths
    Por no fórum Servidores de Rede
    Respostas: 0
    Último Post: 15-12-2003, 15:56
  2. Bloquear P2P em somente uma ETH
    Por rafaelpazcolles no fórum Servidores de Rede
    Respostas: 1
    Último Post: 06-06-2003, 20:46
  3. graficos da eth
    Por no fórum Servidores de Rede
    Respostas: 4
    Último Post: 02-04-2003, 22:35
  4. Script para Pegar IP da ETH ou PPP0, e enviar por email
    Por Skill no fórum Servidores de Rede
    Respostas: 0
    Último Post: 28-03-2003, 15:55
  5. 2as Placas de Redes! Pingando pela ETH1 e nao pela ETH0! RED
    Por ganjix no fórum Servidores de Rede
    Respostas: 5
    Último Post: 02-12-2002, 21:12

Visite: BR-Linux ·  VivaOLinux ·  Dicas-L