On Sat, Aug 16, 2003 at 06:16:07PM -0700, Mark Knecht wrote:
> Thanks for responding Nathan. Still having the problem big time.
> 
> On Sat, 2003-08-16 at 16:48, [EMAIL PROTECTED] wrote:
> > No explanations jump to mind, but here are a couple of things I'd try
> > if I were facing this behavior:
> > 
> > - Run /sbin/ifconfig - are you seeing high counts of errors, dropped
> >   packets, and such for that interface?
> 
> Not from what I can see. The first is after a reboot and before I start
> Mozilla. The second is after it's been hanging for a minute.
> 
> Wizard root # ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:E0:18:EC:47:FF  
>           inet addr:192.168.1.26  Bcast:192.168.1.255 
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:92 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:95 errors:0 dropped:0 overruns:0 carrier:95
>           collisions:0 txqueuelen:100 
>           RX bytes:45894 (44.8 Kb)  TX bytes:9068 (8.8 Kb)
>           Interrupt:18 Memory:ea000000-ea001080 
> 
> Wizard root # ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:E0:18:EC:47:FF  
>           inet addr:192.168.1.26  Bcast:192.168.1.255 
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:104 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:113 errors:0 dropped:0 overruns:0 carrier:113
>           collisions:0 txqueuelen:100 
>           RX bytes:58770 (57.3 Kb)  TX bytes:11242 (10.9 Kb)
>           Interrupt:18 Memory:ea000000-ea001080 
> 
> > 
> > - Restart the interface:
> > 
> >       /etc/init.d/net.eth0 restarts
> >       
> >   (or whatever the particular device's init script is, if not eth0).
> > 
> > Are you using DHCP on the subnet? If so, did you restart your interface
> > after you restarted the router?
> 
> The above data is after a complete power down of the network. Firewall
> and both PC's shut down. Then the firewall was brought up followed by
> the Gentoo box. No change in the problem. XP box still off.

So much for that... you restarted everything in a reasonable way.

The next thing I would do if I were dealing with this is to run a
network analyzer. The "ethereal" tool, which is available in an ebuild,
is excellent. Of course, if your background doesn't include some
understanding of networks and protocols, there's a nasty learning curve.

> > Some of these symptoms suggest problems when your client opens multiple
> > connections - the browser behavior is consistent with that, although
> > I wouldn't expect that for email protocols (unless you're accessing
> > Web-based email through a browser). That said, I'm not sure what to
> > do about it.
> > 
> 
> No, just using Evolution going to pop and smtp servers. However, the
> delay is only for files that have large attachments, not for ones that
> do not.
> 
> I also tried using an ftp client in Windows and going to a couple of
> places. That didn't seem to work well at all either. Huge delays. Doing
> a right-click on a *.gz file on a web page and saving to Save As results
> in very slow download again.
> 
> So what if the multiple connections, or even just one or two protocols 
> are now causing problems with my firewall and its new firmware? Why
> would this only happen with the Linux box and not the Windows box? I
> think that doesn't make sense.

No, it doesn't make sense and it won't until the problem is identified
and explained - then it'll turn out to be some obvious, d'oh! sort of
thing :-). What you're describing doesn't match anything I've ever seen
in 7 years of using Linux... I'm sure that's why I (and many others)
can't come forward with an explanation based on what you've told us.

> I guess I could bypass the firewall and hang this box directly on the
> net to find out if the problem is in the box or in the firewall, but I'm
> not happy about doing that, and I don't know right now how to set up a
> DHCP Linux box, so I'd have to study to do that.

Converting your internal network to DHCP won't solve whatever's going on.
But you may still need DHCP...

Bypassing your firewall for a brief test wouldn't hurt - especially if
you're sure you're not running any services (Web, ftp, mail, networked
file systems, and such). Then you could ascertain if it's implicated in
the performance problems.

Your firewall is probably handling the address translation, so you'll need
to reconfigure the Linux system to the external address. Your mileage
may vary, but with many broadband providers it'll work to just set up
your Linux system as a DHCP client and let it get an address from the
network (very easy on Gentoo - go to /etc/conf.d/net and change a line
that looks like this:

  iface_eth0="192.168.1.26 broadcast 192.168.1.255 netmask 255.255.255.0"

to look like this:

  iface_eth0="dhcp"

and restart that network device. Assuming you've bypassed the firewall,
it'll get its address from the DHCP server run by your provider and
you'll be on the Internet.)

Nathan Meyers
[EMAIL PROTECTED]


> I'm completely confused. Not that difficult as I'm not much of a Linux
> guy.
> 
> Mark

--
[EMAIL PROTECTED] mailing list

Reply via email to