[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help a sshd newbie! (Here is the results from that script)
On Friday, May 14, 2004, at 13:02 US/Central, kjkeefe@siu.edu wrote:
> + ifconfig
> eth0 Link encap:Ethernet HWaddr 00:30:1B:AE:1F:85
> inet addr:192.168.1.29 Bcast:192.168.1.255
> Mask:255.255.255.0
> inet6 addr: fe80::230:1bff:feae:1f85/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:21089 errors:0 dropped:0 overruns:0 frame:0
> TX packets:15282 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:15236277 (14.5 Mb) TX bytes:1848920 (1.7 Mb)
> Interrupt:18 Base address:0xc000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:245 errors:0 dropped:0 overruns:0 frame:0
> TX packets:245 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:20011 (19.5 Kb) TX bytes:20011 (19.5 Kb)
>
> + ping -c 1 127.0.0.1
> PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
>
> --- 127.0.0.1 ping statistics ---
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
> + ping -c 1 192.168.1.29
> PING 192.168.1.29 (192.168.1.29) 56(84) bytes of data.
>
> --- 192.168.1.29 ping statistics ---
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
Even with your firewall off (all the rules said ACCEPT), you cannot
ping either eth0 or the loopback. You're getting 100% packet loss. As
far as I can tell this doesn't seem to be a problem with either your
firewall nor your sshd daemon, but something else.
I can't think of anything else right now. As a start, I'd do the
following:
- disable the firewall
- boot into single user mode
- enable networking and nothing else
- try to ping the interfaces (lo and eth0)
Regards,
- Robert
-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.