Re: [opensuse] Two NIC's, one connected, Ping Both...?
- From: William Hammond <tech@xxxxxxxxxxx>
- Date: Tue, 15 Jul 2008 23:42:41 -0700
At 02:06 AM 7/14/2008, Brian K. White wrote:
----- Original Message ----- From: "William Hammond" <tech@xxxxxxxxxxx>
To: "open SuSE mail list" <opensuse@xxxxxxxxxxxx>
Sent: Monday, July 14, 2008 4:24 AM
Subject: [opensuse] Two NIC's, one connected, Ping Both...?
The real problem here is that I so far have been unable to connect
to a remote 10.3 Server.
Firewall is active, but all necessary ports are open,
Server is behind a Router, and the Router is doing Port Forwarding.
the this case, 5901,5801,22 ---
This is the only site I can;t get into with Putty. (SSH on 22)
One thing that bothers me is the Server.
Like most modern boards it has two built in NIC.s and 100MB and a 1GB.
Both are configured with Private IP's xxx.xxx.xxx.200 and xxx.xxx.xxx.201
(I bet nobody can guess what the xx's represent.. ;-) )
Only one of these RJ45 Ports is connected, but I can Ping them both.
Is that normal...? and is it okay..? or could it be part of my problem..?
It's perfectly normal.
If you configured any nic with an ip, whether it's connected or not, and couldn't ping it from localhost, that would be an indication the nic was bad. Not counting completely broken firewall rules.
Start by turning off the firewall, double-checking that you are running ssh, and connecting from a localhost. ie:
rcSuSEfirewall2 stop
chkconfig sshd on
rcsshd start
ssh localhost.
If that works then leave the firewall off and connect (ssh) from a local pc on the lan.
If that works then enable the firewall and try again
If that works then try connecting(ssh) from remote.
What to look for depends on which of the above works and doesn't work.
For example:
If you turn the firewall off and still can't ssh localhost, then you are most likely not running sshd.
Either way, check netstat -an for attempted tcp connections, and check syslog for possible messages from sshd or possibly the kernel ip filter.
After that comes various routing/netmask/firewall things but I can't very well write the entire process of debugging a service access problem in an email.
Don't rely on ping unless you _know_ that all routers and switches between you & the target are passing icmp.
It's more and more common for routers to block icmp (ping, traceroute, etc) these days. You can't ping through one of those.
Are the basic network settings correct?
ip, netmask, default-route, nameserver(s)?
ifconfig -a
netstat -rn
cat /etc/resolv.conf
First, let me thank you again, rarely do I see such a complete description of the debugging process. Very helpful.
I can SSH from a local workstation into the Server.
The plus is that I can access the workstation remotely and then SSH to the server.
I followed you script, but my knowledge is thin, so I don't know how to interpret the results.
ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:01:6C:DB:24:ED
inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36408756 errors:0 dropped:0 overruns:0 frame:0
TX packets:34308001 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1285106723 (1225.5 Mb) TX bytes:3512018401 (3349.3 Mb)
Interrupt:17 Base address:0x8000
eth1 Link encap:Ethernet HWaddr 00:01:6C:DB:24:EC
inet addr:192.168.1.201 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:434 errors:0 dropped:0 overruns:0 frame:0
TX packets:165 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:28255 (27.5 Kb) TX bytes:16142 (15.7 Kb)
Interrupt:22
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2263227 errors:0 dropped:0 overruns:0 frame:0
TX packets:2263227 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:260237911 (248.1 Mb) TX bytes:260237911 (248.1 Mb)
netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
--
Brian K. White brian@xxxxxxxxx http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- Follow-Ups:
- Re: [opensuse] Two NIC's, one connected, Ping Both...?
- From: Brian K. White
- Re: [opensuse] Two NIC's, one connected, Ping Both...?
- References:
- [opensuse] Two NIC's, one connected, Ping Both...?
- From: William Hammond
- Re: [opensuse] Two NIC's, one connected, Ping Both...?
- From: Brian K. White
- [opensuse] Two NIC's, one connected, Ping Both...?
- Prev by Date: Re: [opensuse] A simple way to send email, from the command line, to a gmail account.
- Next by Date: Re: [opensuse] A simple way to send email, from the command line, to a gmail account.
- Previous by thread: Re: [opensuse] Two NIC's, one connected, Ping Both...?
- Next by thread: Re: [opensuse] Two NIC's, one connected, Ping Both...?
- Index(es):
Relevant Pages
|
