Dear Alexander,
If nobody objects I plan to commit this change at the end of next week.
LLE_RNLOCK(la); should be LLE_RLOCK(la); in arpresolve
Kind regards,
Ingo Flaschberger
___
freebsd-hackers@freebsd.org mailing list
http
> I'm not sure the the forwarding code works for udp..
> (In fact I'm pretty sure it is not fully implemented)
>
>
> On Mon, 15 Apr 2002 [EMAIL PROTECTED] wrote:
>
> > Hi.
> >
> > I have network interface rl0
> >
> > rl0: flags=8843 mtu 1500
> > inet 192.168.10.22 netmask 0xff00 broad
Hi
On Mon, 15 Apr 2002, Julian Elischer wrote:
> I'm not sure the the forwarding code works for udp..
> (In fact I'm pretty sure it is not fully implemented)
>
>
> On Mon, 15 Apr 2002 [EMAIL PROTECTED] wrote:
>
> > Hi.
> >
> > I have network interface rl0
> >
> > rl0: flags=8843 mtu 1500
> >
> > > the problem is, when i connect after the boot a keyboard at the box, it is
> > > not recognized. at the colocations we often need access to this boxes (not
> > > remote access).
> > > is there a solution for this problem?
>
> Note : this is a way to kill your keyboard : an AT keyboard is n
> > i'm working at an iap, and we are using freebsd (4.2) boxes as routers.
> > normally no keyboard or monitor is attached to the box.
> > the problem is, when i connect after the boot a keyboard at the box, it is
> > not recognized. at the colocations we often need access to this boxes (not
> >
Hi
i'm not sure if that is the right list, but i hope u could help me.
i'm working at an iap, and we are using freebsd (4.2) boxes as routers.
normally no keyboard or monitor is attached to the box.
the problem is, when i connect after the boot a keyboard at the box, it is
not recognized. at the
6 matches
Mail list logo