I've had issues using ifconfig to set MTU. Also, if the problem is MTU, you'll want to set your Windows system MTU down as well... I believe Windows is not very good at responding correctly to the ICMP messages which control transmission size. It just makes everything cleaner. Try the Linux box first. If this clears it up, I'd recommend doing the Windows system as well.
If ifconfig does not work for you (I believe the issue I've seen could be NIC-specific) you can use the "ip" command: MYBOX# ip link set <interface> mtu 1300 On Sat, 27 Sep 2003 07:07:47 -0500 "David A. Bandel" <[EMAIL PROTECTED]> wrote: > On Fri, 26 Sep 2003 13:25:43 -0700 (PDT) > Brad De Vries <[EMAIL PROTECTED]> wrote: > > > I have a network of WinXX PC's with a single Linux box > > acting as the gateway/firewall/dhcp server/e-mail > > server/etc. My Linux box connects to the ISP via 128K > > ISDN dial-up line (too far away for DSL and cable is > > N/A). > > > > When I first connect the Linux box to the ISP, I can: > > 1) Use the Linux box to traceroute to everything (the > > ISP blocked ICMP so I can't ping outside their > > network). > > 2) Use the Linux box to browse the web (using Lynx). > > 3) Use the WinXX PC's to browse the web to "some" > > sites (google, domains hosted by ISP, etc.) > > > > When I first connect the Linux box to the ISP, I can > > not: > > 1) Use the WinXX PC's to tracert beyond the first two > > hops, Linux box is first and the ISP's router is the > > second. > > 2) Use the WinXX PC's to browse the web to anything > > "big" such as Yahoo!, ABCNews, FoxNews, > > WeatherChannel, etc. > > > > After a while (sometimes 5 minutes, sometimes 20 or > > more) I begin to lose some functionality. Such as > > traceroute from Linux to the world or pinging the > > ISP's router, etc. The ISDN Terminal Adapter (i.e., > > modem) sends the requests, the SD light goes on, but > > never receives a reply, no RD light. > > > > I've been experiencing this problem for the last week > > to 10 days. Does anyone have any thoughts as to what > > might be the cause? I've replaced some hardware > > including the hub and cabling and I've tried using an > > analog modem but the same problem persists. The Linux > > box has been running for a very long time without any > > changes. (For those of you heavily in the Windows > > world, a user rebooted the Linux box the other day to > > see if it would fix the problem but it, obviously, > > didn't.) > > Sounds like a typical broken DNF issue. Try lowering the MTU on the > Linux box' connection to your ISP and see if that helps: > > ifconfig <dev> mtu 296 > > If not, does your ISP permit multiple systems behind a NAT box? There > are ways to detect nat'd systems, and he _might_ be blocking them (would > be the first time I've heard of this happening though). > > Ciao, > > David A. Bandel > -- > Focus on the dream, not the competition. > Nemesis Racing Team motto > GPG key autoresponder: mailto:[EMAIL PROTECTED] > -- Matthew Carpenter [EMAIL PROTECTED] http://www.eisgr.com/ Enterprise Information Systems * Network Server Appliances * Network Consulting, Integration & Support * Web Integration and E-Business _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://mail.linux-sxs.org/mailman/listinfo/linux-users
