That's what it was. For some reason, the new system doesn't like the hub and moving the connection to a switch, and using port mirroring is working.
On Thu, 13 May 2010 19:58:59 +0200, Boonie wrote:
> The other option is to attach the hub to the span port and attach the
>
> monitor devices from there. You allready have the equipment for that.
>
> This does not interfere with the normal trafic and if your monitoring PC is
> not sending and data (reverse dns queries?) there should also be no
> collisions.
>
> Dave
>
>
> ----- Original Message -----
> From: <mike@xxxxxxxxxxxx>
> To: "wireshark-users" <wireshark-users@xxxxxxxxxxxxx>
> Sent: Thursday, May 13, 2010 6:52 PM
> Subject: Re: [Wireshark-users] One NIC on public side
>
>
>> Are you sure you want tu run all traffic through a hub? This might lead to
>> packetloss due to colissions.
>>
> It's a temporary setup so that we can get a number of services going right.
> So far, we don't see any packet loss or terrible quality loss and we're even
> passing voip calls through the setup.
> We were using a switch with port monitoring but because we had multiple
> devices which needed to monitor the traffic, we ended up using a hub for
> now.
>
> The setup I'm talking about is...
>
> WAN-Routers----Hub----Firewall----switches----etc
>
> The wireshark and other monitoring systems are connected to the Hub.
>
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe