RE: network issue

2003-02-13 Thread Eric Six
What is your default gateway and subnet mask for your lan?

Cheers,
Eric Six

-Original Message-
From: Brian Henning [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 11:37 AM
To: freebsd
Subject: network issue


My local network (192.168.1.0) consists of two machine BSD1 (192.168.1.40)
and
BSD2 (192.168.1.42).
There is a third machine (192.168.1.254, ip address from isp) that acts as a
gateway router. When my internet connection goes down for whatever reason I
loose connections in my local network. For example, i can't ping
192.168.1.40
from 192.168.1.42. is there any explaination for this? is it because my
default
route is set to be external?

Thanks,

Brian

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue

2003-02-13 Thread Bill Moran
Brian Henning wrote:

My local network (192.168.1.0) consists of two machine BSD1 (192.168.1.40) and
BSD2 (192.168.1.42).
There is a third machine (192.168.1.254, ip address from isp) that acts as a
gateway router. When my internet connection goes down for whatever reason I
loose connections in my local network. For example, i can't ping 192.168.1.40
from 192.168.1.42. is there any explaination for this?


Can you give more details about the topology?  Does the gateway have 2 NICs?
I assume there's a hub on the inside?  Please post the output from ifconfig
on the gateway machine.


is it because my default
route is set to be external?


No, that doesn't normally cause problems to a local network.  When our Internet
goes down it doesn't affect internal traffic in the slightest. This is a rather
strange problem.

--
Bill Moran
Potential Technologies
http://www.potentialtech.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue

2003-02-13 Thread Nathan Kinkade
On Thu, Feb 13, 2003 at 11:36:47AM -0600, Brian Henning wrote:
 My local network (192.168.1.0) consists of two machine BSD1 (192.168.1.40) and
 BSD2 (192.168.1.42).
 There is a third machine (192.168.1.254, ip address from isp) that acts as a
 gateway router. When my internet connection goes down for whatever reason I
 loose connections in my local network. For example, i can't ping 192.168.1.40
 from 192.168.1.42. is there any explaination for this? is it because my default
 route is set to be external?
 
 Thanks,
 
 Brian

Are your two local machines simply connected by a hub/switch, or is
there some other setup?  What does your routing table look like - output
of `netstat -rn`.  Is there an entry that looks something like:
192.168.1link#1 UC  30   eth0

nathan

-- 
GPG Public Key ID: 0x4250A04C
gpg --keyserver pgp.mit.edu --recv-keys 4250A04C
http://63.105.21.156/gpg_nkinkade_4250A04C.asc



msg19271/pgp0.pgp
Description: PGP signature


Re: network issue

2003-02-13 Thread Scott A. Moberly

 My local network (192.168.1.0) consists of two machine BSD1
 (192.168.1.40) and BSD2 (192.168.1.42).
 There is a third machine (192.168.1.254, ip address from isp) that acts
 as a gateway router. When my internet connection goes down for whatever
 reason I loose connections in my local network. For example, i can't
 ping 192.168.1.40 from 192.168.1.42. is there any explaination for this?
 is it because my default route is set to be external?

yup

might consider setting one (say bsd1) up as a firewall/natd machine and
then routing through that.  Adds expandability (and security of course :)
).

-- 
Scott A. Moberly
[EMAIL PROTECTED]

Turner's Definition
A fine is a tax for doing wrong.
A tax is a fine for doing well.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue revisited

2003-02-13 Thread Bill Moran
Brian Henning wrote:

Let me try again, here is my situation and question with a little more detail.

My local network (192.168.1.0) consists of two machine BSD1 (192.168.1.40) and

BSD2 (192.168.1.42). Both of these machines use the subnet mask 255.255.255.0
and gateway 192.168.1.254.

There is a third machine GATEWAY (192.168.1.254, ip address from isp) has two
nics and acts as the router.

All of these machine are connected to a switch locally.

When my internet connection goes down for whatever reason I
loose connections in my local network. For example, i can't ping 192.168.1.40
from 192.168.1.42. is there any explaination for this?


Not that I can think of.  There's no reason I can imagine that your local
connectivity should suffer from Internet problems.  Especially if you're
connecting via IP address (which rules out DNS problems).

Could you provide 'netstat -rn' and 'ifconfig' output from GATEWAY, please.
I don't see anything in the other information you provided that would
indicate any sort of misconfig on BSD2.

--
Bill Moran
Potential Technologies
http://www.potentialtech.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue revisited

2003-02-13 Thread Brian Henning
This is my router info.

rawhide ip addr show
1: lo: LOOPBACK,UP mtu 3924 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope global lo
2: eth0: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:ba:b8:8c:2e brd ff:ff:ff:ff:ff:ff
inet 66.41.139.87/21 brd 255.255.255.255 scope global eth0
3: eth1: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:ba:ae:be:fa brd ff:ff:ff:ff:ff:ff
inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1

rawhide ip route show
192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.254
66.41.136.0/21 dev eth0  proto kernel  scope link  src 66.41.139.87
default via 66.41.136.1 dev eth0

- Original Message -
From: Bill Moran [EMAIL PROTECTED]
To: Brian Henning [EMAIL PROTECTED]
Cc: freebsd [EMAIL PROTECTED]
Sent: Thursday, February 13, 2003 1:49 PM
Subject: Re: network issue revisited


 Brian Henning wrote:
  Let me try again, here is my situation and question with a little more
detail.
 
  My local network (192.168.1.0) consists of two machine BSD1 (192.168.1.40)
and
 
  BSD2 (192.168.1.42). Both of these machines use the subnet mask
255.255.255.0
  and gateway 192.168.1.254.
 
  There is a third machine GATEWAY (192.168.1.254, ip address from isp) has
two
  nics and acts as the router.
 
  All of these machine are connected to a switch locally.
 
  When my internet connection goes down for whatever reason I
  loose connections in my local network. For example, i can't ping
192.168.1.40
  from 192.168.1.42. is there any explaination for this?

 Not that I can think of.  There's no reason I can imagine that your local
 connectivity should suffer from Internet problems.  Especially if you're
 connecting via IP address (which rules out DNS problems).

 Could you provide 'netstat -rn' and 'ifconfig' output from GATEWAY, please.
 I don't see anything in the other information you provided that would
 indicate any sort of misconfig on BSD2.

 --
 Bill Moran
 Potential Technologies
 http://www.potentialtech.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue

2003-02-13 Thread northern snowfall
I'm guessing more than likely your DNS server is external to
your internal LAN and you don't have an internal DNS to
manage RFC1918 IPs. If this is the case, this is why pings will
*seem* to fail. They are trying to look up your internal addresses
(which will fail with an internet connection up fairly quickly)
but hang because there is no connection via your ISP to a
DNS server to respond no, there is no PTR for that A.
Get yourself an internal DNS and you should be ok
Don



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue revisited

2003-02-13 Thread northern snowfall
  (which rules out DNS problems). 

Not unless he does ping -n. If not, the A will still attempt
to be resolved.
Don






To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue revisited

2003-02-13 Thread Bill Moran
Brian Henning wrote:

This is my router info.

rawhide ip addr show
1: lo: LOOPBACK,UP mtu 3924 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope global lo
2: eth0: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:ba:b8:8c:2e brd ff:ff:ff:ff:ff:ff
inet 66.41.139.87/21 brd 255.255.255.255 scope global eth0
3: eth1: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:ba:ae:be:fa brd ff:ff:ff:ff:ff:ff
inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1


Linux box, eh?


rawhide ip route show
192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.254
66.41.136.0/21 dev eth0  proto kernel  scope link  src 66.41.139.87
default via 66.41.136.1 dev eth0


Brian, I don't see anything here that looks wrong at all.  I assume
you have some sort of NAT software handling traffic between the two
interfaces, but I wouldn't normally expect that to cause problems if
the external interface is down.

I honestly can't imaging what could be causing the problems you
describe.  Hopefully, someone else will be able to look at this
and come up with something, but I'm stumped.

If you turn rawhide off (shut it down) can BSD1 ping BSD2?

Is the switch managed?  If so, make sure it's not blocking any
sort of broadcast traffic or the like.  Some of those (especially
older) managed switches can cause the strangest problems if they're
configured wrong.


- Original Message -
From: Bill Moran [EMAIL PROTECTED]
To: Brian Henning [EMAIL PROTECTED]
Cc: freebsd [EMAIL PROTECTED]
Sent: Thursday, February 13, 2003 1:49 PM
Subject: Re: network issue revisited




Brian Henning wrote:


Let me try again, here is my situation and question with a little more



detail.


My local network (192.168.1.0) consists of two machine BSD1 (192.168.1.40)



and


BSD2 (192.168.1.42). Both of these machines use the subnet mask



255.255.255.0


and gateway 192.168.1.254.

There is a third machine GATEWAY (192.168.1.254, ip address from isp) has



two


nics and acts as the router.

All of these machine are connected to a switch locally.

When my internet connection goes down for whatever reason I
loose connections in my local network. For example, i can't ping



192.168.1.40


from 192.168.1.42. is there any explaination for this?


Not that I can think of.  There's no reason I can imagine that your local
connectivity should suffer from Internet problems.  Especially if you're
connecting via IP address (which rules out DNS problems).

Could you provide 'netstat -rn' and 'ifconfig' output from GATEWAY, please.
I don't see anything in the other information you provided that would
indicate any sort of misconfig on BSD2.


--
Bill Moran
Potential Technologies
http://www.potentialtech.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue

2003-02-13 Thread Brian Henning
Ok, i am willing to try out the internal dns server but, i don't know which
machine to run it on.
Any suggestions?

- Original Message -
From: northern snowfall [EMAIL PROTECTED]
To: Brian Henning [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, February 13, 2003 2:11 PM
Subject: Re: network issue


 I'm guessing more than likely your DNS server is external to
 your internal LAN and you don't have an internal DNS to
 manage RFC1918 IPs. If this is the case, this is why pings will
 *seem* to fail. They are trying to look up your internal addresses
 (which will fail with an internet connection up fairly quickly)
 but hang because there is no connection via your ISP to a
 DNS server to respond no, there is no PTR for that A.
 Get yourself an internal DNS and you should be ok
 Don


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue

2003-02-13 Thread northern snowfall


Brian Henning wrote:


Ok, i am willing to try out the internal dns server but, i don't know which
machine to run it on.
Any suggestions?


Whichever box doesn't act as your most-used-workstation, or, the router
if its capable of running a server.
Don



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue revisited

2003-02-13 Thread Bill Moran
northern snowfall wrote:

  (which rules out DNS problems). 

Not unless he does ping -n. If not, the A will still attempt
to be resolved.
Don


Good point, I stand corrected.

--
Bill Moran
Potential Technologies
http://www.potentialtech.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: network issue revisited

2003-02-13 Thread Nathan Kinkade
On Thu, Feb 13, 2003 at 03:33:57PM -0500, Bill Moran wrote:
 northern snowfall wrote:
   (which rules out DNS problems). 
 
 Not unless he does ping -n. If not, the A will still attempt
 to be resolved.
 Don
 
 Good point, I stand corrected.
 
 -- 
 Bill Moran

I must be missing something.  Don is right, the manpage clearly states
that the -n option sould supress symbolic name lookups, but no matter
how hard I try I cannot elicit a DNS query out of ping.  I run named on
my local network.  First, I pinged an IP address that I knew my system
would not have cached anywhere - no DNS lookup.  Then I disabled named
and tried again with a few new IP addresses - still no DNS queries.
Then I even went so far as to rename my hosts file.  At this point I
couldn't even ping 'localhost' by name.  Each time, the ping worked fine
and never once issued a DNS query - I was watching with ethereal.  Is
the manpage incorrect?

Further, the OP's gateway machine should have no effect whatsoever on his
ability to ping another machine directly connected to his switch.  This
problem is mighty strange.

Nathan

-- 
GPG Public Key ID: 0x4250A04C
gpg --keyserver pgp.mit.edu --recv-keys 4250A04C
http://63.105.21.156/gpg_nkinkade_4250A04C.asc



msg19341/pgp0.pgp
Description: PGP signature


Re: network issue

2002-12-16 Thread Edmond Baroud
Hi,

I'm kinda new to this list but I had the same problem when I've
upgraded from 4.5-release to 4.7-stable.

about the ping, I'm not sure if you have any f/w on ur network or
you've installed ipf by default try ipfstat or ipmon.
concerning ssh, make sure your hostname is configured correctly if ur
using a DNS, with the correct reverse, gethostbyname() will hang ssh
with no errors (from what I've seen) if your IP has different dns
entries or wrong reverse hostnames..

hope this helps u get somehwere,

Ed.

Quoting Brian Henning ([EMAIL PROTECTED]):
 I just installed fbsd4.7 on my laptop. I used a lot of the default settings
 like default security and the ssh. I had to add my PCMCIA NIC to the
 pccard.conf so that my machine could be on the network. After doing so i
 configured it and I was able to access the web and the other machines from
 it. I then tried to ssh into the laptop from another machine on my network
 and i get nothing. When i try to ping the same laptop from another machine
 on my local network i get nothing.
 
 [/usr/src/sys/i386/conf] ping 192.168.1.44
 PING 192.168.1.44 (192.168.1.44): 56 data bytes
 100 % packets lost.
 
 i tried this from several other machines and get the same results.
 Anyone have any advice? Something to look for?
 
 thanks for any help,
 
 brian
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message

-- 
Edmond Baroud  Mobile: 1.514.999.8777
UNIX Systems Admin mailto:[EMAIL PROTECTED]
Microcell Telecom  http://www.microcell.ca/
I.Fido Serviceshttp://www.fido.ca/
Fingerprint  140F 5FD5 3FDD 45D9 226D  9602 8C3D EAFB 4E19 BEF9
UNIX is very user friendly, it's just picky about who its friends are.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message