headers
Steven W. Orr | 3 Sep 2007 06:33
Favicon

sshd config problem.

For reasons that are probably very boring, I want to make a change to my 
sshd config. I have two interfaces, eth0 and eth1. I had previously 
modified my listening port from 22 to something with a couple of extra 
digits for the kiddys. Now I have a situation where I want to maintain 
that setup only on eth0 (a.b.c.d) but I want to make it listen on port 22 
for eth1 (192.168.0.2).

I tried
ListenAddress 192.168.0.2:22
ListenAddress 207.172.210.41:1234
but I must be doing something wrong.

Anyone?

--

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net
Permalink | Reply | 8 comments |
headers
John Abreau | 3 Sep 2007 08:58
Picon
Favicon
Gravatar

Re: sshd config problem.


On Mon, September 3, 2007 12:33 am, Steven W. Orr said:
> For reasons that are probably very boring, I want to make a change to my
> sshd config. I have two interfaces, eth0 and eth1. I had previously
> modified my listening port from 22 to something with a couple of extra
> digits for the kiddys. Now I have a situation where I want to maintain
> that setup only on eth0 (a.b.c.d) but I want to make it listen on port 22
> for eth1 (192.168.0.2).
>
> I tried
> ListenAddress 192.168.0.2:22
> ListenAddress 207.172.210.41:1234
> but I must be doing something wrong.
>
> Anyone?

My first guess would be that you'd need to run two separate instances of
sshd,
each with its own distinct config file.

-- 
John Abreau / Executive Director, Boston Linux & Unix
IM: jabr@... / abreauj <at> AIM / abreauj <at> Yahoo / zusa_it_mgr <at> Skype
Email jabr@... / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99

--

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Bruce Labitt | 3 Sep 2007 14:43
Picon

fc6 mythtv 0.20.2 binary location?

I'm looking to connect to schedules direct for my myth setup.  I updated 
my schedule on August 31, so I should be good for a couple of weeks.  
The link for the RedHat/Fedora binaries on the page 
http://www.mythtv.org/modules.php?name=Web_Links&l_op=viewlink&cid=1
seems to point to a nonexistent page.  Anyone know where they can be 
found?  Or is it just as simple as yum -install mythtv-suite ... ?

TIA,
Bruce
Permalink | Reply | 5 comments |
headers
Frank DiPrete | 3 Sep 2007 15:19
Picon

Re: fc6 mythtv 0.20.2 binary location?


Hi Bruce,

The instructions to use the repo that shalt not be named (starts with an
"a") for yum is posted on the mythtv wiki: (I do not know if 0.20.2 is
in the repo)

http://www.mythtv.org/wiki/index.php/Installing_MythTV_SVN_on_Fedora_Core#Repositories

Use with caution.

As a heavy user of mythtv I gave up on the repo that that starts with an
"a" that shalt not be named the first time it replaced gcc when I wasn't
looking closely.

Since compiling from source I've been much happier.
As an added bonus it gives control over what features you want to
include or exclude.

The svn repo instructions are also on the wiki:
http://www.mythtv.org/wiki/index.php/Installing_MythTV_SVN_on_Fedora_Core#Repositories

The fedora extras yum repo is a big help with some of the multimedia
packages deps.

http://download.fedora.redhat.com/pub/fedora/linux/extras/

[extras]
name=Fedora Extras $releasever - $basearch
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/extras/$releasever/$basearch/
(Continue reading)

Permalink | Reply | 4 comments |
headers
Steven W. Orr | 3 Sep 2007 15:34
Favicon

Re: sshd config problem.

On Monday, Sep 3rd 2007 at 02:58 -0400, quoth John Abreau:

=>
=>On Mon, September 3, 2007 12:33 am, Steven W. Orr said:
=>> For reasons that are probably very boring, I want to make a change to my
=>> sshd config. I have two interfaces, eth0 and eth1. I had previously
=>> modified my listening port from 22 to something with a couple of extra
=>> digits for the kiddys. Now I have a situation where I want to maintain
=>> that setup only on eth0 (a.b.c.d) but I want to make it listen on port 22
=>> for eth1 (192.168.0.2).
=>>
=>> I tried
=>> ListenAddress 192.168.0.2:22
=>> ListenAddress 207.172.210.41:1234
=>> but I must be doing something wrong.
=>>
=>> Anyone?
=>
=>My first guess would be that you'd need to run two separate instances of
=>sshd,
=>each with its own distinct config file.

I believe I don't have to do that. That's why they invented ListenAddress.

--

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net
(Continue reading)

Permalink | Reply | 3 comments |
headers
VirginSnow | 3 Sep 2007 16:20
Favicon

Re: sshd config problem.

> Date: Mon, 3 Sep 2007 09:34:52 -0400 (EDT)
> From: "Steven W. Orr" <steveo@...>

> On Monday, Sep 3rd 2007 at 02:58 -0400, quoth John Abreau:
> 
> =>> I tried
> =>> ListenAddress 192.168.0.2:22
> =>> ListenAddress 207.172.210.41:1234
> =>> but I must be doing something wrong.
> =>>
> =>> Anyone?
> =>
> =>My first guess would be that you'd need to run two separate instances of
> =>sshd,
> =>each with its own distinct config file.
> 
> I believe I don't have to do that. That's why they invented ListenAddress.

Wild guess here... but have you tried the likes of:

ListenAddress 192.168.0.2:22, 207.172.210.41:1234

?
Permalink | Reply | 2 comments |
headers
Dave Johnson | 3 Sep 2007 17:59
Favicon

Re: sshd config problem.

Steven W. Orr writes:
> For reasons that are probably very boring, I want to make a change to my 
> sshd config. I have two interfaces, eth0 and eth1. I had previously 
> modified my listening port from 22 to something with a couple of extra 
> digits for the kiddys. Now I have a situation where I want to maintain 
> that setup only on eth0 (a.b.c.d) but I want to make it listen on port 22 
> for eth1 (192.168.0.2).
> 
> I tried
> ListenAddress 192.168.0.2:22
> ListenAddress 207.172.210.41:1234
> but I must be doing something wrong.
> 
> Anyone?

That should work, but you should also remove any 'Port' config lines
in the config file for the ListenAddress to take effect, expecially if
Port is below the ListenAddress lines.

--

-- 
Dave
Permalink | Reply | 0 comments |
headers
Ted Roche | 3 Sep 2007 18:00
Favicon
Gravatar

Re: sshd config problem.

Steven W. Orr wrote:
> 
> I tried
> ListenAddress 192.168.0.2:22
> ListenAddress 207.172.210.41:1234
> but I must be doing something wrong.
> 

That's what the man page says you should do.

When you tried to do that, what were the symptoms you observed? Did the
first work and the second not? What if you reversed them? Are you able
to access the external interface from an _external_ machine and confirm
it does not respond? Are there firewalls blocking access? Do you get any
error log entries?  Do you have (x)inetd launching your ssh services?

--

-- 
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com
Permalink | Reply | 0 comments |
headers
Steven W. Orr | 3 Sep 2007 18:03
Favicon

Re: sshd config problem.

On Monday, Sep 3rd 2007 at 10:20 -0400, quoth VirginSnow@...:

=>> Date: Mon, 3 Sep 2007 09:34:52 -0400 (EDT)
=>> From: "Steven W. Orr" <steveo@...>
=>
=>> On Monday, Sep 3rd 2007 at 02:58 -0400, quoth John Abreau:
=>> 
=>> =>> I tried
=>> =>> ListenAddress 192.168.0.2:22
=>> =>> ListenAddress 207.172.210.41:1234
=>> =>> but I must be doing something wrong.
=>> =>>
=>> =>> Anyone?
=>> =>
=>> =>My first guess would be that you'd need to run two separate instances of
=>> =>sshd,
=>> =>each with its own distinct config file.
=>> 
=>> I believe I don't have to do that. That's why they invented ListenAddress.
=>
=>Wild guess here... but have you tried the likes of:
=>
=>ListenAddress 192.168.0.2:22, 207.172.210.41:1234

Dunno why, but now it works. Thanks all. 

BTW the line above won't work. It has to be on two lines.

--

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bruce Dawson | 3 Sep 2007 18:12

Re: sshd config problem.

Steven W. Orr wrote:
> On Monday, Sep 3rd 2007 at 10:20 -0400, quoth VirginSnow@...:
>
> =>> Date: Mon, 3 Sep 2007 09:34:52 -0400 (EDT)
> =>> From: "Steven W. Orr" <steveo@...>
> =>
> =>> On Monday, Sep 3rd 2007 at 02:58 -0400, quoth John Abreau:
> =>> 
> =>> =>> I tried
> =>> =>> ListenAddress 192.168.0.2:22
> =>> =>> ListenAddress 207.172.210.41:1234
> =>> =>> but I must be doing something wrong.
> =>> =>>
> =>> =>> Anyone?
> =>> =>
> =>> =>My first guess would be that you'd need to run two separate instances of
> =>> =>sshd,
> =>> =>each with its own distinct config file.
> =>> 
> =>> I believe I don't have to do that. That's why they invented ListenAddress.
> =>
> =>Wild guess here... but have you tried the likes of:
> =>
> =>ListenAddress 192.168.0.2:22, 207.172.210.41:1234
>
> Dunno why, but now it works. Thanks all. 
>   
sshd probably got restarted when logrotate ran this morning.
> BTW the line above won't work. It has to be on two lines
--Bruce
(Continue reading)

Permalink | Reply | 0 comments |

Gmane