Ir para conteúdo
  • Cadastre-se

Servidor Ovh - Problemas


djmaurinho

Posts Recomendados

Gente, eu e um amigo estamos ficando de cabelos em pé ... pois mesmo configurando a placa de rede da forma que está a baixo ele não pinga, o que está acontecendo ? 

[root@xxxxxx ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0:0
DEVICE=eth0:0
BOOTPROTO=static
IPADDR=198.xxxx
NETMASK=255.255.255.255
BROADCAST=198.xxxx
ONBOOT=yes

[root@ns4008649 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0:2
EVICE=eth0:2
BOOTPROTO=static
IPADDR=198xxx..xxxx
NETMASK=255.255.255.255
BROADCAST=198.1xxx6
ONBOOT=yes


[root@xxxx ~]#  ifup eth0:0
[root@xxx ~]#  ifup eth0:1
[root@xxx ~]#  ifup eth0:2
Usage: arping [-fqbDUAV] [-c count] [-w timeout] [-I device] [-s source] destination
  -f : quit on first reply
  -q : be quiet
  -b : keep broadcasting, don't go unicast
  -D : duplicate address detection mode
  -U : Unsolicited ARP mode, update your neighbours
  -A : ARP answer mode, update your neighbours
  -V : print version and exit
  -c count : how many packets to send
  -w timeout : how long to wait for a reply
  -I device : which ethernet device to use (eth0)
  -s source : source ip address
  destination : ask for what ip address
Command line is not complete. Try option "help"
Missing config file ifcfg-ifcfg-eth0:2.

Link para o comentário
Compartilhar em outros sites

PROBLEMA : NÃO CONSIGO PINGAR eth0:0 E NEM A eth0:1 , POREM CONSIGO eth0


RESPOSTA DA OVH

I have checked that your IP failovers XXX.1XX.XX2.174,
XXX.000.XXX.175 e XXX.XXX.XXX.176 are not responding to
ping.
I have also checked the switch and ACL from my side, and
did not notice any issue.

Packet loss on the routers is not an issue, what counts
is the packets reaching to the relevant IP.



CENÁRIO


root@serverovh:~# tcpdump -i eth0:0 icmp -n

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0:0, link-type EN10MB (Ethernet), capture size 65535 bytes
08:43:36.913743 IP 94.XX.75.XXX > XXX.000.00.174: ICMP echo request, id 50749, seq 4, length 64
08:43:36.913779 IP XXX.000.00.174 > 94.XX.75.XXX: ICMP echo reply, id 50749, seq 4, length 64
08:43:37.913817 IP 94.XX.75.XXX > XXX.000.00.174: ICMP echo request, id 50749, seq 5, length 64
08:43:37.913853 IP XXX.000.00.174 > 94.XX.75.XXX: ICMP echo reply, id 50749, seq 5, length 64
08:43:38.636077 IP 189.32.181.30 > XXX.000.00.174: ICMP echo request, id 1, seq 1776, length 40
08:43:38.636113 IP XXX.000.00.174 > 189.32.181.30: ICMP echo reply, id 1, seq 1776, length 40
08:43:38.913701 IP 94.XX.75.XXX > XXX.000.00.174: ICMP echo request, id 50749, seq 6, length 64
08:44:18.913903 IP 94.XX.75.XXX > XXX.000.00.174: ICMP echo request, id 50749, seq 46, length 64
08:44:18.913939 IP XXX.000.00.174 > 94.XX.75.XXX: ICMP echo reply, id 50749, seq 46, length 64
***************** O QUE SIGNIFICA ISSO ? ********************************************************
08:44:19.017178 IP XXX.00.00.00 > 54.251.15.171: ICMP XXX.00.00.00 udp port 53 unreachable, length 80
08:44:19.276771 IP XXX.00.00.00 > 122.248.212.176: ICMP XXX.00.00.00 udp port 53 unreachable, length 80
08:44:19.509749 IP XXX.00.00.00 > 54.251.15.171: ICMP XXX.00.00.00 udp port 53 unreachable, length 84
08:44:19.526334 IP XXX.00.00.00 > 54.251.15.171: ICMP XXX.00.00.00 udp port 53 unreachable, length 84
08:44:19.526593 IP XXX.00.00.00 > 122.248.212.176: ICMP XXX.00.00.00 udp port 53 unreachable, length 80
08:44:19.766243 IP XXX.00.00.00 > 54.251.65.89: ICMP XXX.00.00.00 udp port 53 unreachable, length 80
08:44:19.767175 IP XXX.00.00.00 > 54.251.15.171: ICMP XXX.00.00.00 udp port 53 unreachable, length 84
08:44:19.776572 IP XXX.00.00.00 > 54.251.15.171: ICMP XXX.00.00.00 udp port 53 unreachable, length 84
08:44:19.913895 IP 94.XX.75.XXX > XXX.000.00.174: ICMP echo request, id 50749, seq 47, length 64
08:44:19.913931 IP XXX.000.00.174 > 94.XX.75.XXX: ICMP echo reply, id 50749, seq 47, length 64
08:44:20.017258 IP XXX.00.00.00 > 54.251.65.89: ICMP XXX.00.00.00 udp port 53 unreachable, length 80

***************** fim ********************************************************
169 packets captured
169 packets received by filter



DEBIAN - VEJA A CONFIGURAÇÃO  ( 1 opção )

root@XXXX:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address XXX.00.00.00
        netmask 255.255.255.0
        network 198.27.70.0
        broadcast 198.27.70.255
        gateway 198.27.70.254

dns-nameservers 213.186.33.99

auto eth0:0
iface eth0:0 inet static
address XXX.000.00.174
netmask 255.255.255.255

auto eth0:1
iface eth0:1 inet static
address 000.XX.00.XX2
netmask 255.255.255.255


tb ja usei a configuração ( 2 opção )

        post-up /sbin/ifconfig eth0:0 000.XX.00.XXX netmask 255.255.255.255 broadcast 000.XX.00.XXX
        post-down /sbin/ifconfig eth0:0 dow
        post-up /sbin/ifconfig eth0:1 000.XX.00.XX2 netmask 255.255.255.255 broadcast 000.XX.00.XX2
        post-down /sbin/ifconfig eth0:1 dow
        post-up /sbin/ifconfig eth0:2 000.XX.00.XX3 netmask 255.255.255.255 broadcast 000.XX.00.XX3
        post-down /sbin/ifconfig eth0:2 dow


AMBAS OPÇÕES NAO CONSIGO PINGAR OS IPS
 

Link para o comentário
Compartilhar em outros sites

Tente;

 

DEVICE="eth0:1"
ONBOOT="yes"
BOOTPROTO="static"
IPADDR="IP.AD.RE.SS"
NETMASK="255.255.255.255"
BROADCAST="IP.AD.RE.SS"
GATEWAY="IP.DO.GATEWAY"
 
Já na questão do gateway, o gateway da OVH é sempre o final 254 em sua range de IP, que no caso se o seu IP fosse
 
8.8.8.8, o gateway seria 8.8.8.254
 
Tente efetuar o procedimento acima.
Link para o comentário
Compartilhar em outros sites

Visitante
Este tópico está impedido de receber novos posts.
  • Quem Está Navegando   0 membros estão online

    • Nenhum usuário registrado visualizando esta página.
×
×
  • Criar Novo...

Informação Importante

Concorda com os nossos termos?