LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   No HTTP traffic after changing to a new router (https://www.linuxquestions.org/questions/linux-networking-3/no-http-traffic-after-changing-to-a-new-router-323983/)

jamesf303 05-16-2005 07:51 AM

No HTTP traffic after changing to a new router
 
Hi Linux Dudes,

I have a fedora (FC3) box that I am setting up to run MythTV.

All was working fine with my current ADSL router (Origo 8400) - My win XP pc could talk to the internet, the fodora box could talk to the internet and the two boxes could talk to each other (Samba and HTTP (apache on the FC3 box)

I got a new router (SafeCom) that has wireless. I have sucessfully set up the router for wired and wireless on my XP pc but the FC3 box wont play along.

The FC3 box gets it IP etc through DHCP OK. I can ping internally (the router and my XP pc) and also sites on the internet (i.e. google.com).
When I try to access a webpage in Firefox (or Lynx) it just sits there... The DNS lookup seems to work ok because firefox shows "Looking up somesite.com" then "Connecting to somesite.com" but no actual HTTP traffic is transferred.

Interestingly, wget seems to be able to grab the front page from google, yahoo etc with no problems.

My initial thoughts were that it might have been something to do with having set up Fedora Linux with a 10.0.0.5 IP addr allocated by the my old router (origo) but now its being allocated a 192.168.1.x ip address by my new router.

With that in mind, I set up my new router to allocate 10.0.0.x IP via DHCP. I then used KDE network settings dialogue window to deactivate and re-activate the eth0 interface thus getting re-DHCPed.

Still no luck with the old IP address (10.0.0.5). Looking at the o/p from ifconfig I could see that the broadcast address was different:

OLD:

eth0 Link encap:Ethernet HWaddr 00:11:D8:3D:5F:1D
inet addr:10.0.0.5 Bcast:255.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::211:d8ff:fe3d:5f1d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:99478 errors:0 dropped:0 overruns:0 frame:0
TX packets:76101 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:92131578 (87.8 MiB) TX bytes:5123061 (4.8 MiB)
Interrupt:11 Base address:0xe000


NEW:

eth0 Link encap:Ethernet HWaddr 00:11:D8:3D:5F:1D
inet addr:10.0.0.5 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::211:d8ff:fe3d:5f1d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:99254 errors:0 dropped:0 overruns:0 frame:0
TX packets:75976 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:92115389 (87.8 MiB) TX bytes:5115003 (4.8 MiB)
Interrupt:11 Base address:0xe000


I used ifconfig to force the bcast to the old value (255.255.255.255) but (surprise surprise) that didn't work either.

Just out on interest, I whacked in a Knoppix (3.7) CD that I have and rebooted. When Knoppix came up I was able to use Konqueror to browse the net etc. This proves to me that the issue is not with the router/linux combination but with the FC3 settings.

In case you can't tell, I am not exactly a linux expert (I'm not too bad though :) ) so any pointers or ideas on how to debug this problem would be greatly appreciated!! Maybe there is some file in which network settings were hard-coded at install time?? or a log to check that might give useful information?


Thanks in advance,

james

camorri 05-16-2005 10:42 AM

Just a guess, do you have a default route set? Log as SU and do a "route" command. If you have a default route set, it will be listed. If not, set one and try again.

Here is an example of route output.

# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

jamesf303 05-16-2005 10:57 AM

Hi Cliff,

Thanks for the pointer - I'll have a check when I'm back home tonight.
It seems odd that it would work with one router but not the other though??

James

stevie_velvet 07-27-2005 02:11 AM

fedora\rhel & Firefox\Thunderbird & 3 Tricks

(1) Try disabling IPv6 if enabled

(2) Ensure SELinux & Firewall\IPChanins are disabled, especially if you don't know how they work

(3) ensure that your DNS \ \etc\resolv.conf has at least 1 DNS entry of yuour ISP, NOT your Router, even if Windows doesn't

(4) If all else fails, download the latest RPM for your app

poop21 11-11-2006 07:44 AM

Its probably that the browser defaults to a proxy server on port 8080. Just remove the proxy and you should be fine! Not sure where on the firefox settings but should be easy enough to find (worked for me btw)

UhhMaybe 05-25-2007 11:57 PM

Are YOU able to see the NEW Router in YOUR browser...to set up the NEW Router through the web page? If Yes, then delete the old router settings. Then set up the NEW Router through YOUR browser. After rebooting, try the command line interface with "ifconfig -a", "ifconfig", "lspci", "lsusb", "lsmod", "modprobe", "route -n", "ethtool", and "dig". Also the man pages for "iwconfig" and "ethtool". Still troublesome, try here...http://www.tldp.org/HOWTO/HOWTO-INDEX/howtos.html


All times are GMT -5. The time now is 04:23 PM.