At 01:04 19.9.2001 , you wrote:
>On Tue, Sep 18, 2001 at 12:17:29AM +0300, Mikko Lammi wrote:
>
> > Hello,
>
>Hi,
>
>
> > We have the following network topology:
> >
> >
> > (Internet connection)
> > |
> > [Bridge/FW box A]
> > | |
> > | |
> > [Switch X] [Switch Y]---(Ethernet Segment 1)
> > | \_______________
> > | \
> > [Bridge box B] (Ethernet Segment 2)
> > |
> > (Ethernet Segment 3)
> >
> >
> > All links between bridges/switches are 100Base-Tx FD.
> >
> > The problem is random lag when traffic goes over two bridge
> > boxes. Everything from ethernet segments 1 and 2 to Internet
> > works fine, also there are no problems between segments 2
> > and 3 or 2 and 1. But from segment 3 to segment 1 or Internet
> > there is some strange latency; ping times are from 0.2 ms
> > (pretty normal) to even 1000 ms. No packet loss though. So
> > basically everything that goes over two bridges is lagged. If
> > I ping directly bridge A from bridge B there's no lag, but if
> > I try to ping anything behind bridge A (Internet, segment 1),
> > random lag occurs.
>
>Are you pinging with the '-n' option?
No, the problem isn't anything trivial like DNS resolve delay or
wrong full/half duplex setting. Everything is lagged, not only ICMP
pings. This is very annoying with, for example, ssh connections.
I think it's either the switch X (3Com SuperStack 3 3300 XM) or
bridge box A (bridge + firewall) which is causing problems in
conjuction with bridge B. I guess I must do some more tests
like connecting bridges A and B directly witch patch cable
leaving switch out.
--
* Mikko Lammi / [EMAIL PROTECTED] / http://www.lammaz.net *
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
