>Can anyone explain how or where the "199.15.32&0xc70f22" entry could
>have come from? I've been unable to remove it ...
Have you tried
route -delete 199.15.32.0 -netmask 199.15.34.0? (I'm guessing at the .0
part; it got truncated. "netstat -nrA" might help figure out what it
really is)
(I ca
>Can anyone explain how or where the "199.15.32&0xc70f22" entry could
>have come from? I've been unable to remove it ...
Have you tried
route -delete 199.15.32.0 -netmask 199.15.34.0? (I'm guessing at the .0
part; it got truncated. "netstat -nrA" might help figure out what it
really is)
(I c
On Thu, Jul 22, 1999 at 09:30:28AM -0400, Jung, Michael wrote:
> I started getting these messages in the daily security output.
>
> > arpresolve: can't allocate llinfo for 255.255.255.0rt
> > arpresolve: can't allocate llinfo for 255.255.255.0rt
> > arp
On Thu, Jul 22, 1999 at 09:30:28AM -0400, Jung, Michael wrote:
> I started getting these messages in the daily security output.
>
> > arpresolve: can't allocate llinfo for 255.255.255.0rt
> > arpresolve: can't allocate llinfo for 255.255.255.0rt
> > arp
I started getting these messages in the daily security output.
> arpresolve: can't allocate llinfo for 255.255.255.0rt
> arpresolve: can't allocate llinfo for 255.255.255.0rt
> arpresolve: can't allocate llinfo for 255.255.255.0rt
> arpresolve: can't all
I started getting these messages in the daily security output.
> arpresolve: can't allocate llinfo for 255.255.255.0rt
> arpresolve: can't allocate llinfo for 255.255.255.0rt
> arpresolve: can't allocate llinfo for 255.255.255.0rt
> arpresolve: can't all
6 matches
Mail list logo