Hi Javier,
that is great news. I'll give it a try as soon as I find time for it.
It is *exactly* what I have been looking for.
Have you also considered doing it the other way round? Ethereal could
open a port, and a remote application could connect to it. That way at
least the authentication problem is less prominent. If the remote
application could also tripper start/stop/restart, it would be quite a
usability gain, too.
On 6/28/05, Javier Acuña <javier.acuna@xxxxxxxxxx> wrote:
>
> Hi, I'm resending the previous patch, now the options to set IP address and port number work OK.
>
> In case someone wants to try this, you have to select socket instead of eth0 in the 'Capture Options' preferences, with some IP address and port number.
>
> Cheers
> Javier
>
>
>
>
> ________________________________________________________________
>
> Mensaje enviado desde el Servicio Webmail del Dominio sixbell.cl
>
>
>
>
>
>
> _____________________________
> La informacion contenida en esta transmision es confidencial, y no puede ser usada por otras personas que su(s) destinatario(s). El uso no autorizado de la informacion contenida en esta transmision puede ser sancionado. Si ha recibido esta transmision por error, por favor destruyala y notifique al remitente telefonicamente, con cobro revertido o via e-mail.
>
> The information contained in this transmission is privileged, and may not be used by any person other than its addressee(s). Unauthorized use of the information contained in this transmission may be punished by law. If received in error, please destroy and notify the sender by calling collect or by e-mail.
> _____________________________
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
>
>
>
Attachment:
socket-patch2.gz
Description: Binary data
