Quantcast
Channel: CentOS Bug Tracker - Issues
Viewing all articles
Browse latest Browse all 19115

0006095: Websites not Loading

$
0
0
Fully installed and configured CentOS 6.3 with GNOME (2.28.2) installed from Live CD x84_64 for demonstration purpose of Asterisk PBX.<br /> Platform : Intel Core 2, T5600<br /> RAM: 4 GB<br /> <br /> java version "1.6.0_24"<br /> OpenJDK Runtime Environment (IcedTea6 1.11.5) (rhel-1.50.1.11.5.el6_3-x86_64)<br /> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)<br /> <br /> Report: Firefox, Version (10.0.11) not loading websites specially<br /> <br /> 1. www.gmail.com<br /> 2. www.hotmail.com<br /> <br /> There might be same issue with some other websites but I have not seen that. Same Websites are opening without any problem on MS Windows 7 environment. I <br /> <br /> could not find any information regarding this issue on any Linux Forums either.<br /> These websites could not be loaded on both wired and wireless network under Linux environment. <br /> Same Linux machine opens the above mentioned website without any problems if using some other Network. <br /> Network: D-link DI-524 Wireless Router (IP:192.168.0.1)+ WiMax DSL Modem (IP: 192.168.15.1). Modem is connected to router through WAN port.<br /> These websites are not opening on any other CentOS machines as well in this network. <br /> Older distributions of Linux (Fedora Core 10, Core 11) work fine on the same network.<br /> I have changed the configuration files accordingly to overcome this problem but in no use.<br /> As shown in /etc/resolve.conf , it show two IPs , nameserver 192.168.15.1 & 192.168.0.1.<br /> If I connect the Linux Machine directly throw network cable to my WiMax modem, everything starts working fine. This time if I check the /etc/resolve.conf <br /> <br /> file there will only be “nameserver 192.168.15.1”. I made changes to /etc/sysconfig/network-scriept/ifcfg-Auto_Wlan01 but nothing worked. <br /> Conclusion: There is no problem in installation as it is working fine on all other networks where there is single device (builtin modem + router) but with <br /> <br /> this particular network, where there is a combination of D-link Router DI-524 and WiMax DSL Modem or when there are two nameserver addresses in <br /> <br /> /etc/resolve.conf file. <br /> <br /> Can I call it a bug in kernel in new Linux Versions, that it is not handling two addresses or these two particular addresses (192.168.15.1 & 192.168.0.1). <br /> <br /> But I cannot understand, as I have mentioned about that older Linux distributions are working fine on the same network. If I connect my linux machine <br /> <br /> directly to WiMax modem using wire, everything start working. And as well as there is no problem if working under MS Windows environment. <br /> <br /> <br /> Some configuration files are given below.<br /> If you need any further information please do not hesitate to contact me on my email address.<br /> <br /> Best Regards<br /> Khalid Malik<br /> <a href="mailto:Khalid.maalik@gmail.com">Khalid.maalik@gmail.com</a><br /> <br /> ----------------------------------------------------------------<br /> /etc/resolve.conf<br /> # Generated by NetworkManager<br /> nameserver 192.168.15.1<br /> nameserver 192.168.0.1<br /> -----------------------------------<br /> /etc/sysconfig/network<br /> NETWORKING=yes<br /> NETWORKING_IPV6=no<br /> HOSTNAME=localhost.localdomain<br /> -----------------------------------<br /> <br /> /etc/sysconfig/network-scriept/ifcfg-Auto_ding_dong (Wireless Network Name)<br /> ESSID="ding_dong"<br /> MODE=Managed<br /> KEY_MGMT=WPA-PSK<br /> TYPE=Wireless<br /> BOOTPROTO=dhcp<br /> DEFROUTE=yes<br /> PEERDNS=yes<br /> PEERROUTES=yes<br /> IPV4_FAILURE_FATAL=yes<br /> IPV6INIT=no<br /> NAME="Auto ding_dong"<br /> UUID=5fe5c993-c0aa-449a-90ff-3be6d084032e<br /> ONBOOT=yes<br /> DNS1=8.8.8.8<br /> <br /> #IPADDR=192.168.0.134<br /> #NETMASK=255.255.255.0<br /> #GATEWAY=192.168.0.1

Viewing all articles
Browse latest Browse all 19115

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>