Menu
▾
▴
ipcop-user
|
From: Hylton C. (ZR1HPC) <hy...@co...> - 2009-08-25 19:57:24
|
Hi, I have three boxes internetworked as such: I have an Ethernet LAN cable coming from an ADSL router into the RED interface of IPCop. The IP assigned by the router to the RED interface is 192.168.1.2 The GREEN interface is directed into a switch that the other two machines plug into. The GREEN IP is designed as 192.168.0.1. For explanation sake( All IP's are statically assigned): IPCop GREEN is box A 192.168.0.1 into switch port 1, 1st Box on switch is box B 192.168.0.2 into switch port 2, 2nd box on switch is box C 192.168.0.3 is on switch port 3. I access the IPCop GUI(A) from both machine B and C with hassle. I can access A from B by using the command: >ssh root@192.168.0.1 and entering the root pass for A. Machine B has become a server of sortrs for mail/files/printing etc, and so I would like to use C ro access A. I enter the same command as above and yet get that connection to 192.168.0.1 port 22 is refused. I can ssh into A by going the following route: C -> B -> A there is no problem. I would assume that the reason that one machine has the ability to connect and not the other is due to port forwarding. I have port forwarding enabled for remote ssh support and cannot add another rule because it says the port is in use. How can I access the filesystem on A directly from C or am I stuck with ssh C -> ssh B -> ssh A because of the remote SSH port forwarding? -- ======================================================================== Lions Club member of http://www.fishhoeklionsclub.org.za Using openSuSE 11.0 with KDE Linux user # 229959 at http://counter.li.org ======================================================================== |
|
From: Jason S. <jsc...@sc...> - 2009-08-25 20:41:17
|
On Tue, 2009-08-25 at 21:57 +0200, Hylton Conacher (ZR1HPC) wrote: > Hi, > > > I have three boxes internetworked as such: > I have an Ethernet LAN cable coming from an ADSL router into the RED > interface of IPCop. The IP assigned by the router to the RED interface > is 192.168.1.2 The GREEN interface is directed into a switch that the > other two machines plug into. The GREEN IP is designed as 192.168.0.1. > > For explanation sake( All IP's are statically assigned): > IPCop GREEN is box A 192.168.0.1 into switch port 1, > 1st Box on switch is box B 192.168.0.2 into switch port 2, > 2nd box on switch is box C 192.168.0.3 is on switch port 3. > > I access the IPCop GUI(A) from both machine B and C with hassle. I can > access A from B by using the command: >ssh root@192.168.0.1 and entering > the root pass for A. > > Machine B has become a server of sortrs for mail/files/printing etc, and > so I would like to use C ro access A. > > I enter the same command as above and yet get that connection to > 192.168.0.1 port 22 is refused. > I can ssh into A by going the following route: C -> B -> A there is no > problem. > > I would assume that the reason that one machine has the ability to > connect and not the other is due to port forwarding. I have port > forwarding enabled for remote ssh support and cannot add another rule > because it says the port is in use. > > How can I access the filesystem on A directly from C or am I stuck with > ssh C -> ssh B -> ssh A because of the remote SSH port forwarding? Wrong port number. Read the manual. :-) 22 is disabled, we use 222 for SSH. |
|
From: Jeffrey S. R. <jef...@ru...> - 2009-08-26 00:35:11
|
-----Original Message----- From: Jason Scheffler [mailto:jsc...@sc...] Sent: Tuesday, August 25, 2009 4:13 PM Cc: IPCop -user Subject: Re: [IPCop-user] Cannot SSH directly into IPCop? >On Tue, 2009-08-25 at 21:57 +0200, Hylton Conacher (ZR1HPC) wrote: >> Hi, >> >> >> I have three boxes internetworked as such: >> I have an Ethernet LAN cable coming from an ADSL router into the RED >> interface of IPCop. The IP assigned by the router to the RED interface >> is 192.168.1.2 The GREEN interface is directed into a switch that the >> other two machines plug into. The GREEN IP is designed as 192.168.0.1. >> >> For explanation sake( All IP's are statically assigned): >> IPCop GREEN is box A 192.168.0.1 into switch port 1, >> 1st Box on switch is box B 192.168.0.2 into switch port 2, >> 2nd box on switch is box C 192.168.0.3 is on switch port 3. >> >> I access the IPCop GUI(A) from both machine B and C with hassle. I can >> access A from B by using the command: >ssh root@192.168.0.1 and entering >> the root pass for A. >> >> Machine B has become a server of sortrs for mail/files/printing etc, and >> so I would like to use C ro access A. >> >> I enter the same command as above and yet get that connection to >> 192.168.0.1 port 22 is refused. >> I can ssh into A by going the following route: C -> B -> A there is no >> problem. >> >> I would assume that the reason that one machine has the ability to >> connect and not the other is due to port forwarding. I have port >> forwarding enabled for remote ssh support and cannot add another rule >> because it says the port is in use. >> >> How can I access the filesystem on A directly from C or am I stuck with >> ssh C -> ssh B -> ssh A because of the remote SSH port forwarding? >Wrong port number. Read the manual. :-) 22 is disabled, we use 222 for >SSH. Also should make sure you allow access in the "Firewall" -> "External Access" page for each network or address you want to manage IPCop by. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Filtered-With-Copfilter: Version 0.84beta4 (ProxSMTP 1.8) Copfilter-Virus-Scanned: ClamAV 0.94.2/9740/Tue Aug 25 14:57:27 2009 Copfilter-Virus-Scanned: AVG 7.5.51, engine 442 270.12.36/2126 2009-05-21 Copfilter-Virus-Scanned: F-PROT 6.2.1.4252 - Engine 4.4.4.56 - Virusdatabase 2009-08-25 1 by Markus Madlener @ http://www.copfilter.org |
|
From: Hylton C. (ZR1HPC) <hy...@co...> - 2009-08-26 16:40:00
|
Jeffrey S. Russell wrote: > > -----Original Message----- > From: Jason Scheffler [mailto:jsc...@sc...] > Sent: Tuesday, August 25, 2009 4:13 PM > Cc: IPCop -user > Subject: Re: [IPCop-user] Cannot SSH directly into IPCop? > >> On Tue, 2009-08-25 at 21:57 +0200, Hylton Conacher (ZR1HPC) wrote: >>> Hi, >>> >>> >>> I have three boxes internetworked as such: >>> I have an Ethernet LAN cable coming from an ADSL router into the RED >>> interface of IPCop. The IP assigned by the router to the RED > interface >>> is 192.168.1.2 The GREEN interface is directed into a switch that > the >>> other two machines plug into. The GREEN IP is designed as > 192.168.0.1. >>> For explanation sake( All IP's are statically assigned): >>> IPCop GREEN is box A 192.168.0.1 into switch port 1, >>> 1st Box on switch is box B 192.168.0.2 into switch port 2, >>> 2nd box on switch is box C 192.168.0.3 is on switch port 3. >>> >>> I access the IPCop GUI(A) from both machine B and C with hassle. I > can >>> access A from B by using the command: >ssh root@192.168.0.1 and > entering >>> the root pass for A. >>> >>> Machine B has become a server of sortrs for mail/files/printing etc, > and >>> so I would like to use C ro access A. >>> >>> I enter the same command as above and yet get that connection to >>> 192.168.0.1 port 22 is refused. >>> I can ssh into A by going the following route: C -> B -> A there is > no >>> problem. >>> >>> I would assume that the reason that one machine has the ability to >>> connect and not the other is due to port forwarding. I have port >>> forwarding enabled for remote ssh support and cannot add another rule >>> because it says the port is in use. >>> >>> How can I access the filesystem on A directly from C or am I stuck > with >>> ssh C -> ssh B -> ssh A because of the remote SSH port forwarding? > >> Wrong port number. Read the manual. :-) 22 is disabled, we use 222 for >> SSH. Oops, tnx > Also should make sure you allow access in the "Firewall" -> "External > Access" page for each network or address you want to manage IPCop by. I added this as a new rule into IPCop:Firewall:External Access for all IP's and using port 222. When I tried to SSH from C -> A with $> SSH root192.168.0.1:222 I still get an error about the server not being known? Regards Hylton -- ======================================================================== Lions Club member of http://www.fishhoeklionsclub.org.za Using openSuSE 11.0 with KDE Linux user # 229959 at http://counter.li.org ======================================================================== |
|
From: Jeffrey S. R. <jef...@ru...> - 2009-08-26 17:42:12
|
>-----Original Message----- >From: Hylton Conacher (ZR1HPC) [mailto:hy...@co...] >Sent: Wednesday, August 26, 2009 12:40 PM >To: IPCop -user >Subject: Re: [IPCop-user] Cannot SSH directly into IPCop? > >Jeffrey S. Russell wrote: >> >> -----Original Message----- >> From: Jason Scheffler [mailto:jsc...@sc...] >> Sent: Tuesday, August 25, 2009 4:13 PM >> Cc: IPCop -user >> Subject: Re: [IPCop-user] Cannot SSH directly into IPCop? >> >>> On Tue, 2009-08-25 at 21:57 +0200, Hylton Conacher (ZR1HPC) wrote: >>>> Hi, >>>> >>>> >>>> I have three boxes internetworked as such: >>>> I have an Ethernet LAN cable coming from an ADSL router into the RED >>>> interface of IPCop. The IP assigned by the router to the RED >> interface >>>> is 192.168.1.2 The GREEN interface is directed into a switch that >> the >>>> other two machines plug into. The GREEN IP is designed as >> 192.168.0.1. >>>> For explanation sake( All IP's are statically assigned): >>>> IPCop GREEN is box A 192.168.0.1 into switch port 1, >>>> 1st Box on switch is box B 192.168.0.2 into switch port 2, >>>> 2nd box on switch is box C 192.168.0.3 is on switch port 3. >>>> >>>> I access the IPCop GUI(A) from both machine B and C with hassle. I >> can >>>> access A from B by using the command: >ssh root@192.168.0.1 and >> entering >>>> the root pass for A. >>>> >>>> Machine B has become a server of sortrs for mail/files/printing etc, >> and >>>> so I would like to use C ro access A. >>>> >>>> I enter the same command as above and yet get that connection to >>>> 192.168.0.1 port 22 is refused. >>>> I can ssh into A by going the following route: C -> B -> A there is >> no >>>> problem. >>>> >>>> I would assume that the reason that one machine has the ability to >>>> connect and not the other is due to port forwarding. I have port >>>> forwarding enabled for remote ssh support and cannot add another rule >>>> because it says the port is in use. >>>> >>>> How can I access the filesystem on A directly from C or am I stuck >> with >>>> ssh C -> ssh B -> ssh A because of the remote SSH port forwarding? >> >>> Wrong port number. Read the manual. :-) 22 is disabled, we use 222 for >>> SSH. > >Oops, tnx > >> Also should make sure you allow access in the "Firewall" -> "External >> Access" page for each network or address you want to manage IPCop by. > >I added this as a new rule into IPCop:Firewall:External Access for all >IP's and using port 222. When I tried to SSH from C -> A with > $> SSH root192.168.0.1:222 I still get an error about the server not >being known? > Try "ssh root@192.168.0.1:222" and that should get you there. You need the "@" symbol for that to work. >Regards >Hylton >-- ======================================================================== Lions Club member of http://www.fishhoeklionsclub.org.za Using openSuSE 11.0 with KDE Linux user # 229959 at http://counter.li.org ======================================================================== ------------------------------------------------------------------------ ------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ IPCop-user mailing list IPC...@li... https://lists.sourceforge.net/lists/listinfo/ipcop-user =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-=-=-=-=-= Filtered-With-Copfilter: Version 0.84beta4 (ProxSMTP 1.8) Copfilter-Filtered-With: SpamAssassin 3.2.5 Copfilter-Virus-Scanned: ClamAV 0.94.2/9743/Wed Aug 26 06:54:01 2009 Copfilter-Virus-Scanned: AVG 7.5.51, engine 442 270.12.36/2126 2009-05-21 Copfilter-Virus-Scanned: F-PROT 6.2.1.4252 - Engine 4.4.4.56 - Virusdatabase 2009-08-25 1 by Markus Madlener @ http://www.copfilter.org =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Filtered-With-Copfilter: Version 0.84beta4 (ProxSMTP 1.8) Copfilter-Virus-Scanned: ClamAV 0.94.2/9743/Wed Aug 26 06:54:01 2009 Copfilter-Virus-Scanned: AVG 7.5.51, engine 442 270.12.36/2126 2009-05-21 Copfilter-Virus-Scanned: F-PROT 6.2.1.4252 - Engine 4.4.4.56 - Virusdatabase 2009-08-25 1 by Markus Madlener @ http://www.copfilter.org |
|
From: Administrator <ad...@di...> - 2009-08-26 18:07:21
|
<snip> > >>> I enter the same command as above and yet get that connection to > >>> 192.168.0.1 port 22 is refused. <snip> > I added this as a new rule into IPCop:Firewall:External Access for all > IP's and using port 222. When I tried to SSH from C -> A with > $> SSH root192.168.0.1:222 I still get an error about the server not > being known? Connection refused, or server not known? Connection refused means the client connected to the server and the connection was rejected. Server not known means the server wasn't recognised by the client, so a reply was received but the certificate didn't match (something). David |
|
From: Kerry E. <ke...@ke...> - 2009-08-26 16:53:05
|
-snip- > I added this as a new rule into IPCop:Firewall:External Access for all > IP's and using port 222. When I tried to SSH from C -> A with > $> SSH root192.168.0.1:222 I still get an error about the server not > being known? > > Regards > Hylton Missed the "@" symbol and probably need to specify -p parameter for port. Try this: ssh -p 222 root@192.168.0.1 It's all in the ssh manpages. Kerry |
|
From: Hylton C. (ZR1HPC) <hy...@co...> - 2009-08-27 09:25:19
|
Hi Kerry, Kerry Erb wrote: > -snip- > >> I added this as a new rule into IPCop:Firewall:External Access for all >> IP's and using port 222. When I tried to SSH from C -> A with >> $> SSH root192.168.0.1:222 I still get an error about the server not >> being known? >> >> Regards >> Hylton > > Missed the "@" symbol and probably need to specify -p parameter for port. Sorry, I didn't copy and paste and must have left the @ out when I retyped it :( > Try this: > > ssh -p 222 root@192.168.0.1 Thanks, your syntax worked perfectly without me having to have an entry on the firewall:external access section of IPcop. The other syntax of $> ssh root@192.168.0.1;222 didn't work yet the 222 refers to the port number in TCP jatgon, at least to my knowledge? > It's all in the ssh manpages. I did try and read them first but the volumes written didn't let me see what I needed. Arrgh beaten bt RTFM again!! :) Tnx again Regards Hylton -- ======================================================================== Lions Club member of http://www.fishhoeklionsclub.org.za Using openSuSE 11.0 with KDE Linux user # 229959 at http://counter.li.org ======================================================================== |
