LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   HTTP not working, but DSL seems fine (http://www.linuxquestions.org/questions/linux-networking-3/http-not-working-but-dsl-seems-fine-453076/)

robprentice 06-09-2006 01:45 AM

HTTP not working, but DSL seems fine
 
I just installed Fedora core 5 on a home PC machine (double-boots WinXP & Fedora) beneath a DSL gateway running DHCP. Just about everything remains in its default configuration. The network works fine on the WinXP side, but only connects with a few sites under Fedora. Yum, downloads, and google always fail. Experimenting, I found that wget to a particular site only works if I first perform an nslookup to it. I can ping my ISP's DNS server and the DSL router, the router's lights are all green. Traceroute shows nothing but asterisks. I stopped iptables temporarily, but got the same behavior. Some relevant command output follows.
What could cause this? What should I check next?

NOTE: I had to edit out the URLs below in order to get
this post to work. Various URLs that I've tried
show the same behavior.

------------- mii-tool -v ----------------
eth0: negotiated 100baseTx-FD flow-control, link ok
product info: vendor 00:07:49, model 1 rev 1
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control

-------- ethtool eth01 ---------
Settings for eth0:
No data available

--------- ifconfig -a --------------
eth0 Link encap:Ethernet HWaddr 00:0C:41:EF:33:70
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:41ff:feef:3370/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:955 (955.0 b) TX bytes:3557 (3.4 KiB)
Interrupt:9 Base address:0x6000

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:2749 errors:0 dropped:0 overruns:0 frame:0
TX packets:2749 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4312250 (4.1 MiB) TX bytes:4312250 (4.1 MiB)

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)

-----------wget URL-WAS-HERE ------------ wget fails
--21:18:19-- URL-WAS-HERE
=> `index.html'
Resolving URL-WAS-HERE... 1.0.0.0
Connecting to URL-WAS-HERE|1.0.0.0|:80...
TIMES OUT

-----------/sbin/arp -a ----------- shows contact with gateway DSL router
dslmodem.domain.actdsltmp (192.168.0.1) at 00:15:05:0C:0F:8A [ether] on eth0

----------ping 204.144.142.2 # ISP's DNS server----------
PING 204.144.142.2 (204.144.142.2) 56(84) bytes of data.
64 bytes from 204.144.142.2: icmp_seq=1 ttl=62 time=31.0 ms
64 bytes from 204.144.142.2: icmp_seq=2 ttl=62 time=32.0 ms
64 bytes from 204.144.142.2: icmp_seq=3 ttl=62 time=30.8 ms
64 bytes from 204.144.142.2: icmp_seq=4 ttl=62 time=53.0 ms
64 bytes from 204.144.142.2: icmp_seq=5 ttl=62 time=31.8 ms
64 bytes from 204.144.142.2: icmp_seq=6 ttl=62 time=31.6 ms

--- 204.144.142.2 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5002ms
rtt min/avg/max/mdev = 30.842/35.089/53.061/8.051 ms

----------- nslookup URL-WAS-HERE ---------- an nslookup succeeds
Server: 192.168.0.1
Address: 192.168.0.1#53

Non-authoritative answer:
URL-WAS-HERE canonical name = URL-WAS-HERE.
Name: URL-WAS-HERE
Address: 66.102.7.104
Name: URL-WAS-HERE
Address: 66.102.7.147
Name: URL-WAS-HERE
Address: 66.102.7.99

---------- wget URL-WAS-HERE ----------- wget after nslookup works
--21:22:25-- URL-WAS-HERE
=> `index.html'
Resolving URL-WAS-HERE... 66.102.7.104
Connecting to URL-WAS-HERE|66.102.7.104|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

0K .. 300.49 KB/s

21:22:25 (300.49 KB/s) - `index.html' saved [2621]


-----------traceroute 66.102.7.104 --------- traceroute shows little
traceroute to 66.102.7.147 (66.102.7.147), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
...

------- lspci --------
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:0d.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 04)
00:0d.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 01)
00:0e.0 Mass storage controller: Promise Technology, Inc. PDC20262 (FastTrak66/Ultra66) (rev 01)
00:0f.0 SCSI storage controller: Adaptec AIC-7892A U160/m (rev 02)
00:10.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev 11)
01:00.0 VGA compatible controller: nVidia Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 11)

------- lsmod --------
Module Size Used by
ppdev 8645 0
autofs4 19013 1
hidp 15937 2
rfcomm 34517 0
l2cap 23617 10 hidp,rfcomm
bluetooth 44069 3 hidp,rfcomm,l2cap
sunrpc 136573 1
ip_conntrack_netbios_ns 3009 0
ipt_REJECT 5441 1
xt_state 2241 2
ip_conntrack 49261 2 ip_conntrack_netbios_ns,xt_state
nfnetlink 6489 1 ip_conntrack
xt_tcpudp 3265 4
iptable_filter 3137 1
ip_tables 11657 1 iptable_filter
x_tables 12613 4 ipt_REJECT,xt_state,xt_tcpudp,ip_tables
vfat 11969 1
fat 47709 1 vfat
dm_mirror 19985 0
dm_mod 50521 1 dm_mirror
video 14917 0
button 6609 0
battery 9285 0
ac 4933 0
ipv6 225569 12
lp 12297 0
parport_pc 25445 1
parport 34313 3 ppdev,lp,parport_pc
floppy 57733 0
nvram 8393 0
joydev 9473 0
uhci_hcd 28881 0
sg 32349 0
snd_emu10k1_synth 6977 0
snd_emux_synth 31553 1 snd_emu10k1_synth
snd_seq_virmidi 7105 1 snd_emux_synth
snd_seq_midi_emul 5953 1 snd_emux_synth
snd_emu10k1 104261 2 snd_emu10k1_synth
snd_rawmidi 24001 2 snd_seq_virmidi,snd_emu10k1
snd_ac97_codec 83937 1 snd_emu10k1
snd_ac97_bus 2497 1 snd_ac97_codec
snd_seq_dummy 3781 0
snd_seq_oss 28993 0
snd_seq_midi_event 7105 2 snd_seq_virmidi,snd_seq_oss
snd_seq 47153 8 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss 45009 0
snd_mixer_oss 16449 1 snd_pcm_oss
snd_pcm 76869 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_seq_device 8909 7 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd_timer 22597 3 snd_emu10k1,snd_seq,snd_pcm
snd_page_alloc 10441 2 snd_emu10k1,snd_pcm
snd_util_mem 5057 2 snd_emux_synth,snd_emu10k1
snd_hwdep 9541 2 snd_emux_synth,snd_emu10k1
emu10k1_gp 3905 0
snd 50501 15 snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_seq_oss,snd_seq,snd_pcm_os s,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,snd_hwdep
i2c_piix4 8529 0
gameport 15177 2 emu10k1_gp
tulip 46817 0
i2c_core 20673 1 i2c_piix4
soundcore 9377 1 snd
ext3 116809 2
jbd 53077 1 ext3
aic7xxx 129909 0
scsi_transport_spi 21441 1 aic7xxx
sd_mod 16577 0
scsi_mod 125289 4 sg,aic7xxx,scsi_transport_spi,sd_mod

cdhgee 06-09-2006 03:33 AM

Sounds like your DNS setup isn't quite right. Can you post /etc/resolv.conf.

robprentice 06-12-2006 09:16 PM

Hi. Here's /etc/resolv.conf:

; generated by /sbin/dhclient-script
search domain.actdsltmp
nameserver 192.168.0.1
nameserver 204.144.142.2

cdhgee 06-13-2006 06:32 AM

Try taking the 192.168.0.1 line out and see if that helps. If not, try replacing the file with the following contents:

Code:

nameserver 158.43.192.1
nameserver 158.43.128.1

I know these name servers work.

robprentice 06-13-2006 11:56 PM

Removing the entry corresponding to the DSL gateway
did the trick. Thanks for your help.

robprentice 06-29-2006 01:30 PM

I fixed the problem described above, only to have it return each
time that I reboot. It appears to be a DHCP problem that shows up
in both Fedora and Ubuntu. My PC is connected to an ISP via an
Actiontec DSL modem. By default, whenever I boot, the /etc/resolv.conf
file gets replaced with the following:

; generated by /sbin/dhclient-script
search domain.actdsltmp
nameserver 192.168.0.1
nameserver 204.144.142.2

The first IP address shown is that of the DSL router, which
should not be in the list. If I correct the file to:

nameserver 204.144.142.2
nameserver 204.144.142.1

then the Internet connection works fine, until I reboot. What's the
best way for me to fix this problem?

robprentice 07-01-2006 06:35 PM

I found a workaround that covers up the problem. I placed the
following line in /etc/dhclient.conf:

prepend domain-name-servers 204.144.142.2, 204.144.142.1;

This prepends the known servers to the list, so if they are found
all is well. The drawback is that if my ISP changes its DNS servers,
then DNS will hang on the bogus entry before reaching the new real
servers... the same behavior that I saw before. Actually fixing the
problem will involve looking at how dhclient is working, which I'm
not prepared to get into right now.

If anyone knows of a better solution, I'm all ears. :-)


All times are GMT -5. The time now is 11:49 AM.