help with vic firewall issue

[Robert Olson]

Ah, right, vic uses two sockets.

I suspect that's the problem. By any chance, is the reading socket created 
and bound before the sending socket? (I forget if vic uses a connect() on 
the outgoing udp socket).

At 01:11 PM 2/16/2004, Eric Olson wrote:

>Not only binding to the same port you're connecting to, but also listening
>on that port as follows: (maybe that's what you were saying as well)
>
>vic       UDP eolson-laptop-34:25000->ag-tech.mcs.anl.gov:*
>vic       UDP eolson-laptop-34:25001->ag-tech.mcs.anl.gov:25001
>vic       UDP eolson-laptop-34:25001->ag-tech.mcs.anl.gov:*
>
>Eric
>
>On Mon, 16 Feb 2004, Robert Olson wrote:
>
> > In particular, I'm wondering if it's allowable in unix to have a unicast
> > UDP socket with a source port the same as the dest port, and, if 
> allowable,
> > if it's interfering with teh communication.
> >
> > --bob
> >
> > At 01:02 PM 2/16/2004, Eric Olson wrote:
> >
> > >I don't have one, but I'll look around for one and see if I can find
> > >something about this.
> > >Thanks,
> > >Eric
> > >
> > >On Mon, 16 Feb 2004, Robert Olson wrote:
> > >
> > > > Do you have a copy of the Stevens network book? I wonder if there's 
> some
> > > > socket semantics issue coming up here..
> > > >
> > > > --bob
> > > >
> > > > At 12:50 PM 2/16/2004, Eric Olson wrote:
> > > > >Yes, the problem occurs only when connecting to a bridge (with 
> linux vic).
> > > > >
> > > > >When using the new firewall patch, linux vic's "address in use" error
> > > > >prevents connecting to bridges.
> > > >
> > > >
> >
> >