RE: Urgent 4.9 networking problems
Okay thank you I've been so confused with all this that it didn't even occur to me - its now responding as expected - but I still have my original TCP problem.. It takes EXTREMELY long to send the first SYN, once its done that the entire session is perfect... Anyone at all? Any suggestions on further tests? Thanks again Dave -Original Message- From: Gordon Freeman [mailto:[EMAIL PROTECTED] Sent: 24 June 2004 11:09 PM To: Dave Raven Subject: Re: Urgent 4.9 networking problems try ping -nR -c1 x.y.186.254 If you don't get the same lag then it is your DNS lookup that is causing the problem. On Thu, 24 Jun 2004 22:54:10 +0200, Dave Raven [EMAIL PROTECTED] wrote: Hi all, I really need some urgent help with this I'm completely confused. I have a FreeBSD 4.9 machine running ipfilter ipnat vrrp and a few other services, today is the first time I tried to access through the specific method but now every interface and every local address I try has the same problem. I can ping anything - but any other kind of traffic waits for about 2 minutes before transmitting - this is true with tcp and udp. I'm trying to access machines on the same network - and if I ping -R you can see the same effect - pasted below. I've also included the interface that I'm trying to do this on although it seems to be happening on all my other interfaces.. I try to telnet to a cisco router that's on a switch I'm plugged in and I see the same behaviour - it just waits then suddenly responds very quickly. My IpFilter rules don't log anything until it responds at which time they pass it - and tethereal + tcpdump also see if perfectly AFTER the long delay. It appears that its sitting on the kernel for 2 minutes??? It just does NOTHING then all of a sudden responds. The only thing I can find that works is icmp - and perfectly. I'm sorry for the urgency but its very high priority Thanks in advance Dave # ifconfig fxp1 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet x.y.186.3 netmask 0xff00 broadcast x.y.186.255 inet x.y.186.1 netmask 0x broadcast x.y.186.1 inet x.y.186.15 netmask 0x broadcast x.y.186.15 inet x.y.186.14 netmask 0x broadcast x.y.186.14 inet x.y.186.142 netmask 0x broadcast x.y.186.142 inet x.y.186.33 netmask 0x broadcast x.y.186.33 inet x.y.186.124 netmask 0x broadcast x.y.186.124 inet x.y.186.250 netmask 0x broadcast x.y.186.250 inet x.y.186.122 netmask 0x broadcast x.y.186.122 inet x.y.186.25 netmask 0x broadcast x.y.186.25 inet x.y.186.127 netmask 0x broadcast x.y.186.127 # date ; ping -R -c1 x.y.186.253 ; date Thu Jun 24 22:43:13 SAST 2004 PING x.y.186.253 (152.110.186.253): 56 data bytes 64 bytes from x.y.186.253: icmp_seq=0 ttl=255 time=0.414 ms RR: x.y.186.253 x.y.186.253 x.y.186.3 --- x.y.186.253 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.414/0.414/0.414/0.000 ms Thu Jun 24 22:46:58 SAST 2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Urgent 4.9 networking problems
Dave Raven [EMAIL PROTECTED] wrote: Okay thank you I've been so confused with all this that it didn't even occur to me - its now responding as expected - but I still have my original TCP problem.. It takes EXTREMELY long to send the first SYN, once its done that the entire session is perfect... Anyone at all? Any suggestions on further tests? Are you sure all your problems aren't caused by DNS delays? Most TCP servers will do a reverse lookup on the client attempting to connect, so they have a friendly name to put in their log. If there is no DNS configured for that machine, they'll wait for a fixed timeout before giving up and just logging the IP addy. Try creating PTR records for all these machines and see if that fixes it. Or, just create a zone file for those IPs with no records ... at least that will result in an immediate negative response from the DNS server, which should avoid the delay. Thanks again Dave -Original Message- From: Gordon Freeman [mailto:[EMAIL PROTECTED] Sent: 24 June 2004 11:09 PM To: Dave Raven Subject: Re: Urgent 4.9 networking problems try ping -nR -c1 x.y.186.254 If you don't get the same lag then it is your DNS lookup that is causing the problem. On Thu, 24 Jun 2004 22:54:10 +0200, Dave Raven [EMAIL PROTECTED] wrote: Hi all, I really need some urgent help with this I'm completely confused. I have a FreeBSD 4.9 machine running ipfilter ipnat vrrp and a few other services, today is the first time I tried to access through the specific method but now every interface and every local address I try has the same problem. I can ping anything - but any other kind of traffic waits for about 2 minutes before transmitting - this is true with tcp and udp. I'm trying to access machines on the same network - and if I ping -R you can see the same effect - pasted below. I've also included the interface that I'm trying to do this on although it seems to be happening on all my other interfaces.. I try to telnet to a cisco router that's on a switch I'm plugged in and I see the same behaviour - it just waits then suddenly responds very quickly. My IpFilter rules don't log anything until it responds at which time they pass it - and tethereal + tcpdump also see if perfectly AFTER the long delay. It appears that its sitting on the kernel for 2 minutes??? It just does NOTHING then all of a sudden responds. The only thing I can find that works is icmp - and perfectly. I'm sorry for the urgency but its very high priority Thanks in advance Dave # ifconfig fxp1 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet x.y.186.3 netmask 0xff00 broadcast x.y.186.255 inet x.y.186.1 netmask 0x broadcast x.y.186.1 inet x.y.186.15 netmask 0x broadcast x.y.186.15 inet x.y.186.14 netmask 0x broadcast x.y.186.14 inet x.y.186.142 netmask 0x broadcast x.y.186.142 inet x.y.186.33 netmask 0x broadcast x.y.186.33 inet x.y.186.124 netmask 0x broadcast x.y.186.124 inet x.y.186.250 netmask 0x broadcast x.y.186.250 inet x.y.186.122 netmask 0x broadcast x.y.186.122 inet x.y.186.25 netmask 0x broadcast x.y.186.25 inet x.y.186.127 netmask 0x broadcast x.y.186.127 # date ; ping -R -c1 x.y.186.253 ; date Thu Jun 24 22:43:13 SAST 2004 PING x.y.186.253 (152.110.186.253): 56 data bytes 64 bytes from x.y.186.253: icmp_seq=0 ttl=255 time=0.414 ms RR: x.y.186.253 x.y.186.253 x.y.186.3 --- x.y.186.253 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.414/0.414/0.414/0.000 ms Thu Jun 24 22:46:58 SAST 2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Urgent 4.9 networking problems
Your symptoms are typical of DNS time outs. Ping ip address does no DNS lookups. Ping freebsd.org will not work either. With out a lot more detail about your network environment, the best I can say is look at how your network resolves DNS lookups. Some times a ISP will change the ip address of their DNS or DHCP servers and if you have their ip address hard coded in your firewall rules your network will just stop talking to the public internet. Start your research there. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dave Raven Sent: Thursday, June 24, 2004 4:54 PM To: [EMAIL PROTECTED] Subject: Urgent 4.9 networking problems Hi all, I really need some urgent help with this I'm completely confused. I have a FreeBSD 4.9 machine running ipfilter ipnat vrrp and a few other services, today is the first time I tried to access through the specific method but now every interface and every local address I try has the same problem. I can ping anything - but any other kind of traffic waits for about 2 minutes before transmitting - this is true with tcp and udp. I'm trying to access machines on the same network - and if I ping -R you can see the same effect - pasted below. I've also included the interface that I'm trying to do this on although it seems to be happening on all my other interfaces.. I try to telnet to a cisco router that's on a switch I'm plugged in and I see the same behaviour - it just waits then suddenly responds very quickly. My IpFilter rules don't log anything until it responds at which time they pass it - and tethereal + tcpdump also see if perfectly AFTER the long delay. It appears that its sitting on the kernel for 2 minutes??? It just does NOTHING then all of a sudden responds. The only thing I can find that works is icmp - and perfectly. I'm sorry for the urgency but its very high priority Thanks in advance Dave # ifconfig fxp1 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet x.y.186.3 netmask 0xff00 broadcast x.y.186.255 inet x.y.186.1 netmask 0x broadcast x.y.186.1 inet x.y.186.15 netmask 0x broadcast x.y.186.15 inet x.y.186.14 netmask 0x broadcast x.y.186.14 inet x.y.186.142 netmask 0x broadcast x.y.186.142 inet x.y.186.33 netmask 0x broadcast x.y.186.33 inet x.y.186.124 netmask 0x broadcast x.y.186.124 inet x.y.186.250 netmask 0x broadcast x.y.186.250 inet x.y.186.122 netmask 0x broadcast x.y.186.122 inet x.y.186.25 netmask 0x broadcast x.y.186.25 inet x.y.186.127 netmask 0x broadcast x.y.186.127 # date ; ping -R -c1 x.y.186.253 ; date Thu Jun 24 22:43:13 SAST 2004 PING x.y.186.253 (152.110.186.253): 56 data bytes 64 bytes from x.y.186.253: icmp_seq=0 ttl=255 time=0.414 ms RR: x.y.186.253 x.y.186.253 x.y.186.3 --- x.y.186.253 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.414/0.414/0.414/0.000 ms Thu Jun 24 22:46:58 SAST 2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Urgent 4.9 networking problems
I have made further progress - thanks for all your steady replies. I know it might look like I haven't looked into it enough but this is just part of my bigger problem - here we go.. By adding my routers ip and my local machines ip to hosts, I've fixed the telnet to the router and the ping -R - but why is telnet timing out ?? I have NO DNS at all - there is nothing in resolv.conf yet it still makes requests to local host. I have to disable dns. I have no idea why it would sit for 2 minutes trying to resolve the ip for my telnet though??? Is this a problem? How do I stop dns altogether... The machine is acting as a firewall with NAT'ing and routing. The real problem that's gotten me down to here is with IPNat though - it says its map'd the address but in actual fact freebsd forwards it. Could this all be a red herring as a dns problem? Thanks Dave -Original Message- From: JJB [mailto:[EMAIL PROTECTED] Sent: 24 June 2004 11:23 PM To: Dave Raven; [EMAIL PROTECTED] Subject: RE: Urgent 4.9 networking problems Your symptoms are typical of DNS time outs. Ping ip address does no DNS lookups. Ping freebsd.org will not work either. With out a lot more detail about your network environment, the best I can say is look at how your network resolves DNS lookups. Some times a ISP will change the ip address of their DNS or DHCP servers and if you have their ip address hard coded in your firewall rules your network will just stop talking to the public internet. Start your research there. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dave Raven Sent: Thursday, June 24, 2004 4:54 PM To: [EMAIL PROTECTED] Subject: Urgent 4.9 networking problems Hi all, I really need some urgent help with this I'm completely confused. I have a FreeBSD 4.9 machine running ipfilter ipnat vrrp and a few other services, today is the first time I tried to access through the specific method but now every interface and every local address I try has the same problem. I can ping anything - but any other kind of traffic waits for about 2 minutes before transmitting - this is true with tcp and udp. I'm trying to access machines on the same network - and if I ping -R you can see the same effect - pasted below. I've also included the interface that I'm trying to do this on although it seems to be happening on all my other interfaces.. I try to telnet to a cisco router that's on a switch I'm plugged in and I see the same behaviour - it just waits then suddenly responds very quickly. My IpFilter rules don't log anything until it responds at which time they pass it - and tethereal + tcpdump also see if perfectly AFTER the long delay. It appears that its sitting on the kernel for 2 minutes??? It just does NOTHING then all of a sudden responds. The only thing I can find that works is icmp - and perfectly. I'm sorry for the urgency but its very high priority Thanks in advance Dave # ifconfig fxp1 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet x.y.186.3 netmask 0xff00 broadcast x.y.186.255 inet x.y.186.1 netmask 0x broadcast x.y.186.1 inet x.y.186.15 netmask 0x broadcast x.y.186.15 inet x.y.186.14 netmask 0x broadcast x.y.186.14 inet x.y.186.142 netmask 0x broadcast x.y.186.142 inet x.y.186.33 netmask 0x broadcast x.y.186.33 inet x.y.186.124 netmask 0x broadcast x.y.186.124 inet x.y.186.250 netmask 0x broadcast x.y.186.250 inet x.y.186.122 netmask 0x broadcast x.y.186.122 inet x.y.186.25 netmask 0x broadcast x.y.186.25 inet x.y.186.127 netmask 0x broadcast x.y.186.127 # date ; ping -R -c1 x.y.186.253 ; date Thu Jun 24 22:43:13 SAST 2004 PING x.y.186.253 (152.110.186.253): 56 data bytes 64 bytes from x.y.186.253: icmp_seq=0 ttl=255 time=0.414 ms RR: x.y.186.253 x.y.186.253 x.y.186.3 --- x.y.186.253 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.414/0.414/0.414/0.000 ms Thu Jun 24 22:46:58 SAST 2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Urgent 4.9 networking problems
On Thu, 24 Jun 2004, Dave Raven wrote: # ifconfig fxp1 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet x.y.186.3 netmask 0xff00 broadcast x.y.186.255 inet x.y.186.1 netmask 0x broadcast x.y.186.1 inet x.y.186.15 netmask 0x broadcast x.y.186.15 inet x.y.186.14 netmask 0x broadcast x.y.186.14 inet x.y.186.142 netmask 0x broadcast x.y.186.142 inet x.y.186.33 netmask 0x broadcast x.y.186.33 inet x.y.186.124 netmask 0x broadcast x.y.186.124 inet x.y.186.250 netmask 0x broadcast x.y.186.250 inet x.y.186.122 netmask 0x broadcast x.y.186.122 inet x.y.186.25 netmask 0x broadcast x.y.186.25 inet x.y.186.127 netmask 0x broadcast x.y.186.127 I don't disagree with the other posters that mentioned DNS timeouts, but in addition those broadcast addresses aren't right. Since all the addresses are within the same /24 subnet, they should all be .255 (which is the default, so you wouldn't need to specify them. KeS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Urgent 4.9 networking problems
The original ip 186.3 sets the broadcast - any aliases after that must have a /32 broadcast as they are aliases... That's correct isn't it (rest of list) ? Also - my connection is from 186.3 anyway, and those ip's are all functioning correctly.. I don't think that's where the problem is Thanks Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Stevens Sent: 24 June 2004 11:32 PM To: Dave Raven Cc: [EMAIL PROTECTED] Subject: Re: Urgent 4.9 networking problems On Thu, 24 Jun 2004, Dave Raven wrote: # ifconfig fxp1 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet x.y.186.3 netmask 0xff00 broadcast x.y.186.255 inet x.y.186.1 netmask 0x broadcast x.y.186.1 inet x.y.186.15 netmask 0x broadcast x.y.186.15 inet x.y.186.14 netmask 0x broadcast x.y.186.14 inet x.y.186.142 netmask 0x broadcast x.y.186.142 inet x.y.186.33 netmask 0x broadcast x.y.186.33 inet x.y.186.124 netmask 0x broadcast x.y.186.124 inet x.y.186.250 netmask 0x broadcast x.y.186.250 inet x.y.186.122 netmask 0x broadcast x.y.186.122 inet x.y.186.25 netmask 0x broadcast x.y.186.25 inet x.y.186.127 netmask 0x broadcast x.y.186.127 I don't disagree with the other posters that mentioned DNS timeouts, but in addition those broadcast addresses aren't right. Since all the addresses are within the same /24 subnet, they should all be .255 (which is the default, so you wouldn't need to specify them. KeS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Urgent 4.9 networking problems
On Thu, 24 Jun 2004, Dave Raven wrote: The original ip 186.3 sets the broadcast - any aliases after that must have a /32 broadcast as they are aliases... That's correct isn't it (rest of list) ? I don't believe so - it's the netmask which needs to be /32, which you did correctly. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-virtual-hosts.html KeS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Urgent 4.9 networking problems
Post your ipf rules and ipnat rules and /etc/resolv.conf resolv.conf should have your isp's dns server names. If not then post rc.conf also. Give interface name of Nic card connected to public internet. Has this network ever functioned correctly or is it something you are just putting together now? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dave Raven Sent: Thursday, June 24, 2004 5:29 PM To: [EMAIL PROTECTED] Subject: RE: Urgent 4.9 networking problems I have made further progress - thanks for all your steady replies. I know it might look like I haven't looked into it enough but this is just part of my bigger problem - here we go.. By adding my routers ip and my local machines ip to hosts, I've fixed the telnet to the router and the ping -R - but why is telnet timing out ?? I have NO DNS at all - there is nothing in resolv.conf yet it still makes requests to local host. I have to disable dns. I have no idea why it would sit for 2 minutes trying to resolve the ip for my telnet though??? Is this a problem? How do I stop dns altogether... The machine is acting as a firewall with NAT'ing and routing. The real problem that's gotten me down to here is with IPNat though - it says its map'd the address but in actual fact freebsd forwards it. Could this all be a red herring as a dns problem? Thanks Dave -Original Message- From: JJB [mailto:[EMAIL PROTECTED] Sent: 24 June 2004 11:23 PM To: Dave Raven; [EMAIL PROTECTED] Subject: RE: Urgent 4.9 networking problems Your symptoms are typical of DNS time outs. Ping ip address does no DNS lookups. Ping freebsd.org will not work either. With out a lot more detail about your network environment, the best I can say is look at how your network resolves DNS lookups. Some times a ISP will change the ip address of their DNS or DHCP servers and if you have their ip address hard coded in your firewall rules your network will just stop talking to the public internet. Start your research there. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dave Raven Sent: Thursday, June 24, 2004 4:54 PM To: [EMAIL PROTECTED] Subject: Urgent 4.9 networking problems Hi all, I really need some urgent help with this I'm completely confused. I have a FreeBSD 4.9 machine running ipfilter ipnat vrrp and a few other services, today is the first time I tried to access through the specific method but now every interface and every local address I try has the same problem. I can ping anything - but any other kind of traffic waits for about 2 minutes before transmitting - this is true with tcp and udp. I'm trying to access machines on the same network - and if I ping -R you can see the same effect - pasted below. I've also included the interface that I'm trying to do this on although it seems to be happening on all my other interfaces.. I try to telnet to a cisco router that's on a switch I'm plugged in and I see the same behaviour - it just waits then suddenly responds very quickly. My IpFilter rules don't log anything until it responds at which time they pass it - and tethereal + tcpdump also see if perfectly AFTER the long delay. It appears that its sitting on the kernel for 2 minutes??? It just does NOTHING then all of a sudden responds. The only thing I can find that works is icmp - and perfectly. I'm sorry for the urgency but its very high priority Thanks in advance Dave # ifconfig fxp1 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet x.y.186.3 netmask 0xff00 broadcast x.y.186.255 inet x.y.186.1 netmask 0x broadcast x.y.186.1 inet x.y.186.15 netmask 0x broadcast x.y.186.15 inet x.y.186.14 netmask 0x broadcast x.y.186.14 inet x.y.186.142 netmask 0x broadcast x.y.186.142 inet x.y.186.33 netmask 0x broadcast x.y.186.33 inet x.y.186.124 netmask 0x broadcast x.y.186.124 inet x.y.186.250 netmask 0x broadcast x.y.186.250 inet x.y.186.122 netmask 0x broadcast x.y.186.122 inet x.y.186.25 netmask 0x broadcast x.y.186.25 inet x.y.186.127 netmask 0x broadcast x.y.186.127 # date ; ping -R -c1 x.y.186.253 ; date Thu Jun 24 22:43:13 SAST 2004 PING x.y.186.253 (152.110.186.253): 56 data bytes 64 bytes from x.y.186.253: icmp_seq=0 ttl=255 time=0.414 ms RR: x.y.186.253 x.y.186.253 x.y.186.3 --- x.y.186.253 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.414/0.414/0.414/0.000 ms Thu Jun 24 22:46:58 SAST 2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd
Re: Urgent 4.9 networking problems
On Thu, Jun 24, 2004 at 02:31:58PM -0700, Kevin Stevens wrote: On Thu, 24 Jun 2004, Dave Raven wrote: # ifconfig fxp1 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet x.y.186.3 netmask 0xff00 broadcast x.y.186.255 inet x.y.186.1 netmask 0x broadcast x.y.186.1 inet x.y.186.15 netmask 0x broadcast x.y.186.15 inet x.y.186.14 netmask 0x broadcast x.y.186.14 inet x.y.186.142 netmask 0x broadcast x.y.186.142 inet x.y.186.33 netmask 0x broadcast x.y.186.33 inet x.y.186.124 netmask 0x broadcast x.y.186.124 inet x.y.186.250 netmask 0x broadcast x.y.186.250 inet x.y.186.122 netmask 0x broadcast x.y.186.122 inet x.y.186.25 netmask 0x broadcast x.y.186.25 inet x.y.186.127 netmask 0x broadcast x.y.186.127 I don't disagree with the other posters that mentioned DNS timeouts, but in addition those broadcast addresses aren't right. Since all the addresses are within the same /24 subnet, they should all be .255 (which is the default, so you wouldn't need to specify them. Err -- no. The broadcast address is a function of the netmask. Specifically, looking at IPv4 addresses/masks as 32bit integers, the broadcast address has all ones where ever the netmask has zeros. The OP actually has it right. Especially as that is clearly the slightly edited output from ifconfig(8), and ifconfig automatically calculates the broadcast address from the inet address and netmask. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpkTVrVEgmH0.pgp Description: PGP signature
Re: Urgent 4.9 networking problems
On Thu, 24 Jun 2004, Matthew Seaman wrote: On Thu, Jun 24, 2004 at 02:31:58PM -0700, Kevin Stevens wrote: Err -- no. The broadcast address is a function of the netmask. Specifically, looking at IPv4 addresses/masks as 32bit integers, the broadcast address has all ones where ever the netmask has zeros. The OP actually has it right. Especially as that is clearly the slightly edited output from ifconfig(8), and ifconfig automatically calculates the broadcast address from the inet address and netmask. Ok, tested, my bad. Sorry for any confusion. KeS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Urgent 4.9 networking problems
Dave Raven [EMAIL PROTECTED] wrote: I think I can solve the problem with the BIMAP - I'm just interested in finding out why it has to wait to resolve the host name when I'm telnetting directly to an ip address and I have no nameservers specified? Surely that can't be the way it has to be... Whether or not this happens will be a function of your telnet server _and_ the telnet client. It's not unusual to do both forward and a reverse lookup in DNS ... the reasons are mainly 1) to have something human readible in the logs (IP addresses aren't really human-readible compared to domain names) and 2) to ensure that you're not being tricked by some sort of DNS spoofing. While it's probably possible to disable DNS completely, that would be rather like disabling the turn signals on your car. It defeats a lot of what the rules of the highway were designed for. Much like you don't understand why you have to use DNS, I can't understand why you're rebelling against it so much. Are you saying that there are _no_ DNS servers on this network for you to plug into? If you insist on not using any DNS, I can all but guarantee that you will have weird timeouts to track down for the rest of eternety on this network. Most IP programs rely on DNS to some degree. Some of them will be able to be configured to skip DNS checks, and some will not, or will be difficult to convince to ignore DNS. I temporarily removed /etc/resolv.conf on my desktop machine, and it caused DNS queries to fail instantly when I tried to use ping. I can't say that all programs will react that way, but based on that, it doesn't seem like FreeBSD's telnet would be timing out on DNS lookups. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
