Page 1 sur 1

journal parefeu BBox2 Belgacom

Message Publié : 25 Oct 2013 12:09
par o_pauwels
Bonjour,

j'ai remarqué que le log du parefeu de ma Bbox2 est constamment rempli de messages de ce type :

Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Outbound Traffic Blocked - Default policy UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3
Oct 24 11:54:19 2013 Inbound Traffic Blocked - Spoofing protection UDP 192.168.182.1:1900->239.255.255.250:1900 on eth3

Cette adresse 192.168.182.1 ne fait pas partie de mon réseau local, ai-je des raisons de m'inquiéter ou pas du tout? Ce genre de message apparaît 24h/24 7j/7 dans mon log.

Merci pour vos réponses

Re: journal parefeu BBox2 Belgacom

Message Publié : 02 Nov 2013 16:00
par Frater
Une machine (windows) avec une IP fixe...

Le port 1900 est le port de découverte du SSDP de windows pour les périphériques upnp...

Regarde si dans la famille personne n'a ajouté un Pc windows 8 qui vient d'ailleurs...

je m'édites, car 192.168.182.x, c'est le réseaux FON ou VOOFREE avant authentication...

donc un de tes PC s'est connecter sur le FON/VOOFREE puis, rejeter s'est connecter sur ton WiFi... (avec la même ip, Windows est parfois idiot)

regarde les mac adresses si cela ne te dis rien...

Re: journal parefeu BBox2 Belgacom

Message Publié : 03 Nov 2013 13:18
par o_pauwels
C'est étonnant toutes les machines de mon réseau local sont en IP fixe de type 192.168.1.x.
Il y a 2 tablettes, 2 PC (1 Windows 7 et 1 XP) et une XBOX.
Je ne sais vraiment pas d'où elle vient cette adresse IP personne n'utilise FON ici et le DHCP est désactivé.

Re: journal parefeu BBox2 Belgacom

Message Publié : 04 Nov 2013 11:04
par solar10