Date: Thu, 17 Jun 2004 23:49:41 +0100 From: bob <freebsd@nomoreheroes.org.uk> To: freebsd-questions@freebsd.org Subject: Dlink DSL router doesn't like FreeBSD Message-ID: <1087512581.3954.13.camel@localhost>
next in thread | raw e-mail | index | archive | help
I have had exactly the same experience with linux, using mandrake 10. Everything works from my linux box on the lan to other hosts on the lan. When I try to telnet on ports 22(ssh),25(smtp),80(http) and 110(pop3) NOTHING WORKS. I can browse the web and send/recieve email with Evolution/Thunderbird/Firefox without any problems BUT I cannot use telnet for anything outside of the LAN when I am on my Linux box. My windows laptop can do everything (I didn't try ssh because the windows box doesn't have a client). The only constant factor in this is the D-Link 504t. This has other faults in it anyway, such as not restricting remote access to the web-login screen once the latest firmware is installed. They missed out essential features such as being able to configure the time when it shipped, along with the option to connect on demand which was documented in the mannual but not present in the config dispite being shown in mannual's photographs. Not only this but the mannual was wrong on some points too, showing a feature in one part of the web-config when it had been moved to another section after the mannual was written. Is anyone getting suspicious of the quality of this router ? I use it, and it works, expect for this problem. I don't trust it very much though and I will be glad to see the back of it when I upgrade, unless dlink fix the problems listed above and restore my faith in this product. On Fri, 14 May 2004, Walter C. Pelissero wrote: > 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 prompt, I type it in, and then ssh freezes for a couple of> minutes until it probably goes in timeout and gives up.>> The D-Link help desk is useless; the only thing they suggested was to> return the router to where I bought it. I've anyhow the impression> that the problem might not completely be the router's fault. In fact> I plugged a Windoze machine, installed PuTTY, and ssh seems to work> flawlessly.>> What am I missing here?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1087512581.3954.13.camel>