Re: Traffic Mirroring for Debugging

I suppose you have multiples interfaces on your 192.168.1.10. Normally, you have multiple IP addresses on your 192.168.1.10, one address for each interface. If you bridge interfaces, all your interfaces will have one and only one IP address 192.168.1.10. If you prefer, your machine (192.168.1.1

Re: Traffic Mirroring for Debugging

On Fri, 22 Aug 2008, Bonnel Christophe <[EMAIL PROTECTED]> writes: > Why don't you bridge the interfaces of 192.168.1.10? I don't have in depth experience with bridging, would you mind explaining a little bit about it please. (Example tutorial pointers will be appreciated.) > In that case, you ne

Re: Traffic Mirroring for Debugging

Why don't you bridge the interfaces of 192.168.1.10 ? In that case, you need to reconfigure client to point to 192.168.1.20 and you can sniff your network via the 192.168.1.10 machine ? Hope this helps, Christophe Volkan YAZICI a écrit : Hi, In one of our servers, I want to debug a network

Traffic Mirroring for Debugging

Hi, In one of our servers, I want to debug a network server daemon. The problem is I don't have luxury for a downtime or to iterrupt related server's network traffic. Current routing structure looks like below. VPN Switch (192.168.1.1) -> Server Machine (192.168.1.2) To debug the related serve