Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 17 Jul 1999 11:06:58 -0700
From:      The Clark Family <Clark@open.org>
To:        <dtougas@converging.net>, <freebsd-questions@FreeBSD.ORG>
Cc:        "'Steve Hovey'" <shovey@buffnet.net>
Subject:   RE: Getting frustrated with bizarre networking problem...
Message-ID:  <4.0.1.19990715163707.00e1e7d0@opengovt.open.org>
In-Reply-To: <D1378A34D8E2D211831900105A99D3FE06D1C9@BDC>
References:  <D1378A34D8E2D211831900105A99D3FE26309A@BDC>

next in thread | previous in thread | raw e-mail | index | archive | help

I ran into weirdness like this once.

Turns out that two (different brand) switches weren't converging, and blind
spots were popping up.

Are you sure that the stuff upstream of the ADSL unit is expecting to see
two MACs? I've heard some weird things about how DSLAMs work.

One box may be washing the other's MAC entries out of a table. If so, put
the NT system behind the FreeBSD box, and alias/NATD it.

(Then they'd only have one MAC.)

Restarting the FreeBSD box may be re-publishing the ARP info.

Just a guess, [RC]



At 04:22 PM 7/14/99 -0600, Damien Tougas wrote:
>> Could your NT (or something else) be sending feault routing 
>> information to
>> the freebsd, and do you have routed running on the freebsd?
>
>No, routed is not running on FreeBSD.  Both FreeBSD and Proxy
>are at the same level in the networking heiarchy.  Proxy is
>multi-homed (10.0.0.1 and 161.X.Y.250) and acts like a
>gateway to our internal network. FreeBSD, which has a single NIC
>(161.X.Y.251), serves up our WWW.  Both servers are connected
>via a hub to our ADSL modem, and have the same gateway which
>is 161.X.X.1.  So I guess my point to all this is that I don't
>understand how NT could be sending false routing information.
>
>Perhaps somthing else could be happening higher up at our ISP.
>The only thing that confuses me a bit is that the when when
>the http server appears to be down from the outside, all we need
>to do is either reboot FreeBSD or (as I have just discovered)
>start tcpdump running and the service is instantly restored.
>
>I by no means claim to be a networking guru, so there are likely
>issues to which you are referring that I do not understand.
>
>> If routed is running - from the inside when you cant get in from the
>> outside do a netstat -nr to see if the default route is your 
>> proxy or not. If it isnt, then your packets are going someplace 
>> else is the problem.
>
>I will defenitely give this a try when it happens again.
>
>Thanks for your reply.
>
>Damien Tougas
>Converging Technology Solutions, Inc.
>10148 - 73 Street
>Edmonton, Alberta  T6A 2W9
>Phone: (780) 469-1679
>Fax:  (780) 461-5127
>mailto:dtougas@converging.net
>http://www.converging.net
>
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-questions" in the body of the message
> 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.0.1.19990715163707.00e1e7d0>