Re: ssh connects to originating host
On 05/12/2009 04:50:57 PM, Shashank wrote: > See your issue? > No matter who (m?) you try to nslookup, it returns the same IP > address: > 63.251.179.5 > > Can you provide cat /etc/nsswitch output? Please provide this output > on both system A and B. > > Specifically we are looking for the following entry: > > hosts: files dns (Your file may have it in reverse order, if > it > does please change it to look like what I posted and then try again) > /etc/nsswitch.conf is completely stock on both systems. In particular, the hosts line is as you write it above. That's the bad news. The good news is that after both systems hibernated overnight, when I resumed them, all of the connections work as they should. I can ssh from A to B, B is able to NFS mount directories from A. Given that hibernate/resume is supposed to preserve/restore the state of the system, I can't imagine what is going on. I did reboot both systems yesterday without having any effect on the problem. Thanks to all who offered advice. If anyone wishes to pursue the issue further I would be happy to do so. > > > > > r...@mtranch[27]->nslookup mtranch > > Server: 192.168.10.1 > > Address: 192.168.10.1#53 > > > > Non-authoritative answer: > > Name: mtranch.mtranch.com > > Address: 63.251.179.5 > > > > r...@mtranch[28]->nslookup mtranchw > > Server: 192.168.10.1 > > Address: 192.168.10.1#53 > > > > Non-authoritative answer: > > Name: mtranchw.mtranch.com > > Address: 63.251.179.5 > > > >> Hopefully that will help us resolve your issue. > > > > > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
See your issue? No matter who (m?) you try to nslookup, it returns the same IP address: 63.251.179.5 Can you provide cat /etc/nsswitch output? Please provide this output on both system A and B. Specifically we are looking for the following entry: hosts: files dns (Your file may have it in reverse order, if it does please change it to look like what I posted and then try again) > r...@mtranch[27]->nslookup mtranch > Server: 192.168.10.1 > Address: 192.168.10.1#53 > > Non-authoritative answer: > Name: mtranch.mtranch.com > Address: 63.251.179.5 > > r...@mtranch[28]->nslookup mtranchw > Server: 192.168.10.1 > Address: 192.168.10.1#53 > > Non-authoritative answer: > Name: mtranchw.mtranch.com > Address: 63.251.179.5 > >> Hopefully that will help us resolve your issue. > > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
Geoffrey Leach wrote: > r...@mtranch[25]->cat /etc/hosts > # Do not remove the following line, or various programs > # that require network functionality will fail. > 127.0.0.1 localhost.localdomain localhost mtranch.mtranch.com > mtranch > ::1 localhost6.localdomain6 localhost6 > 192.168.10.2 mtranch.mtranch.com mtranch > 192.168.10.3 mtranchw.mtranch.com mtranchw > 192.168.10.4 pvr.mtranch.com pvr > > Isn't that your problem, right there? 127.0.0.1 [...] mtranch This makes both mtranch and pvr resolve hostname "mtranch" to 127.0.0.1 -- which is what you're complaining about -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
Additional info: see below. On 05/12/2009 03:50:27 PM, Geoffrey Leach wrote: On 05/12/2009 03:08:26 PM, Shashank wrote: > So let me see if I understand it correctly. Let's also drop the > domain name > > > System A : > > mtranch eth0 - 192.168.10.2 > mtranchw wlan0 - 192.168.10.4 > > System B: > pvreth0 ?? > wlan0192.168.10.3 > eth0 on B is connected to an OTA HD TV tuner > So far so good... > Now you are connected to system A: > > You type ssh pvr (B) you get connected back to A? > Can you provide cat /etc/hosts on system A ? r...@mtranch[25]->cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost mtranch.mtranch.com mtranch ::1 localhost6.localdomain6 localhost6 192.168.10.2mtranch.mtranch.com mtranch 192.168.10.3mtranchw.mtranch.com mtranchw 192.168.10.4pvr.mtranch.com pvr > > As per your traceroute pvr output, you are getting the 192.168.10.2 > instead of 192.168.10.3. > > Also on system A, can you run: > nslookup pvr > nslookup mtranch > nslookup mtranchw r...@mtranch[26]->nslookup pvr Server: 192.168.10.1 Address:192.168.10.1#53 Non-authoritative answer: Name: pvr.mtranch.com Address: 63.251.179.5 r...@mtranch[27]->nslookup mtranch Server: 192.168.10.1 Address:192.168.10.1#53 Non-authoritative answer: Name: mtranch.mtranch.com Address: 63.251.179.5 r...@mtranch[28]->nslookup mtranchw Server: 192.168.10.1 Address:192.168.10.1#53 Non-authoritative answer: Name: mtranchw.mtranch.com Address: 63.251.179.5 > Hopefully that will help us resolve your issue. No sooner than I hit 'send' I noticed this > System A : > > mtranch eth0 - 192.168.10.2 > mtranchw wlan0 - 192.168.10.4 No. Should be: wlan0 - 192.168.10.3 > > System B: > pvreth0 ?? > wlan0192.168.10.3 No. Should be: wlan0192.168.10.4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
On 05/12/2009 03:08:26 PM, Shashank wrote: > So let me see if I understand it correctly. Let's also drop the > domain > name > > > System A : > > mtranch eth0 - 192.168.10.2 > mtranchw wlan0 - 192.168.10.4 > > System B: > pvreth0 ?? > wlan0192.168.10.3 > eth0 on B is connected to an OTA HD TV tuner > So far so good... > Now you are connected to system A: > > You type ssh pvr (B) you get connected back to A? > Can you provide cat /etc/hosts on system A ? r...@mtranch[25]->cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost mtranch.mtranch.com mtranch ::1 localhost6.localdomain6 localhost6 192.168.10.2mtranch.mtranch.com mtranch 192.168.10.3mtranchw.mtranch.com mtranchw 192.168.10.4pvr.mtranch.com pvr > > As per your traceroute pvr output, you are getting the 192.168.10.2 > instead of 192.168.10.3. > > Also on system A, can you run: > nslookup pvr > nslookup mtranch > nslookup mtranchw r...@mtranch[26]->nslookup pvr Server: 192.168.10.1 Address:192.168.10.1#53 Non-authoritative answer: Name: pvr.mtranch.com Address: 63.251.179.5 r...@mtranch[27]->nslookup mtranch Server: 192.168.10.1 Address:192.168.10.1#53 Non-authoritative answer: Name: mtranch.mtranch.com Address: 63.251.179.5 r...@mtranch[28]->nslookup mtranchw Server: 192.168.10.1 Address:192.168.10.1#53 Non-authoritative answer: Name: mtranchw.mtranch.com Address: 63.251.179.5 > Hopefully that will help us resolve your issue. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
So let me see if I understand it correctly. Let's also drop the domain name System A : mtranch eth0 - 192.168.10.2 mtranchw wlan0 - 192.168.10.4 System B: pvreth0 ?? wlan0192.168.10.3 So far so good... Now you are connected to system A: You type ssh pvr (B) you get connected back to A? Can you provide cat /etc/hosts on system A ? As per your traceroute pvr output, you are getting the 192.168.10.2 instead of 192.168.10.3. Also on system A, can you run: nslookup pvr nslookup mtranch nslookup mtranchw Hopefully that will help us resolve your issue. -S -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
On 05/12/2009 01:20:03 PM, Shashank wrote: > Can you provide the output of following commands on both A and B? > > netstat -nr > traceroute host (A when logged in to B and viceversa) > arp -a ( on both A and B) > ifconfig (on A) eliminate the public IP/GATEway before you post it > here. > > > You may not have the correct path to the network (private) . > Please see reply at end > > > On Tue, May 12, 2009 at 2:29 PM, Geoffrey Leach > wrote: > > On 05/12/2009 11:12:42 AM, Christopher K. Johnson wrote: > >> Geoffrey Leach wrote: > >> > Two systems A and B, connected via wireless. A and B both have > the > >> same > >> > /etc/hosts. Connecting from B to A, "ssh A", works fine. However > on > >> A, > >> > "ssh B" logs me into A. This used to work fine; the only clue I > >> have > >> is > >> > that ssh did not like the stored RSA key. I let it fix it, and > >> that's > >> > when the trouble started. Rebooting A did not fix, nor did > removing > >> the > >> > saved key and repeating. > >> > > >> > Any suggestions? > >> > > >> > Thanks. > >> > > >> > > >> > > >> My best guess: > >> The stored key issue was symptomatic of the problem resolving host > to > >> ip > >> address incorrectly. > >> > >> There are three things to check: > >> 1) Logged on at host A, what does 'host B' command return for > >> information? Is it the correct address for B? If the wrong > address > >> then you need to research whether your dns server or an /etc/hosts > >> entry > >> is the cause. > > > > Keeping in mind that this all worked previously > > The 'domain' is mtranch.com. Quotes because its not a registered > domain > > Host A is mtranch.mtranch.com, host B is pvr.mtranch.com > > > > host B on A: > > r...@mtranch[9]->host pvr > > pvr.mtranch.com has address 63.251.179.5 > > Host pvr.mtranch.com not found: 3(NXDOMAIN) > > Host pvr.mtranch.com not found: 3(NXDOMAIN) > > > > I believe that 63.251.179.5 is my ISP's (I'm on satelite with a > dynamic > > IP address) DNS server. > > > > r...@mtranch[16]->ping pvr > > PING pvr.mtranch.com (192.168.10.4) 56(84) bytes of data. > > > > That's the IP address that's in /etc/hosts. Other direction also > works. > > > > If I go over to pvr, I can ssh to mtranch. However, if I try to NFS > > mount directories on mtranch (A) to pvr (B) that fails with > > "Permission Denied". Again, worked fine yesterday. > > > >> 2) Whatever user you do this as on host A, is there a ~/.ssh/ > config > >> file? And if so, does it have a stanza that defines how to > contact > >> host > >> B, but do so with the wrong name or ip address? > > > > There's no ~/.ssh/config, and /etc/ssh/ssh_config is the stock > version > > from Fedora 10 > > > >> 3) It is also possible, but less likely, that on host A you have > dnat > >> rules in iptables causing the endpoint for that ssh tcp connection > to > >> be > >> changed to a local host based address. > > > > I disabled the firewall (I'm using Firestarter); no change in > behavior > On 'A' -- 192.168.10.3 mtranchw.mtranch.com mtranchw is the wireless connection on A. r...@mtranch[19]->netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.10.00.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.10.00.0.0.0 255.255.255.0 U 0 0 0 wlan0 0.0.0.0 192.168.10.10.0.0.0 UG0 0 0 eth0 r...@mtranch[20]->traceroute pvr traceroute to pvr (192.168.10.4), 30 hops max, 60 byte packets 1 pvr.mtranch.com (192.168.10.4) 0.073 ms 0.036 ms 0.033 ms r...@mtranch[21]->arp -a mtranchw.mtranch.com (192.168.10.3) at 00:1a:ef:03:03:e3 [ether] on eth0 ? (192.168.10.1) at 00:18:4d:88:55:c2 [ether] on eth0 r...@mtranch[22]->ifconfig eth0 Link encap:Ethernet HWaddr 00:18:F3:98:CD:0B inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::218:f3ff:fe98:cd0b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8707 errors:0 dropped:0 overruns:0 frame:0 TX packets:7352 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6635268 (6.3 MiB) TX bytes:714646 (697.8 KiB) Interrupt:19 Base address:0x400 loLink 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:1010 errors:0 dropped:0 overruns:0 frame:0 TX packets:1010 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:104950 (102.4 KiB) TX bytes:104950 (102.4 KiB) wlan0 Link encap:Ethernet HWaddr 00:19:D2:2D:F2:76 inet addr:192.168.10.4 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::219:d2ff:fe2d:f276/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX
Re: ssh connects to originating host
Can you provide the output of following commands on both A and B? netstat -nr traceroute host (A when logged in to B and viceversa) arp -a ( on both A and B) ifconfig (on A) eliminate the public IP/GATEway before you post it here. You may not have the correct path to the network (private) . -S On Tue, May 12, 2009 at 2:29 PM, Geoffrey Leach wrote: > On 05/12/2009 11:12:42 AM, Christopher K. Johnson wrote: >> Geoffrey Leach wrote: >> > Two systems A and B, connected via wireless. A and B both have the >> same >> > /etc/hosts. Connecting from B to A, "ssh A", works fine. However on >> A, >> > "ssh B" logs me into A. This used to work fine; the only clue I >> have >> is >> > that ssh did not like the stored RSA key. I let it fix it, and >> that's >> > when the trouble started. Rebooting A did not fix, nor did removing >> the >> > saved key and repeating. >> > >> > Any suggestions? >> > >> > Thanks. >> > >> > >> > >> My best guess: >> The stored key issue was symptomatic of the problem resolving host to >> ip >> address incorrectly. >> >> There are three things to check: >> 1) Logged on at host A, what does 'host B' command return for >> information? Is it the correct address for B? If the wrong address >> then you need to research whether your dns server or an /etc/hosts >> entry >> is the cause. > > Keeping in mind that this all worked previously > The 'domain' is mtranch.com. Quotes because its not a registered domain > Host A is mtranch.mtranch.com, host B is pvr.mtranch.com > > host B on A: > r...@mtranch[9]->host pvr > pvr.mtranch.com has address 63.251.179.5 > Host pvr.mtranch.com not found: 3(NXDOMAIN) > Host pvr.mtranch.com not found: 3(NXDOMAIN) > > I believe that 63.251.179.5 is my ISP's (I'm on satelite with a dynamic > IP address) DNS server. > > r...@mtranch[16]->ping pvr > PING pvr.mtranch.com (192.168.10.4) 56(84) bytes of data. > > That's the IP address that's in /etc/hosts. Other direction also works. > > If I go over to pvr, I can ssh to mtranch. However, if I try to NFS > mount directories on mtranch (A) to pvr (B) that fails with > "Permission Denied". Again, worked fine yesterday. > >> 2) Whatever user you do this as on host A, is there a ~/.ssh/config >> file? And if so, does it have a stanza that defines how to contact >> host >> B, but do so with the wrong name or ip address? > > There's no ~/.ssh/config, and /etc/ssh/ssh_config is the stock version > from Fedora 10 > >> 3) It is also possible, but less likely, that on host A you have dnat >> rules in iptables causing the endpoint for that ssh tcp connection to >> be >> changed to a local host based address. > > I disabled the firewall (I'm using Firestarter); no change in behavior > > > > > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
On 05/12/2009 11:12:42 AM, Christopher K. Johnson wrote: > Geoffrey Leach wrote: > > Two systems A and B, connected via wireless. A and B both have the > same > > /etc/hosts. Connecting from B to A, "ssh A", works fine. However on > A, > > "ssh B" logs me into A. This used to work fine; the only clue I > have > is > > that ssh did not like the stored RSA key. I let it fix it, and > that's > > when the trouble started. Rebooting A did not fix, nor did removing > the > > saved key and repeating. > > > > Any suggestions? > > > > Thanks. > > > > > > > My best guess: > The stored key issue was symptomatic of the problem resolving host to > ip > address incorrectly. > > There are three things to check: > 1) Logged on at host A, what does 'host B' command return for > information? Is it the correct address for B? If the wrong address > then you need to research whether your dns server or an /etc/hosts > entry > is the cause. Keeping in mind that this all worked previously The 'domain' is mtranch.com. Quotes because its not a registered domain Host A is mtranch.mtranch.com, host B is pvr.mtranch.com host B on A: r...@mtranch[9]->host pvr pvr.mtranch.com has address 63.251.179.5 Host pvr.mtranch.com not found: 3(NXDOMAIN) Host pvr.mtranch.com not found: 3(NXDOMAIN) I believe that 63.251.179.5 is my ISP's (I'm on satelite with a dynamic IP address) DNS server. r...@mtranch[16]->ping pvr PING pvr.mtranch.com (192.168.10.4) 56(84) bytes of data. That's the IP address that's in /etc/hosts. Other direction also works. If I go over to pvr, I can ssh to mtranch. However, if I try to NFS mount directories on mtranch (A) to pvr (B) that fails with "Permission Denied". Again, worked fine yesterday. > 2) Whatever user you do this as on host A, is there a ~/.ssh/config > file? And if so, does it have a stanza that defines how to contact > host > B, but do so with the wrong name or ip address? There's no ~/.ssh/config, and /etc/ssh/ssh_config is the stock version from Fedora 10 > 3) It is also possible, but less likely, that on host A you have dnat > rules in iptables causing the endpoint for that ssh tcp connection to > be > changed to a local host based address. I disabled the firewall (I'm using Firestarter); no change in behavior -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
Tom Horsley wrote: On Tue, 12 May 2009 14:12:42 -0400 Christopher K. Johnson wrote: The stored key issue was symptomatic of the problem resolving host to ip address incorrectly. There is a command who's name I forget for printing the arp tables, so you can find out what mac address the system thinks is hooked to the IP address and if you know the mac of the network interfaces you can tell for sure which one it is talking to. That would be 'arp' with no arguments, or 'arp -n' to show ip addresses without inverse resolution to hostnames. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
On Tue, 12 May 2009 14:12:42 -0400 Christopher K. Johnson wrote: > The stored key issue was symptomatic of the problem resolving host to ip > address incorrectly. There is a command who's name I forget for printing the arp tables, so you can find out what mac address the system thinks is hooked to the IP address and if you know the mac of the network interfaces you can tell for sure which one it is talking to. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ssh connects to originating host
Geoffrey Leach wrote: Two systems A and B, connected via wireless. A and B both have the same /etc/hosts. Connecting from B to A, "ssh A", works fine. However on A, "ssh B" logs me into A. This used to work fine; the only clue I have is that ssh did not like the stored RSA key. I let it fix it, and that's when the trouble started. Rebooting A did not fix, nor did removing the saved key and repeating. Any suggestions? Thanks. My best guess: The stored key issue was symptomatic of the problem resolving host to ip address incorrectly. There are three things to check: 1) Logged on at host A, what does 'host B' command return for information? Is it the correct address for B? If the wrong address then you need to research whether your dns server or an /etc/hosts entry is the cause. 2) Whatever user you do this as on host A, is there a ~/.ssh/config file? And if so, does it have a stanza that defines how to contact host B, but do so with the wrong name or ip address? 3) It is also possible, but less likely, that on host A you have dnat rules in iptables causing the endpoint for that ssh tcp connection to be changed to a local host based address. Chris -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
ssh connects to originating host
Two systems A and B, connected via wireless. A and B both have the same /etc/hosts. Connecting from B to A, "ssh A", works fine. However on A, "ssh B" logs me into A. This used to work fine; the only clue I have is that ssh did not like the stored RSA key. I let it fix it, and that's when the trouble started. Rebooting A did not fix, nor did removing the saved key and repeating. Any suggestions? Thanks. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
