Re: VoIP and SSH
- From: "Andrew Falanga" <af300wsm@xxxxxxxxx>
- Date: Mon, 7 Jan 2008 09:36:40 -0700
On Jan 7, 2008 8:45 AM, Jon Krause <data2@xxxxxxxxxxxxxx> wrote:
Andrew Falanga wrote:Regardless of the response being late, thank you very much for the
On Friday 04 January 2008 14:55:00 Jon Krause wrote:
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@xxxxxxxxxxx mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to"freebsd-questions-unsubscribe@xxxxxxxxxxx" <freebsd-questions-unsubscribe@xxxxxxxxxxx>
Thanks to all for the suggestions. I'll see what I can find. Something one
of you mentioned has me curious. That being whether or not there is a DHCP
server running. My father's linksys router doles out IPs from 192.168.1.100 - <something> (I forget now). Once, while trying to get this
working, he logged into his system (from his system) using ssh. What was odd
was that he was able to log into his system by using the IP address of 192.168.100.101, but using ifconfig he'd always tell me that the IP was 192.168.1.100. I'm betting that his VoIP box must be doling out IPs as well
as his Linksys router, or something like that.
Jon, what do you mean when you say, "The 'VoIP box' is usually an MTA?" I'm
used to MTA meaning Message Transfer Agent. Is it the same in this case too?
Sorry for the late response.
MTA = "multimedia terminal adapter"
It's a Cable industry term most recently replaced by eMTA (embedded) where
the MTA is embedded in the cablemodem. Most commonly used by Comcast, Time
Warner and others for Packet Cable telephone service.
response. In fact, my father's cable modem service comes from Time Warner's
Road Runner service in upstate NY. I'll bet this must be the problem.
Thanks again.
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
- References:
- VoIP and SSH
- From: Andrew Falanga
- Re: VoIP and SSH
- From: Jon Krause
- Re: VoIP and SSH
- From: Andrew Falanga
- Re: VoIP and SSH
- From: Jon Krause
- VoIP and SSH
- Prev by Date: Re: home dir executable (!/bin/sh, chmod+x) shell scripts won't run without "sh <script>"
- Next by Date: Re: home dir executable (!/bin/sh, chmod+x) shell scripts won't run without "sh <script>"
- Previous by thread: Re: VoIP and SSH
- Next by thread: Log archiving question
- Index(es):
Relevant Pages
|
