Date: Sun, 05 May 2002 14:07:13 -0400 From: Lord Raiden <raiden23@netzero.net> To: freebsd-questions@FreeBSD.ORG Subject: demand dial DSL Message-ID: <4.2.0.58.20020505135842.009a8a60@pop.netzero.net>
next in thread | raw e-mail | index | archive | help
Ok, I just got handed a weird one (and on a Sunday of all days no less) today and I'm curious of an answer. I've got a remote office that is running on DSL and the ISP just told us we have to switch over to the new DSL modem or else. So, we switched. (like I'm gonna argue. I've got enough to worry about this week. hehe) Now here's something that's interesting. The new DSL modem refuses all inbound connections unless there is an active connection behind the modem. AKA, someone on our lan has to be surfing the net or the connection goes dead inbound. Outbound is fine. The connection wakes up instantly when someone sends data across the modem and during that time we can connect to our remote lan and do what we want. But after 15 minutes of no traffic in or out it goes numb again and you can't get any data past the modem. Heck, it's not even pingable. I'm thinking about bugging our ISP for that dsl connection and figure out why it's doing that, but I wanted to see if there was just something simple that I could do instead to keep it from doing that. IF it's a simple 2 second fix that would work great. The new modem they stuck us with is a 3com Sdsl modem slaved into a kingston DSL router with a Fbsd file and remote mail server behind it. IT's not a big thing, but suggestions are welcome. I was thinking about having Cron ping something remotely every 10 minutes or so with a single ping to make sure the connection never shuts down. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.2.0.58.20020505135842.009a8a60>