Yesterday i use the api to remove an IP from the permanent mitigation
(178.32.15.131) but it still on mitigation :
9 te4-1.ccr01.par08.atlas.cogentco.com (154.54.38.250) 14.838 ms
15.217 ms 15.327 ms
10 * * *
11 th2-g1-a9.fr.eu (213.186.32.161) 22.736 ms 22.754 ms 19.318 ms
12 rbx-g1-a9.fr.eu (91.121.131.209) 20.453 ms 19.222 ms 19.886 ms
13 vac1-0-a9.fr.eu.vaccum (178.33.100.149) 20.211 ms 20.411 ms 21.172 ms
14 vac1-1-n7.fr.eu.fire

How i can protect OVH
How i can protect OVH

a
a

x.x.x.x is UP again at 08-10-2013 21:09:18, after 1h 9m of downtime.
selon pingdom
Le 9 octobre 2013 03:06, Flix Lebel a crit :
> Salut Oles,
> Mon client voudrait savoir de combien de temps a t le downtime.
> Merci!
> On 2013-10-08, at 18:09, Oles wrote:
>> http://travaux.ovh.net/?do=details&id=9483
>>
>> Nous avons eu un problme dans les rgles qui
>> dfinit sur le firewall network. L'ensemble
>> du trafic a t filtr par er

Salut Oles,
Mon client voudrait savoir de combien de temps a t le downtime.
Merci!
On 2013-10-08, at 18:09, Oles wrote:
> http://travaux.ovh.net/?do=details&id=9483
> Nous avons eu un problme dans les rgles qui
> dfinit sur le firewall network. L'ensemble
> du trafic a t filtr par erreur. Nous avons
> enlev les rgles en attendant de trouver
> l'origine du problme.
> Durant l'incident, les robots n'ont pas se
> connecter sur

Any news for 188.165.240.169 specific? Seems like while the others got up with disabling/restarting the firewall, i'm still stuck in ping but connection refused on other services.
> ok. I see no rules for you. so it's on our
> side. I will check it in 2H.
> On Tue, Oct 08, 2013 at 10:12:43PM +0200, Mens, Raymon wrote:
>> No Sorry. Same problem still with for example 188.165.240.169, only ping. Connection refused on any other service (i.e. SSH).
>>
>>
>

i have a problem , i can't activate/deactivate the firewall
look
the
response i have in the administration panel prom OVH
An error
occurred
on loading your service information. (There was an error in
the server
response)
ip server 37.187.71.53
ns3359291.ovh.net

http://travaux.ovh.net/?do=details&id=9483
Nous avons eu un problme dans les rgles qui
dfinit sur le firewall network. L'ensemble
du trafic a t filtr par erreur. Nous avons
enlev les rgles en attendant de trouver
l'origine du problme.
Durant l'incident, les robots n'ont pas se
connecter sur l'infra et donc n'ont pas pu
ajouter/enlever les IP qui ont reu des
attaques. Une attaque importante vers une IP
vers BGP n'a pas pu donc tre mit

ENGLISH:
Hi Wojciech,
The only thing that OVH staff is telling us about anti-spam is:
1. They are using VADE RETRO system
2. They block at 145 points score (no idea what is the points)
POLSKI:
Cze Wojciech,
Jedyne odpowiedzi o systemie anty-spam od adminw z OVH to:
1. Uywaj systemu VADE RETRO
2. Blokada jest od 145 punktw (nie wiadomo co to za punkty)
Vladimir Mitiuszew
Architekt Systemw
500 392 142
12 617 61

Bonsoir,
Via l'API tu peux te coder un script qui va intrroger l'tat de toutes
tes ips afin de vrifier si elles en miti ou pas.
Ensuite via cron tu lances ce script, toutes les heures, tous les jours,
ou autre ...
A+
Nicolas.
Le 08/10/2013 22:27, Max Fest a crit :
> Bonsoir tout le monde,
> j'aurais aime savoir si, avec la mitigation automatique, il est
> possible d'avoir une alerte (Mail / sms / signaux de fumee) lors qu'un
>

Hello, bonne ide
Le 8 octobre 2013 22:27, Max Fest a crit :
> Bonsoir tout le monde,
> j'aurais aime savoir si, avec la mitigation automatique, il est possible
> d'avoir une alerte (Mail / sms / signaux de fumee) lors qu'un attaque et
> detecte et que le serveur est mis en mitigation.
> Je demande cela car je viens de voir que cela fait 2 semaines que un de
> mes serveurs subit un petit DDoS (40Mb/s) et que je ne me suis

Bonsoir tout le monde,
j'aurais aime savoir si, avec la mitigation automatique, il est possible
d'avoir une alerte (Mail / sms / signaux de fumee) lors qu'un attaque et
detecte et que le serveur est mis en mitigation.
Je demande cela car je viens de voir que cela fait 2 semaines que un de
mes serveurs subit un petit DDoS (40Mb/s) et que je ne me suis rendu
compte de rien (Merci OVH !).
Merci d'avance.

And I have the same problem
De:
danny0809881@gmail.com
Fecha: 08/10/2013 22:23
Para:
Asunto: Re: [ddos] bhs
Your not understand standing what i am saying
here i can access the whole
panel for the firewall adding in any rules
or anything will not allow me i
get this message
been waiting on OVH
fix this since 3rd September 2013 i am still waiting
can get someone
fix this please give you the ticket number err

Your not understand standing what i am saying here i can access the whole
panel for the firewall adding in any rules or anything will not allow me i
get this message
been waiting on OVH fix this since 3rd September 2013 i am still waiting
can get someone fix this please give you the ticket number error getting
[image: OVH Dedicated Customer Zone]
- Configuration
Network (0)
Infrastructures (3)
ns2014417.ovh.net
ns2291

The previous rules has no effects, all ACL rules applied before doesn't
have any effect on this IP.
IP: 87.98.133.58
And Firewall is disabled on another IP but it still stuck on TNF route
IP: 87.98.134.179
On Tue, Oct 8, 2013 at 10:17 PM, wrote:
> ok. I see no rules for you. so it's on our
> side. I will check it in 2H.
> On Tue, Oct 08, 2013 at 10:12:43PM +0200, Mens, Raymon wrote:
> > No Sorry. Same problem still with for example 188.16

ok. I see no rules for you. so it's on our
side. I will check it in 2H.
On Tue, Oct 08, 2013 at 10:12:43PM +0200, Mens, Raymon wrote:
> No Sorry. Same problem still with for example 188.165.240.169, only ping. Connection refused on any other service (i.e. SSH).
> >
> > vac1: done
> >
> > everybody is up ?
> >
> >> I will restart the Firewall
> >>
> >> ---------------------------------------------------------------------

Yes, only went went you restarted the firewall, now works
On Tue, Oct 8, 2013 at 10:15 PM, Zaretti Steve wrote:
> Services are UP, connexions works now :)
> Le 8 octobre 2013 22:14, a crit :
> > what does it mean "down" ? I see the firewall rules
> > for your IP and it's very restrictive
> >
> > On Tue, Oct 08, 2013 at 10:10:41PM +0200, Zaretti Steve wrote:
> >> Nope: 87.98.179.227 is down atm
> >>
> >> 2013/10/8 :
> >> ><

no ip = no help
On Tue, Oct 08, 2013 at 10:13:12PM +0200, Joseph H. wrote:
> up again here
> On Tue, Oct 8, 2013 at 10:12 PM, Mens, Raymon wrote:
> > No Sorry. Same problem still with for example 188.165.240.169, only ping.
> > Connection refused on any other service (i.e. SSH).
> >
> >
> > >
> > > vac1: done
> > >
> > > everybody is up ?
> > >
> > >> I will restart the Firewall
> > >>
> > >> ----

Services are UP, connexions works now :)
Le 8 octobre 2013 22:14, a crit :
> what does it mean "down" ? I see the firewall rules
> for your IP and it's very restrictive
> On Tue, Oct 08, 2013 at 10:10:41PM +0200, Zaretti Steve wrote:
>> Nope: 87.98.179.227 is down atm
>>
>> 2013/10/8 :
>> >
>> > vac1: done
>> >
>> > everybody is up ?
>> >
>> >> I will restart the Firewall
>> >>
>> >> --------------

what does it mean "down" ? I see the firewall rules
for your IP and it's very restrictive
On Tue, Oct 08, 2013 at 10:10:41PM +0200, Zaretti Steve wrote:
> Nope: 87.98.179.227 is down atm
> 2013/10/8 :
> >
> > vac1: done
> >
> > everybody is up ?
> >
> >> I will restart the Firewall
> >>
> >> ---------------------------------------------------------------------
> >
> > -------------------------------------