new router, can't get out

OK, somebody give me a clue please. I replaced a USR8054 with a Netgear
MR814v2 today. Both have four ethernet ports -- the USR has 10/100 ports, I
believe the Netgear has 10 Mbps only. :-( Both have 802.11 transmitters --
USR is b/g, Netgear is b only. All machines in the house except for mine
can get on the net. Some are laptops connected by 802.11b, some are through
a dumb hub daisy-chained off port 4, and some are wired. The router has the
same address as the previous one, 192.168.1.25, so I shouldn't have to
change anything on the computers.

I own VMware, and it can't get out either, which leads me to think it's
something about my NIC. According to the router's web-based config tool,
the MAC address is not blocked (and that shouldn't affect VMware anyhow).
My NIC uses the "8139too" driver in 2.4.22 .

Does anybody know what might be wrong? Thanks.

Eben King wrote:

> OK, somebody give me a clue please. I replaced a USR8054 with a Netgear
> MR814v2 today. Both have four ethernet ports -- the USR has 10/100 ports,
> I
> believe the Netgear has 10 Mbps only. :-( Both have 802.11 transmitters
> --
> USR is b/g, Netgear is b only. All machines in the house except for mine
> can get on the net. Some are laptops connected by 802.11b, some are
> through a dumb hub daisy-chained off port 4, and some are wired. The
> router has the same address as the previous one, 192.168.1.25, so I
> shouldn't have to change anything on the computers.
>
> I own VMware, and it can't get out either, which leads me to think it's
> something about my NIC. According to the router's web-based config tool,
> the MAC address is not blocked (and that shouldn't affect VMware anyhow).
> My NIC uses the "8139too" driver in 2.4.22 .
>
> Does anybody know what might be wrong? Thanks.

Hi!

Don't know about your specific router setup, but I have one provided by the
local telco and it has to be set to PPPoE explicitly to work in both Linux
and Windows.

You might check if the new router you have is not set on ATM or something?
--
---
Stefan Viljoen
Software Support Technician
Polar Design Solutions

"Stefan Viljoen" <rylan@-deletethis-intekom.co.za> wrote in message
news:cbgeal$s7d$(E-Mail Removed)...
> Eben King wrote:
>
> > OK, somebody give me a clue please. I replaced a USR8054 with a Netgear
> > MR814v2 today. Both have four ethernet ports -- the USR has 10/100
ports,
> > I
> > believe the Netgear has 10 Mbps only. :-( Both have 802.11
transmitters
> > --
> > USR is b/g, Netgear is b only. All machines in the house except for
mine
> > can get on the net. Some are laptops connected by 802.11b, some are
> > through a dumb hub daisy-chained off port 4, and some are wired. The
> > router has the same address as the previous one, 192.168.1.25, so I
> > shouldn't have to change anything on the computers.
> >
> > I own VMware, and it can't get out either, which leads me to think it's
> > something about my NIC. According to the router's web-based config
tool,
> > the MAC address is not blocked (and that shouldn't affect VMware
anyhow).
> > My NIC uses the "8139too" driver in 2.4.22 .
> >
> > Does anybody know what might be wrong? Thanks.

> Don't know about your specific router setup, but I have one provided by
the
> local telco and it has to be set to PPPoE explicitly to work in both Linux
> and Windows.
>
> You might check if the new router you have is not set on ATM or something?

No, all the other machines on the LAN work, so the router's settings must be
approximately correct. I don't have PPPoE anyhow; the cable modem converts
DOCSIS(?) to straight TCP/IP over ethernet, which goes directly into the
router. Good idea, though.

"Eben King" <(E-Mail Removed)> wrote in message
news:qDOCc.5431$(E-Mail Removed) ...
> OK, somebody give me a clue please. I replaced a USR8054 with a Netgear
> MR814v2 today. Both have four ethernet ports -- the USR has 10/100 ports,
I
> believe the Netgear has 10 Mbps only. :-( Both have 802.11
transmitters --
> USR is b/g, Netgear is b only. All machines in the house except for mine
> can get on the net. Some are laptops connected by 802.11b, some are
through
> a dumb hub daisy-chained off port 4, and some are wired. The router has
the
> same address as the previous one, 192.168.1.25, so I shouldn't have to
> change anything on the computers.
>
> I own VMware, and it can't get out either, which leads me to think it's
> something about my NIC. According to the router's web-based config tool,
> the MAC address is not blocked (and that shouldn't affect VMware anyhow).
> My NIC uses the "8139too" driver in 2.4.22 .
>
> Does anybody know what might be wrong? Thanks.

I narrowed it down some. While I can get on the net, various programs on my
computer -- among them junkbuster, fetchmail and gaim -- don't like the
router. I'll probably exchange it for the Linksys 802.11b router, as it was
the same price, and will probably act better. The 10 Mbps-only restriction
is a major down, in my book.

-eben

I solved it. It seems "IP: TCP Explicit Congestion Notification support" in
the kernel's "networking options" section is compatible with the previous
router (USR8054) but not this one (NG814v2). I've already compiled a kernel
without it, but until I reboot, I can turn it off by "echo 0 >
/proc/sys/net/ipv4/tcp_ecn".

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar

Logic is a systematic method of coming to
the wrong conclusion with confidence.

On Fri, 25 Jun 2004 05:21:26 +0000, Eben King rearranged some electrons to
form:

> OK, somebody give me a clue please. I replaced a USR8054 with a Netgear
> MR814v2 today. Both have four ethernet ports -- the USR has 10/100 ports,
> I believe the Netgear has 10 Mbps only. :-( Both have 802.11
> transmitters -- USR is b/g, Netgear is b only. All machines in the house
> except for mine can get on the net. Some are laptops connected by
> 802.11b, some are through a dumb hub daisy-chained off port 4, and some
> are wired. The router has the same address as the previous one,
> 192.168.1.25, so I shouldn't have to change anything on the computers.
>
> I own VMware, and it can't get out either, which leads me to think it's
> something about my NIC. According to the router's web-based config tool,
> the MAC address is not blocked (and that shouldn't affect VMware anyhow).
> My NIC uses the "8139too" driver in 2.4.22 .
>
> Does anybody know what might be wrong? Thanks.

This may be a long shot, but I had a situation a while back where I had to
set the NIC to "half-duplex only" to make it work.

--
David M (dmacchiarolo)
http://home.triad.rr.com/redsled
T/S 53
sled351 Linux 2.4.18-14 has been up 18 days 7:02