Path: csiph.com!x330-a1.tempe.blueboxinc.net!aioe.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: General Schvantzkoph Newsgroups: comp.os.linux.networking Subject: Re: unable to ping/ssh w/ fedora Date: 9 May 2011 20:52:38 GMT Lines: 26 Message-ID: <92r2gmFdfvU3@mid.individual.net> References: <483af9ad-94d2-47c4-9e7a-05df97e47826@s9g2000yqm.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net jMZK3ID0cEl4Ev45yKRtxQWxECdkCtX73F+H8ZP4v1GMILRwtS Cancel-Lock: sha1:J5Cp3ieWG+iUXbxreOcMAsRcmRY= User-Agent: Pan/0.133 (House of Butterflies) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.networking:260 On Sun, 08 May 2011 11:53:59 -0700, Matias wrote: > Hi all, > > What's going on is I can't ping or ssh from the remote to the local but > I can ping/ssh from the local. My system has a cable ISP and a wireless > router. I've already tried unplugging the cable and the router and > restarting, and I've tried shutting off the firewall. What else could be > the problem? The OS is fedora. > > M. How is your router configured? If you want to ssh into the Fedora box from the Internet you will have to port forward the ssh port to the box. The standard port for ssh is 22, however unless you have a compelling reason for using the standard port you should move ssh to a high port. The reason for moving it is to hide from port scanners, with the standard port you will see about one break in attempt a day, if you pick a non-standard port you won't experience any break in attempts unless you are a high value target. Pings are usually handled by the router. Typically ICMP responses are disabled which is why you can't ping your network, if you want to be able to ping your router you must enable ICMP responses, however be advised that if you do that you are letting the scumbags know that you exist.