Mark:
route -n yields Destination Gateway Genmask Flags Metric Ref Use IFace 24.159.200.0 0.0.0.0 255.255.252.0 U 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo 0.0.0.0 24.159.200.1 0.0.0.0 UG 0 0 eth0
"route print" on Windoze yields: Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 24.159.200.1 24.159.201.xxx 20 24.159.200.0 255.255.252.0 24.159.201.xxx 24.159.201.xxx 20 24.159.201.xxx 255.255.255.255 127.0.0.1 127.0.0.1 20 24.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 240.0.0.0 24.159.201.xxx 24.159.201.xxx 20 255.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 1 Default Gateway: 24.159.200.1
where "24.159.201.xxx" is the leased IP.
Thanks for any assistance.
Paul
From: Mark Neidorff mark@neidorff.com Date: 2004/03/27 Sat PM 05:54:13 GMT To: For users of Fedora Core releases fedora-list@redhat.com Subject: Re: DNS Woes
There is a lot of information missing here.
I assuming you are using fedora. Are you using webmin? What happens when you run (as root) route -n ? Is your gateway listed? Is it correct?
Lets start there.
Mark
On Sat, 27 Mar 2004 stucklenp@charter.net wrote:
I have a challenge: since running "yum update" and blindly accepting all the packages and then rebooting, I have not been able to get my Fedora box on the Web. Since that system is my firewall box it is really important that I get it running again. Note that I get the same symptoms with or without the firewall running.
The NIC is configured to "Automatically obtain IP address settings with DHCP" and "Automatically obtain DNS information from provider" (I have tried manually setting DNS addresses as well.)
When the network service is started, the NIC does get a valid IP from the ISP, as verified by the ISP. As well, I see the lease information in the messages log. "...dhclient: bound to <myIP> -- renual in 13961 seconds... ifup: done... network: Bringing up interface etho: succeeded"
Other Symptoms: ping <external IP> results in "Destination port Unreachable." ping <leased IP> Works fine.
Redhat Network Configuration show the NIC active and "ok" resolve.conf contains the correct IPs for the ISP's DNS servers.
To add insult to injury, when I plug my Windoze box into the cable modem and set its IP to use DHCP, I have no problem attaching to the Web.
Any ideas as to how I can resolve this?
Thanks
-- Sign over a gynecologist's office: "Dr. Jones, at your cervix."
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
stucklenp@charter.net wrote:
Mark:
route -n yields Destination Gateway Genmask Flags Metric Ref Use IFace 24.159.200.0 0.0.0.0 255.255.252.0 U 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo 0.0.0.0 24.159.200.1 0.0.0.0 UG 0 0 eth0
"route print" on Windoze yields: Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 24.159.200.1 24.159.201.xxx 20 24.159.200.0 255.255.252.0 24.159.201.xxx 24.159.201.xxx 20 24.159.201.xxx 255.255.255.255 127.0.0.1 127.0.0.1 20 24.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 240.0.0.0 24.159.201.xxx 24.159.201.xxx 20 255.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 1 Default Gateway: 24.159.200.1
where "24.159.201.xxx" is the leased IP.
Thanks for any assistance.
Paul
1. An earlier suggestion was to power off then back on the modem. Have you done that?
2. What is the output of 'ifconfig eth0' ? Does it match the 24.159.201.xxx above?
3. Can you ping the eth0 address?
I have at times had to power off then back on the modem, followed by 'service network restart' when my cable ISP went braindead. That sequence usually works.
Jeff
Jeff Vian became daring and sent these 1.6K bytes,
stucklenp@charter.net wrote:
Mark:
route -n yields Destination Gateway Genmask Flags Metric Ref Use IFace 24.159.200.0 0.0.0.0 255.255.252.0 U 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo 0.0.0.0 24.159.200.1 0.0.0.0 UG 0 0 eth0
"route print" on Windoze yields: Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 24.159.200.1 24.159.201.xxx 20 24.159.200.0 255.255.252.0 24.159.201.xxx 24.159.201.xxx 20 24.159.201.xxx 255.255.255.255 127.0.0.1 127.0.0.1 20 24.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 240.0.0.0 24.159.201.xxx 24.159.201.xxx 20 255.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 1 Default Gateway: 24.159.200.1
where "24.159.201.xxx" is the leased IP.
- An earlier suggestion was to power off then back on the modem. Have
you done that?
Fixed the problem for me.
- What is the output of 'ifconfig eth0' ? Does it match the
24.159.201.xxx above?
- Can you ping the eth0 address?
I have at times had to power off then back on the modem, followed by 'service network restart' when my cable ISP went braindead. That sequence usually works.
stucklenp@charter.net wrote:
Mark:
route -n yields Destination Gateway Genmask Flags Metric Ref Use IFace 24.159.200.0 0.0.0.0 255.255.252.0 U 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo 0.0.0.0 24.159.200.1 0.0.0.0 UG 0 0 eth0
"route print" on Windoze yields: Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 24.159.200.1 24.159.201.xxx 20 24.159.200.0 255.255.252.0 24.159.201.xxx 24.159.201.xxx 20 24.159.201.xxx 255.255.255.255 127.0.0.1 127.0.0.1 20 24.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 240.0.0.0 24.159.201.xxx 24.159.201.xxx 20 255.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 1 Default Gateway: 24.159.200.1
where "24.159.201.xxx" is the leased IP.
Thanks for any assistance.
Paul
I forgot to ask if you can ping the gateway (24.159.200.1) ??
From the command line add route add default gateway 24.159.200.1 dev
eth0. There are some GUI network setups under System Settings. I can't seem to remember where to permanently set static routes.
On Sun, 28 Mar 2004 stucklenp@charter.net wrote:
Mark:
route -n yields Destination Gateway Genmask Flags Metric Ref Use IFace 24.159.200.0 0.0.0.0 255.255.252.0 U 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo 0.0.0.0 24.159.200.1 0.0.0.0 UG 0 0 eth0
"route print" on Windoze yields: Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 24.159.200.1 24.159.201.xxx 20 24.159.200.0 255.255.252.0 24.159.201.xxx 24.159.201.xxx 20 24.159.201.xxx 255.255.255.255 127.0.0.1 127.0.0.1 20 24.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 240.0.0.0 24.159.201.xxx 24.159.201.xxx 20 255.255.255.255 255.255.255.255 24.159.201.xxx 24.159.201.xxx 1 Default Gateway: 24.159.200.1
where "24.159.201.xxx" is the leased IP.
Is it a typo on your part????? You lease an ip in the 24.159.201 range, but your nic in fedora is in the 24.159.200 range!!!!! That would mess everything up.
Mark
While opening KDE I started exiting programs and starting others before it was fully initialized and scrambled my GUI so badly that the only the mouse worked on screen0. Symptoms included (on screen0 only screen1 totally unaffected); 1) Unable to get more than 1 virtual screen. 2) Crash when trying to change the backround. 3) No keyboard. 4) No window decorations. 5) Root and other users unaffected.
I moved the .kde directory in my home directory and all references in /~ and /tmp. This cleared all my preferences and allowed me to fix the error.
This allowed me to fix the error/bug/corruption. Is there a more direct less invasive way to effect repairs?
jludwig wrote:
While opening KDE I started exiting programs and starting others before it was fully initialized and scrambled my GUI so badly that the only the mouse worked on screen0. Symptoms included (on screen0 only screen1 totally unaffected);
That's the way I've fixed KDE before, sorry, don't know a better way.
Out of curiosity, is anti-aliasing working for you in dual-head mode? It works better for me with fonts if I don't use a font server, but still icons look bad and fonts still aren't right, especially in kterm.
thanks,
Peter
I never considered modifying default anti-aliasing or font rendering. I don't use xinerama since xinerama stretches the screen. This leaves me with, in essence, two single monitor systems using the same display manager, mouse and keyboard. I found that I much prefer running this way even though I can't move applications from one screen to another. At times it is inconvenient but the lessening of visual strain significantly increases the overall usefulness and productivity of the system.
jludwig wrote:
I never considered modifying default anti-aliasing or font rendering. I don't use xinerama since xinerama stretches the screen. This leaves me with, in essence, two single monitor systems using the same display manager, mouse and keyboard. I found that I much prefer running this way even though I can't move applications from one screen to another. At times it is inconvenient but the lessening of visual strain significantly increases the overall usefulness and productivity of the system.
Sorry, I know this is off topic, but I'm curious. How does being able to move windows between displays create visual strain? On both my work and home dual-head machines I don't see any difference in how applications are displayed between xinerama, non-xinerama dual-head or just plain single head. I don't see any visual strain inducing problems at all.
The one exception to this had to do with a bug which used to exist in X that caused OpenOffice to put too much space between characters, this has been fixed, however.
Peter
On Mon, 2004-03-29 at 13:56, Peter Eddy wrote:
jludwig wrote:
While opening KDE I started exiting programs and starting others before it was fully initialized and scrambled my GUI so badly that the only the mouse worked on screen0. Symptoms included (on screen0 only screen1 totally unaffected);
That's the way I've fixed KDE before, sorry, don't know a better way.
Out of curiosity, is anti-aliasing working for you in dual-head mode? It works better for me with fonts if I don't use a font server, but still icons look bad and fonts still aren't right, especially in kterm.
I also noticed that anti-aliasing didn't work in dual-head mode with Xinerama, if I turn Xinerama off it works well, in GNOME it works well also with Xinerama on. Using TwinView instead of Xinerama it also works well but I'd still prefer if somebody fixed anti-aliasing with Xinerama because I don't like way TwinView works...
Jean-Rene Cormier
I noticed since Fedora1 that Xinerama doesn't work with antialiased fonts. I had to install (overwrite) Xlibs with redhat9 ones and then it's ok, but I can't to logoff, because X hangs after shutdowning KDE. Anyone fixed this problem?
thx, michal Nvidia GF4, Matrox Mystique, Athlon-xp.
Jean-Rene Cormier wrote:
On Mon, 2004-03-29 at 13:56, Peter Eddy wrote:
jludwig wrote:
While opening KDE I started exiting programs and starting others before it was fully initialized and scrambled my GUI so badly that the only the mouse worked on screen0. Symptoms included (on screen0 only screen1 totally unaffected);
That's the way I've fixed KDE before, sorry, don't know a better way.
Out of curiosity, is anti-aliasing working for you in dual-head mode? It works better for me with fonts if I don't use a font server, but still icons look bad and fonts still aren't right, especially in kterm.
I also noticed that anti-aliasing didn't work in dual-head mode with Xinerama, if I turn Xinerama off it works well, in GNOME it works well also with Xinerama on. Using TwinView instead of Xinerama it also works well but I'd still prefer if somebody fixed anti-aliasing with Xinerama because I don't like way TwinView works...
Jean-Rene Cormier
While opening KDE I started exiting programs and starting others before it was fully initialized and scrambled my GUI so badly that the only the mouse worked on screen0. Symptoms included -- on screen0 only screen1 totally unaffected; 1) Unable to get more than 1 virtual screen. 2) Crash when trying to change the backround. 3) No keyboard. 4) No window decorations. 5) Root and other users unaffected.
I moved the .kde directory in my home directory and all references in /~ and /tmp. This cleared all my preferences and allowed me to fix the error.
This allowed me to fix the error/bug/corruption. Is there a more direct less invasive way to effect repairs?
-
Aaron Matteson -
Jean-Rene Cormier -
Jeff Vian -
jludwig -
Mark Neidorff -
Michal Zeravik -
Peter Eddy -
stucklenp＠charter.net