Date: Fri, 04 Jan 2008 16:55:00 -0500 From: Jon Krause <data2@cablespeed.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Cc: Andrew Falanga <af300wsm@gmail.com> Subject: Re: VoIP and SSH Message-ID: <477EAB34.6080808@cablespeed.com> In-Reply-To: <200801041325.02005.af300wsm@gmail.com> References: <200801041325.02005.af300wsm@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Falanga wrote: > Hi, > > I don't understand this one and I'm hoping someone here might know. My > father's router wasn't forwarding connection requests for any port that we'd > configured for sshd to listen on. After changing out his linksys router and > his Cable MODEM (the company said it was a very old modem), the problem was > still present. Oddly enough, if he unplugs his VoIP box from his network, > all this problem goes away and connection requests over ssh and port 22 are > forwarded fine. With the VoIP box present, it doesn't work. > > Neither the FreeBSD machine or the VoIP box share IPs, but it doesn't work > with the VoIP in the network. Any ideas? > > The "VoIP box" is usually an MTA, many include a router/firewall also. It should have an admin interface usually 192.168.0.1 or 192.168.1.1 The cable company technical support should be able to walk you through getting access (or check any documentation that came with the MTA) They may or may not have port options (open or forward) that may allow ssh to work for you. Good Luck, Jon > Andy > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?477EAB34.6080808>