Just to update you on the D-Link 504T problem. After some weeks and a
relocation I've been able to dig further in it and come to the
conclusion that the 504T (mind the 'T') is buggy.
Both the D-Link European help desk and the following page confirmed
what I suspected:
http://www.broadbandrepor
John Mills writes:
> First, are you coming into your LAN from outside, or going outwards?
Either ways.
> If it's an outgoing-connection problem, I would look into the
> firewall setting of the FBSD box. Maybe you set didn't set it up to
> pass the ports for outgoing telnet and ssh, or maybe y
I'm trying to make work a D-Link 504T DSL router/switch with FreeBSD
5.2.1-RELEASE-p6.
I've already realised that IPv6 is not supported by the router so I
compiled an IPv4-only kernel and got to work DNS, HTTP, and FTP.
My problem is that ssh and telnet don't work. I get as far as the
Password p
Ian Dowse writes:
> In message <[EMAIL PROTECTED]>, Warner Losh writes:
> >
> >I think that might be due to a bug in the shared interrupt code that
> >Ian Dowse sent me about earlier today.
>
> Just to add a few details - there is a bug in the update_masks()
> function in i386/isa/intr_mac
Warner Losh writes:
> After talking with Ian Dowse, I think that we've hammered out what may
> cause this. Basically, the problem is
I'm afraid your patch didn't fix the problem on my laptop. It
certainly changed the behaviour and the system doesn't crash any more,
but I'm almost unable to
David Malone writes:
> On Mon, Aug 20, 2001 at 07:51:17PM +0100, Walter C. Pelissero wrote:
> > This enforces my belief that there is something broken in some deeper
> > layer of the network code (see the remote printing issue).
>
> Just out of curiosity, what sort of
John Baldwin writes:
> > fault virtual address = 0x65746e69
> "etni"
>
> Looks like a string has gotten spammed across a data structure or a
> weird pointer, etc.
Whatever mess happend, I've got some news for you that should remove
the NFS module from the list of
[ third time I retry to post this message on the mailing list ]
Peter Pentchev writes:
> On Mon, Aug 20, 2001 at 12:27:24PM +0100, Walter C. Pelissero wrote:
> All those ??'s are the result of kgdb being unable to look inside
> a kernel module. Are you loading NFS as a mo
[ it seems my original article didn't get through ]
I recently upgraded to 4.4-RC.
Now my Vaio panics when I use NFS volumes (as client).
The panic is reproducible with a:
find /some/NFS/mount/point -type f -exec cat {} \; >/dev/null
Sometime I got a "page fault", sometime a "lockmgr: locki
