Re: cvsup TreeList failed connection timed out
On Mon, Mar 16, 2009 at 05:22:04AM +, RW wrote: On Sun, 15 Mar 2009 22:32:49 -0500 Troy t...@twisted.net wrote: I'm having a problem with cvsup and it just started happening. I have other servers on the same LAN that are having no problem connecting to the very same servers. I found other people that had this problem by searching but nothing gave a definitive answer on how to solve this. I tried to rebuild cvsup from source again and it build just fine but the problem still exists. Since you don't mention that you are running an old release, have you tried switching to csup in the base system? I am on RELENG_7. I just rebuilt the world on the machine when this problem started. I should have mentioned that. I also rebuilt the world on a second server sitting right next to this one and it has no problem with CVSUP. There has to be a cause for why this cvsup is failing or a file that can be deleted and rebuilt or some other troubleshooting to this problem. Anyone have ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
cvsup TreeList failed connection timed out
I'm having a problem with cvsup and it just started happening. I have other servers on the same LAN that are having no problem connecting to the very same servers. I found other people that had this problem by searching but nothing gave a definitive answer on how to solve this. I tried to rebuild cvsup from source again and it build just fine but the problem still exists. I turned on tcpdump and there is nothing that stands out why this is happening other than a clear timeout. Thoughts on how to troubleshoot this problem? -Troy Parsing supfile /etc/cvsupfile Connecting to cvsup10.FreeBSD.org Connected to cvsup10.FreeBSD.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection src-all/cvs TreeList failed: Network write failure: Connection timed out Will retry at 22:34:40 ^C ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvsup TreeList failed connection timed out
On Sun, 15 Mar 2009 22:32:49 -0500 Troy t...@twisted.net wrote: I'm having a problem with cvsup and it just started happening. I have other servers on the same LAN that are having no problem connecting to the very same servers. I found other people that had this problem by searching but nothing gave a definitive answer on how to solve this. I tried to rebuild cvsup from source again and it build just fine but the problem still exists. Since you don't mention that you are running an old release, have you tried switching to csup in the base system? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Slow DNS (and host: connection timed out)
On Tuesday 10 February 2009 09:33:36 Mel wrote:
On Thursday 05 February 2009 22:55:56 David Naylor wrote:
Hi,
My ISP is using a WinGate DNS but resolving host names often takes a long
time. The problem is also present in Konqueror (3 4) and Firefox.
An example:
# time host google.co.za
google.co.za has address 66.249.93.104
google.co.za has address 72.14.207.104
google.co.za has address 64.233.161.104
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
Do your own DNS. Your ISP chokes in ('IPv6') look ups. If you're not
allowed to, still run a local resolver with aggressive neg ttl caching.
See the numerous tutorials on the web on how to run your own resolver.
Well spotted. You are right that the ISP is choking on , except it is
returning SERVFAIL. I already have a local named running and acts as a
forwarder. Unfortunately I have to use the ISP to resolve names (it is the
only nameserver I have access to).
Google says bind won't cache SERVFAIL responces and I have no idea how to
disable named from forwarding requests.
signature.asc
Description: This is a digitally signed message part.
Re: Slow DNS (and host: connection timed out)
On Tuesday 10 February 2009 03:09:54 David Naylor wrote:
On Tuesday 10 February 2009 09:33:36 Mel wrote:
On Thursday 05 February 2009 22:55:56 David Naylor wrote:
Hi,
My ISP is using a WinGate DNS but resolving host names often takes a
long time. The problem is also present in Konqueror (3 4) and
Firefox.
An example:
# time host google.co.za
google.co.za has address 66.249.93.104
google.co.za has address 72.14.207.104
google.co.za has address 64.233.161.104
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
Do your own DNS. Your ISP chokes in ('IPv6') look ups. If you're not
allowed to, still run a local resolver with aggressive neg ttl caching.
See the numerous tutorials on the web on how to run your own resolver.
Well spotted. You are right that the ISP is choking on , except it is
returning SERVFAIL. I already have a local named running and acts as a
forwarder. Unfortunately I have to use the ISP to resolve names (it is the
only nameserver I have access to).
You cannot connect to an outside nameserver, due to ISP restrictions I take
it?
Google says bind won't cache SERVFAIL responces and I have no idea how to
disable named from forwarding requests.
Me neither. I battled with ISC about this before, but their position is that
ISP nameservers and loadbalancers should 'get with the program'.
Not everyone has this luxury but if your ISP has any competition in your area,
check them out.
I briefly looked into views but you don't seem to be able to select views
based on RRs. Firewall isn't really an option either, since you'd have to
inspect the UDP payload.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Slow DNS (and host: connection timed out)
On Thursday 05 February 2009 22:55:56 David Naylor wrote:
Hi,
My ISP is using a WinGate DNS but resolving host names often takes a long
time. The problem is also present in Konqueror (3 4) and Firefox.
An example:
# time host google.co.za
google.co.za has address 66.249.93.104
google.co.za has address 72.14.207.104
google.co.za has address 64.233.161.104
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
Do your own DNS. Your ISP chokes in ('IPv6') look ups. If you're not
allowed to, still run a local resolver with aggressive neg ttl caching.
See the numerous tutorials on the web on how to run your own resolver.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Slow DNS (and host: connection timed out)
David Naylor wrote: On Friday 06 February 2009 13:47:47 Lokadamus wrote: David Naylor wrote: I don't quite understand your question. See below for the network topology: ISP (host WinGate DNS, only proxy and socks connections allowed out) | Wireless connection to my gateway Server (My gateway, running bind9 for internet domain and DNS caching, FreeBSD 7.1p2) PCI D-Link GPlus wireless card for link to ISP PCI rl0 link to switch Ok, here is a realtek. That can sometimes make problems. Can you change this network interface card? Yes I could, however I have the same problem on the gateway over the wireless card. The wireless card is connecting the gateway to the ISP (i.e. gateway-wireless-ISP) with the ethernet to the intranet. I haven't had any problems with pinging the gateway from my laptop. Can you see problems of your wireless card in /var/log/messages? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Slow DNS (and host: connection timed out)
On Saturday 07 February 2009 17:34:02 Lokadamus wrote: David Naylor wrote: On Friday 06 February 2009 13:47:47 Lokadamus wrote: David Naylor wrote: I don't quite understand your question. See below for the network topology: ISP (host WinGate DNS, only proxy and socks connections allowed out) | Wireless connection to my gateway Server (My gateway, running bind9 for internet domain and DNS caching, FreeBSD 7.1p2) PCI D-Link GPlus wireless card for link to ISP PCI rl0 link to switch Ok, here is a realtek. That can sometimes make problems. Can you change this network interface card? Yes I could, however I have the same problem on the gateway over the wireless card. The wireless card is connecting the gateway to the ISP (i.e. gateway-wireless-ISP) with the ethernet to the intranet. I haven't had any problems with pinging the gateway from my laptop. Can you see problems of your wireless card in /var/log/messages? I do get some errors, here is a sample: # grep ndis0 /var/log/messages Feb 7 17:57:55 dgserver kernel: arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 Feb 7 18:03:25 dgserver kernel: arp: 192.168.0.1 is on lo0 but got reply from 00:02:6f:3e:8a:ed on ndis0 The MAC address is not an my network, as far as I can see. signature.asc Description: This is a digitally signed message part.
Re: Slow DNS (and host: connection timed out)
David Naylor wrote: Can you see problems of your wireless card in /var/log/messages? I do get some errors, here is a sample: # grep ndis0 /var/log/messages Feb 7 17:57:55 dgserver kernel: arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 Feb 7 18:03:25 dgserver kernel: arp: 192.168.0.1 is on lo0 but got reply from 00:02:6f:3e:8a:ed on ndis0 The MAC address is not an my network, as far as I can see. Can you give me a netstat -nr and a ifconfig? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Slow DNS (and host: connection timed out)
On Saturday 07 February 2009 18:58:40 you wrote: David Naylor wrote: Can you see problems of your wireless card in /var/log/messages? I do get some errors, here is a sample: # grep ndis0 /var/log/messages Feb 7 17:57:55 dgserver kernel: arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 Feb 7 18:03:25 dgserver kernel: arp: 192.168.0.1 is on lo0 but got reply from 00:02:6f:3e:8a:ed on ndis0 The MAC address is not an my network, as far as I can see. Can you give me a netstat -nr and a ifconfig? dgserver# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.193.194.1 UGS 0 830 ndis0 127.0.0.1 127.0.0.1 UH 0 254lo0 192.168.0.0/24 link#2 UC 00rl0 192.168.0.27e:2b:34:e8:eb:a2 UHLW12rl0618 192.168.0.300:a1:b0:a0:63:68 UHLW1 504rl0 1129 192.168.0.600:1d:72:1d:63:41 UHLW1 1734rl0 35 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 1 109rl0 192.193.194.0/24 link#1 UC 00 ndis0 192.193.194.1 00:02:6f:47:92:29 UHLW2 1941 ndis0 1199 Internet6: (removed, not used) dgserver# ifconfig ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:11:95:16:59:5d inet 192.193.194.58 netmask 0xff00 broadcast 192.193.194.255 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid QuickNet channel 1 (2412 Mhz 11b) bssid 00:02:6f:3e:13:cf authmode OPEN privacy OFF bmiss 7 scanvalid 60 rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8VLAN_MTU ether 00:13:f7:cb:2f:b9 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 dgserver# dmesg | grep 'rl0' rl0: RealTek 8139 10/100BaseTX port 0xf800-0xf8ff mem 0xfdffc000-0xfdffc0ff irq 11 at device 14.0 on pci0 miibus0: MII bus on rl0 dgserver# dmesg | grep 'ndis0' ndis0: D-Link AirPlus G+ DWL-G520+ Wireless PCI Adapter mem 0xfdffa000-0xfdffbfff,0xfdfc-0xfdfd irq 15 at device 13.0 on pci0 ndis0: [ITHREAD] ndis0: NDIS API version: 5.1 ndis0: WARNING: using obsoleted if_watchdog interface ndis0: Ethernet address: 00:11:95:16:59:5d ndis0: link state changed to UP (and both commands above have a common): arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 arp: 192.168.0.2 is on rl0 but got reply from 00:02:6f:3e:8a:ed on ndis0 signature.asc Description: This is a digitally signed message part.
Re: Slow DNS (and host: connection timed out)
David Naylor wrote: Hi, My ISP is using a WinGate DNS but resolving host names often takes a long time. The problem is also present in Konqueror (3 4) and Firefox. Lastly: # cat /etc/resolve.conf nameserver 192.193.194.1 What is wrong, why is DN resolving taking such an abnormally long time? How can I diagnose and fix it? Thanks in advance, 2 Questions: Which networccard is build in? Can you use another nameserver? An extern nameserver for testing? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Slow DNS (and host: connection timed out)
Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 192.168.0.6.55429 63.245.209.93.80 SYN_SENT tcp4 0 0 192.168.0.6.12337 74.125.77.147.80 SYN_SENT Firefox on Windows doesn't have this problem. it doesn't look like DNS problem as it's stuck on connecting to HTTP port (80). check out with ping if it's all fine with your netcard under FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Slow DNS (and host: connection timed out)
On Friday 06 February 2009 10:37:00 Lokadamus wrote: David Naylor wrote: Hi, My ISP is using a WinGate DNS but resolving host names often takes a long time. The problem is also present in Konqueror (3 4) and Firefox. Lastly: # cat /etc/resolve.conf nameserver 192.193.194.1 What is wrong, why is DN resolving taking such an abnormally long time? How can I diagnose and fix it? Thanks in advance, 2 Questions: Which networccard is build in? I don't quite understand your question. See below for the network topology: ISP (host WinGate DNS, only proxy and socks connections allowed out) | | Wireless connection to my gateway | Server (My gateway, running bind9 for internet domain and DNS caching, FreeBSD 7.1p2) PCI D-Link GPlus wireless card for link to ISP PCI rl0 link to switch | | Switch | My desktop (Client, FreeBSD 7.1p2, acts as bridge for laptop) PCI dc0 link to switch Built-in nfe0 link to laptop | My laptop (Client, FreeBSD 8.0) Built-in bge0 link to desktop All the FreeBSD systems (server, desktop and laptop) experience the DNS problem. Can you use another nameserver? An extern nameserver for testing? Other than the ISP's nameserver and my servers nameserver (which works fine for its master domain) no. Does this help? signature.asc Description: This is a digitally signed message part.
Re: Slow DNS (and host: connection timed out)
David Naylor wrote: I don't quite understand your question. See below for the network topology: ISP (host WinGate DNS, only proxy and socks connections allowed out) | | Wireless connection to my gateway | Server (My gateway, running bind9 for internet domain and DNS caching, FreeBSD 7.1p2) PCI D-Link GPlus wireless card for link to ISP PCI rl0 link to switch Ok, here is a realtek. That can sometimes make problems. Can you change this network interface card? | | Switch | My desktop (Client, FreeBSD 7.1p2, acts as bridge for laptop) PCI dc0 link to switch Built-in nfe0 link to laptop | My laptop (Client, FreeBSD 8.0) Built-in bge0 link to desktop All the FreeBSD systems (server, desktop and laptop) experience the DNS problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Slow DNS (and host: connection timed out)
Hi, I have similar problem, 3 servers in the same switch, the same configuration, but sending of e-mail from php takes very long time, but only on 2 servers with 7.1 amd64. On 6.2 (the same ip range, the same dns resolver, the same version of php, the same switch) no problem. Where could be a problem? Resolver? Interesting is that are moments when problem isnt on 7.1 too (but very rarely). I thing that is problem of version of FBSD but I havent any verification yet. Radek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Slow DNS (and host: connection timed out)
On Friday 06 February 2009 13:47:47 Lokadamus wrote: David Naylor wrote: I don't quite understand your question. See below for the network topology: ISP (host WinGate DNS, only proxy and socks connections allowed out) | Wireless connection to my gateway Server (My gateway, running bind9 for internet domain and DNS caching, FreeBSD 7.1p2) PCI D-Link GPlus wireless card for link to ISP PCI rl0 link to switch Ok, here is a realtek. That can sometimes make problems. Can you change this network interface card? Yes I could, however I have the same problem on the gateway over the wireless card. The wireless card is connecting the gateway to the ISP (i.e. gateway-wireless-ISP) with the ethernet to the intranet. I haven't had any problems with pinging the gateway from my laptop. | Switch My desktop (Client, FreeBSD 7.1p2, acts as bridge for laptop) PCI dc0 link to switch Built-in nfe0 link to laptop My laptop (Client, FreeBSD 8.0) Built-in bge0 link to desktop All the FreeBSD systems (server, desktop and laptop) experience the DNS problem. signature.asc Description: This is a digitally signed message part.
Re: Slow DNS (and host: connection timed out)
On Friday 06 February 2009 11:37:31 Wojciech Puchar wrote: Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 192.168.0.6.55429 63.245.209.93.80 SYN_SENT tcp4 0 0 192.168.0.6.12337 74.125.77.147.80 SYN_SENT Firefox on Windows doesn't have this problem. it doesn't look like DNS problem as it's stuck on connecting to HTTP port (80). check out with ping if it's all fine with your netcard under FreeBSD netcard works fine: (from laptop, see http://lists.freebsd.org/pipermail/freebsd-questions/2009-February/192278.html for layout of network) # ping -c 2000 -i 0.1 192.193.194.1 PING 192.193.194.1 (192.193.194.1): 56 data bytes 2000 packets transmitted, 1937 packets received, 3.1% packet loss round-trip min/avg/max/stddev = 3.339/27.799/741.743/78.702 ms The above was because only proxied (and socks) traffic is allowed beyond the ISP. The point I was trying to make was (by the number of '.' before the first netstat line) that it takes the browser over 25 seconds before it even attempts the connection. See below for when I have transparent proxying enabled (and the connection does go through). # konqueror www.google.co.za [1] 4862 # sh -c 'while true; do echo -n .; netstat -np tcp; sleep 5; done' Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 0 0 192.168.0.2.50707 74.125.77.99.80ESTABLISHED .Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 0 0 192.168.0.2.64852 74.125.77.99.80TIME_WAIT tcp4 0 0 192.168.0.2.50707 74.125.77.99.80TIME_WAIT Note that in this case it takes 35 seconds before Konqueror attempts the connection. Regards, signature.asc Description: This is a digitally signed message part.
Slow DNS (and host: connection timed out)
Hi, My ISP is using a WinGate DNS but resolving host names often takes a long time. The problem is also present in Konqueror (3 4) and Firefox. An example: # time host google.co.za google.co.za has address 66.249.93.104 google.co.za has address 72.14.207.104 google.co.za has address 64.233.161.104 ;; connection timed out; no servers could be reached ;; connection timed out; no servers could be reached 0.000u 0.008s 0:24.69 0.0% 0+0k 0+0io 0pf+0w The web browsers also take a long time before they actually try connecting. # konqueror www.google.co.za [1] 4862 # sh -c 'while true; do echo -n .; netstat -np tcp; sleep 5; done' ..Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 192.168.0.6.55429 63.245.209.93.80 SYN_SENT tcp4 0 0 192.168.0.6.12337 74.125.77.147.80 SYN_SENT .Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 192.168.0.6.55429 63.245.209.93.80 SYN_SENT tcp4 0 0 192.168.0.6.12337 74.125.77.147.80 SYN_SENT Firefox on Windows doesn't have this problem. Lastly: # cat /etc/resolve.conf nameserver 192.193.194.1 What is wrong, why is DN resolving taking such an abnormally long time? How can I diagnose and fix it? Thanks in advance, David System: # uname -a FreeBSD dragon.dg 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Sub Feb 1 20:27:42 SAST 2009 r...@dragon.dg:/tmp/tmp/src/sys/GENERIC i386 and # uname -a FreeBSD dragonmini.dg 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Dec 21 20:04:04 SAST 2008 r...@dragonmini.dg:/tmp/usr/src/sys/GENERIC amd64 signature.asc Description: This is a digitally signed message part.
RESOLVED: Connection timed out
Greg, Your email was very helpful. I isolated the freebsd box, and the win2K box on a LAN without connection to the upstream Cisco device, and all the connectivity problems went away. I'll be implementing the 'turn off STP' on those Cisco ports shortly. Many thanks, Matthew Greg Barniskis wrote: Matthew Pope wrote: I find that during the blocking behaviour, when I try and ping the windows box, a tcpdump shows that each second ping attempt is followed by a response (it appears) from an IPv6 address... 13:30:51.066625 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 13:30:53.069431 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 If you're referring to the above samples as appears from IPV6, those are Spanning Tree Protocol packets originating from the Cisco switch, and are unrelated to your ping test. You will see them on the wire frequently even in the absence of any normal IP traffic. You probably want the following Cisco configuration directive added to those switch ports that do not connect the 2900 to other switches: spanning-tree portfast The presence of the STP packets may or may not be related to your performance issues. They shouldn't be, but some buggy NICs/drivers do seem to get freaked out by STP. When STP is enabled on a switch port, it definitely will delay your initial link establishment by 30 seconds or so, when the attached computer is first powered up. That alone can confuse things when the NIC is trying to negotiate a link speed and the switch is still thinking about STP. It's even possible that you're getting a link speed/duplex mismatch out of it, and of course that will play holy hell with your response time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connection timed out
I find that during the blocking behaviour, when I try and ping the windows box, a tcpdump shows that each second ping attempt is followed by a response (it appears) from an IPv6 address (10.1.1.99 is the freebsd host): Virtual terminal 1: $ tcpdump tcpdump.out Virtual terminal 2: $ ping 10.1.1.173 [my win2K box, named mpworkstation] Virtual terminal 1: $ CTRL-C Virtual terminal 1: $ cat tcpdump.out 13:30:51.066625 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 13:30:53.069431 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 13:30:53.778918 IP 10.1.1.99 mpworkstation: ICMP echo request, id 25361, seq 0, length 64 13:30:54.712093 IP 10.1.1.99.domain blackhole-1.iana.org.domain: 39723 [1au] PTR? 99.1.1.10.in-addr.arpa. (51) 13:30:54.779708 IP 10.1.1.99 mpworkstation: ICMP echo request, id 25361, seq 1, length 64 13:30:54.803586 arp who-has 10.1.1.2 tell 10.1.1.119 13:30:54.840818 IP blackhole-1.iana.org.domain 10.1.1.99.domain: 39723 NXDomain* 0/1/1 (128) 13:30:55.072256 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 13:30:55.780687 IP 10.1.1.99 mpworkstation: ICMP echo request, id 25361, seq 2, length 64 13:30:55.841542 IP 10.1.1.99.domain blackhole-2.iana.org.domain: 1862 [1au] PTR? 2.1.1.10.in-addr.arpa. (50) 13:30:55.970699 IP blackhole-2.iana.org.domain 10.1.1.99.domain: 1862 NXDomain* 0/1/1 (127) 13:30:55.971365 IP 10.1.1.99.domain blackhole-1.iana.org.domain: 16894 [1au] PTR? 119.1.1.10.in-addr.arpa. (52) 13:30:56.099288 IP blackhole-1.iana.org.domain 10.1.1.99.domain: 16894 NXDomain* 0/1/1 (129) 13:30:56.781666 IP 10.1.1.99 mpworkstation: ICMP echo request, id 25361, seq 3, length 64 13:30:57.075128 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 13:30:57.778934 IP 192.168.1.108.netbios-dgm 192.168.1.255.netbios-dgm: NBT UDP PACKET(138) 13:30:57.779300 IP 10.1.1.108.netbios-dgm 10.1.1.255.netbios-dgm: NBT UDP PACKET(138) 13:30:57.782640 IP 10.1.1.99 mpworkstation: ICMP echo request, id 25361, seq 4, length 64 13:30:58.099166 IP 10.1.1.99.domain epazote.arin.net.domain: 41215 [1au] PTR? 255.1.168.192.in-addr.arpa. (55) 13:30:58.783615 IP 10.1.1.99 mpworkstation: ICMP echo request, id 25361, seq 5, length 64 13:30:59.077884 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 13:30:59.784593 IP 10.1.1.99 mpworkstation: ICMP echo request, id 25361, seq 6, length 64 13:31:00.099647 IP 10.1.1.99.domain c3.NSTLD.COM.domain: 18950 [1au] PTR? 255.1.168.192.in-addr.arpa. (55) 13:31:00.174654 IP c3.NSTLD.COM.domain 10.1.1.99.domain: 18950- 0/2/1 (115) 13:31:00.174865 IP 10.1.1.99.domain blackhole-2.iana.org.domain: 21147 [1au] PTR? 255.1.168.192.in-addr.arpa. (55) 13:31:00.302542 IP blackhole-2.iana.org.domain 10.1.1.99.domain: 21147 NXDomain* 0/1/1 (132) 13:31:00.303203 IP 10.1.1.99.domain blackhole-1.iana.org.domain: 15742 [1au] PTR? 108.1.168.192.in-addr.arpa. (55) 13:31:00.424762 IP blackhole-1.iana.org.domain 10.1.1.99.domain: 15742 NXDomain* 0/1/1 (132) 13:31:00.425485 IP 10.1.1.99.domain blackhole-2.iana.org.domain: 36677 [1au] PTR? 255.1.1.10.in-addr.arpa. (52) 13:31:00.539310 IP blackhole-2.iana.org.domain 10.1.1.99.domain: 36677 NXDomain* 0/1/1 (129) 13:31:00.539955 IP 10.1.1.99.domain blackhole-1.iana.org.domain: 34458 [1au] PTR? 108.1.1.10.in-addr.arpa. (52) 13:31:00.653398 IP blackhole-1.iana.org.domain 10.1.1.99.domain: 34458 NXDomain* 0/1/1 (129) 13:31:00.785569 IP 10.1.1.99 mpworkstation: ICMP echo request, id 25361, seq 7, length 64 13:31:01.081370 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 Lowell Gilbert wrote: Matthew Pope [EMAIL PROTECTED] writes: I am trying to resolve a connection timed out problem. The problem occurs when I attempt to ssh, or http to my freebsd host from my windows (2K) box. About 3/4 of the time I get a Connection timed out when I attempt to ssh into the freebsd host. Coincident with this behaviour, I can not ping my windows box from the freebsd host, and when I try I get no packets returned. Meanwhile, the freebsd box at no time has any problems pinging google, only the local network. I recall having a sockets timeout variable or something that needed tuning when I ran freebsd as a http / ssh server before . Can someone provide a hint as to how I can resolve this? Thanks, Matthew -bash-2.05b$ uname -a FreeBSD ns.mbpesecurity.com 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: Mon Oct 23 00:47:22 EDT 2006 [EMAIL PROTECTED] urity.com:/usr/obj/usr/src/sys/MPKERNEL i386 Does the FreeBSD box access the Internet through the same link as it reaches the Windows machine? [I'm
Re: Connection timed out
Matthew Pope wrote: I find that during the blocking behaviour, when I try and ping the windows box, a tcpdump shows that each second ping attempt is followed by a response (it appears) from an IPv6 address... 13:30:51.066625 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 13:30:53.069431 802.1d config 8000.00:30:19:53:05:00.8011 root 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 If you're referring to the above samples as appears from IPV6, those are Spanning Tree Protocol packets originating from the Cisco switch, and are unrelated to your ping test. You will see them on the wire frequently even in the absence of any normal IP traffic. You probably want the following Cisco configuration directive added to those switch ports that do not connect the 2900 to other switches: spanning-tree portfast The presence of the STP packets may or may not be related to your performance issues. They shouldn't be, but some buggy NICs/drivers do seem to get freaked out by STP. When STP is enabled on a switch port, it definitely will delay your initial link establishment by 30 seconds or so, when the attached computer is first powered up. That alone can confuse things when the NIC is trying to negotiate a link speed and the switch is still thinking about STP. It's even possible that you're getting a link speed/duplex mismatch out of it, and of course that will play holy hell with your response time. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connection timed out
Matthew Pope [EMAIL PROTECTED] writes: I am trying to resolve a connection timed out problem. The problem occurs when I attempt to ssh, or http to my freebsd host from my windows (2K) box. About 3/4 of the time I get a Connection timed out when I attempt to ssh into the freebsd host. Coincident with this behaviour, I can not ping my windows box from the freebsd host, and when I try I get no packets returned. Meanwhile, the freebsd box at no time has any problems pinging google, only the local network. I recall having a sockets timeout variable or something that needed tuning when I ran freebsd as a http / ssh server before . Can someone provide a hint as to how I can resolve this? Thanks, Matthew -bash-2.05b$ uname -a FreeBSD ns.mbpesecurity.com 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: Mon Oct 23 00:47:22 EDT 2006 [EMAIL PROTECTED] urity.com:/usr/obj/usr/src/sys/MPKERNEL i386 Does the FreeBSD box access the Internet through the same link as it reaches the Windows machine? [I'm guessing not, but you didn't say.] Is there anything in the logs or on the console? Does the link light stay on for the FreeBSD machine? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Connection timed out
Hello, I am trying to resolve a connection timed out problem. The problem occurs when I attempt to ssh, or http to my freebsd host from my windows (2K) box. About 3/4 of the time I get a Connection timed out when I attempt to ssh into the freebsd host. Coincident with this behaviour, I can not ping my windows box from the freebsd host, and when I try I get no packets returned. Meanwhile, the freebsd box at no time has any problems pinging google, only the local network. I recall having a sockets timeout variable or something that needed tuning when I ran freebsd as a http / ssh server before . Can someone provide a hint as to how I can resolve this? Thanks, Matthew -bash-2.05b$ uname -a FreeBSD ns.mbpesecurity.com 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: Mon Oct 23 00:47:22 EDT 2006 [EMAIL PROTECTED] urity.com:/usr/obj/usr/src/sys/MPKERNEL i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ssh connection timed out
Hi I've just installed FreeBSD4.5 on machine attached to a college network. I can connect to the machine using ssh from another machine on the network. When I try to connect using ssh from home via an ISP (using PuTTY on winxp) I get connection timed out. I can connect from home using telnet though... which makes me guess its a problem with the sshd configuration. output from uname -a: FreeBSD .ucd.ie 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Mon Jan 28 14:31:56 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 TIA, Goodwin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ssh connection timed out
Thanks for the suggestions -sshd isn't wrapped in hosts.allow -tried both IP address and name -upped LoginGraceTime from 120 to 500 (ISDN dialup ISP) I'll mail sysadmin and see if ssh is allowed from outside the network. Did you mean portscan the network gateway... I'll see what sysadmin say first Thanks Goodwin - Original Message - From: Kevin D. Kinsey, DaleCo, S.P. [EMAIL PROTECTED] To: Goodwin Lawlor [EMAIL PROTECTED]; FreeBSD List [EMAIL PROTECTED] Sent: Thursday, October 10, 2002 8:10 PM Subject: Re: ssh connection timed out Any number of possibilities...I'm not sure from what you've given. If you have more detail, it might help... 1. You didn't wrap sshd in /etc/hosts.allow, did you? I doubt it, that would twist a message to /bin/echo you're not allowed. 2. Have your tried both by IP addy and name? DNS issue? 3. Seems quite likely that the college sys admins are firewalling the WAN connection. Ask them if you are allowed to use SSH from outside. Or, if you're feeling anti-establishment today, portscan them and see if #22 is open, ;-) However, seems strange they'd filter SSH and leave ol' insecure telnet open h. 4. It takes longer to connect and set up a tunnel, are you on a dial up ISP? Check things like LoginGraceTime in /etc/ssh/sshd_config. I'm sure there are better men out there than I. I use putty on WinXP all the time, however, and time outs are very rare. Kevin Kinsey DaleCo, S.P. - Original Message - From: Goodwin Lawlor [EMAIL PROTECTED] To: FreeBSD List [EMAIL PROTECTED] Sent: Thursday, October 10, 2002 1:41 PM Subject: ssh connection timed out Hi I've just installed FreeBSD4.5 on machine attached to a college network. I can connect to the machine using ssh from another machine on the network. When I try to connect using ssh from home via an ISP (using PuTTY on winxp) I get connection timed out. I can connect from home using telnet though... which makes me guess its a problem with the sshd configuration. output from uname -a: FreeBSD .ucd.ie 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Mon Jan 28 14:31:56 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 TIA, Goodwin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
