I recently upgraded/installed Fedora Core 2 migrating from Redhat 8.0 to this one. My internet connection is now incredibly slowwwww, and at times does not even connect to sites. I know have connection because some do load up eventually. I thought this may be a firewall thing, so turned that off, but still having trouble.

I haven't changed anything but the distro, the hardware stayed the same. Anyone might know why?

A common mistake is an incorrect MTU setting in your DSL router, PPPoE or PPP settings. Other common mistakes are a bad DNS server configuration and a broken local network configuration.

Thanks for the reply.
I have linux on a windows network using a dsl router. The router is forwarding to port 192.168.0.254 and I have my linux network set to that static address (this is so people who game/MUD to my machine can be forwarded to the right box). Also, fedora shows up on the active user list on the browser's network status.

The windows host seems to be 192.168.0.4.

How do I check the MTU?

The MTU is in your router setup.

For the Linux side of the network configuration, consider posting the output of:

netstat -nr
/sbin/ifconfig -a
cat /etc/resolv.conf
cat /etc/hosts

Tweaked a few more things and seems to be working now. I'm including the stats you wanted to see if there's anything weird going on anway:

Actually, this host is my laptop:

cat /etc/hosts

192.168.0.6

Not sure why the main comp or 192.168.0.1 is not there

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0



eth0 Link encap:Ethernet HWaddr 00:50:BF:ED:CF:EF
inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::250:bfff:feed:cfef/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1084 errors:0 dropped:0 overruns:0 frame:0
TX packets:1500 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:499018 (487.3 Kb) TX bytes:192199 (187.6 Kb)
Interrupt:11 Base address:0xf800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7003 errors:0 dropped:0 overruns:0 frame:0
TX packets:7003 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9270434 (8.8 Mb) TX bytes:9270434 (8.8 Mb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


search domain.actdsltmp
nameserver 192.168.0.4
nameserver 205.XXX.X.XX
nameserver 192.168.0.1

This is strange, unless your Windows host really provides a DNS service. Specifying "nameserver 192.168.0.1" should be enough, because your router forwards DNS queries to your service provider's name server.

hmm, one thing though. I renamed my hostname from localhost to eon, and can't seem to telnet 'eon', or 127.0.0.1 What do i need to change?

/etc/hosts must contain the following:

127.0.0.1 localhost.localdomain localhost

Don't delete it. Don't change it.

Thanks again,
I replaced that but am still unable to do it. I think maybe the telnet daemon is missing. I can telnet out though??

Hehe,
In answer to my own dilema I did not have the telnet-server package installed. So installed it, restarted xinetd and works fine now