LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 03-07-2004, 01:47 AM   #1
Rotwang
Member
 
Registered: Jan 2004
Distribution: CentOS
Posts: 281

Rep: Reputation: 30
Question Can't connect to my linksys router


This seems very odd. I have Linksys router like lots of people have- you know how you open your browser and go to 192.168.1.1 to change it's config? I can do that fine from my windows machine in IE, but not from my Mandrake 9.2 box in Konquerer or Mozilla. Browser just hangs. Both boxes are connected to the router, one is on port 2 and the other port 4.

I can get out to exernal sites just fine, and samba works both ways between the two machines.

 
Old 03-07-2004, 08:26 AM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
I'd like to ask a really weird question: What kernel version are you running (uname -a should tell you)?

The reason I'm asking is that I ran into a very similar problem with some of the early 2.6.x kernels. Starting with the 2.6.1 kernel however, I was able to connect again. As far as I can tell, nothing changed except the kernel version. It was configured the same, my firewall didn't change yet I was able to connect again.

You could try taking down your firewall and then trying. It could be that Linksys is trying to connect using a method blocked by your firewall.
 
Old 03-07-2004, 11:16 AM   #3
Rotwang
Member
 
Registered: Jan 2004
Distribution: CentOS
Posts: 281

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by Hangdog42
I'd like to ask a really weird question: What kernel version are you running (uname -a should tell you)?

Yep it was my firewall, thanks. btw here is my kernel version anyway

2.4.22-10mdkenterprise #1 SMP Thu Sep 18 11:46:49 CEST 2003 i686 unknown unknown GNU/Linux

(It's Mandrake 9.2)
 
Old 03-07-2004, 01:15 PM   #4
quantumechanix
Member
 
Registered: Jan 2003
Posts: 47

Rep: Reputation: 15
i have this problem too

i'm using Fedora Core 2 test1, with kernel 2.6.3-2.1.240. i have a linksys router, and i also cannot get to the router's admin page (192168.1.1). i have checked and turned off my firewall, with no luck. also, i cannot ping many web sites. some websites like www.mwave.com time out in the browser. a windows box on the same router has none of these problems. i have been trying to figure this out for a week now. everything worked fine with Fedora Core 1, RH 8/9...

any help would be greatly appreciated.

below is some info from my system. my primary DNS is correct at 207.69.188.185. the nic card seems ok. some of the info is redundant, i just wanted to be thorough. if there's something i missed, please tell me. thanks again
##################################################
[root@localhost root]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:07:E9:B3:7C:8D
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::207:e9ff:feb3:7c8d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6152 errors:0 dropped:0 overruns:0 frame:0
TX packets:5518 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4187565 (3.9 Mb) TX bytes:651227 (635.9 Kb)

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:1969 errors:0 dropped:0 overruns:0 frame:0
TX packets:1969 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2724674 (2.5 Mb) TX bytes:2724674 (2.5 Mb)

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)

##################################################
[root@localhost root]# system-config-network-cmd
DeviceList.Ethernet.eth0.AutoDNS=true
DeviceList.Ethernet.eth0.Hostname=www.earthlink.net
DeviceList.Ethernet.eth0.HardwareAddress=00:07:e9:b3:7c:8d
DeviceList.Ethernet.eth0.Type=Ethernet
DeviceList.Ethernet.eth0.Netmask=255.255.255.0
DeviceList.Ethernet.eth0.BootProto=none
DeviceList.Ethernet.eth0.Device=eth0
DeviceList.Ethernet.eth0.OnBoot=true
DeviceList.Ethernet.eth0.IP=192.168.1.100
DeviceList.Ethernet.eth0.DeviceId=eth0
DeviceList.Ethernet.eth0.AllowUser=false
DeviceList.Ethernet.eth0.Gateway=192.168.1.1
HardwareList.Ethernet.eth0.Status=ok
HardwareList.Ethernet.eth0.Name=eth0
HardwareList.Ethernet.eth0.Type=Ethernet
HardwareList.Ethernet.eth0.Card.ModuleName=e100
HardwareList.Ethernet.eth0.Card.IRQ=11
HardwareList.Ethernet.eth0.Description=82801BD PRO/100 VE (LOM) Ethernet Controller
ProfileList.default.ActiveDevices.1=eth0
ProfileList.default.HostsList.1.IP=127.0.0.1
ProfileList.default.HostsList.1.Hostname=localhost.localdomain
ProfileList.default.HostsList.1.AliasList.1=localhost
ProfileList.default.DNS.SecondaryDNS=207.69.188.186
ProfileList.default.DNS.SearchList.1=earthlink.net
ProfileList.default.DNS.Domainname=
ProfileList.default.DNS.Hostname=localhost.localdomain
ProfileList.default.DNS.TertiaryDNS=207.69.188.187
ProfileList.default.DNS.PrimaryDNS=207.69.188.185
ProfileList.default.Active=true
ProfileList.default.ProfileName=default
##################################################
[root@localhost root]# iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
##################################################
[root@localhost root]# cat /etc/resolv.conf
; generated by /sbin/dhclient-script
search earthlink.net
nameserver 207.69.188.185
nameserver 207.69.188.186
nameserver 207.69.188.187
##################################################
[root@localhost root]# more /etc/hosts*
::::::::::::::
/etc/hosts
::::::::::::::
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::::::::::::::
/etc/hosts.allow
::::::::::::::
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
::::::::::::::
/etc/hosts.deny
::::::::::::::
#
# hosts.deny This file describes the names of the hosts which are
# *not* allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
# The portmap line is redundant, but it is left to remind you that
# the new secure portmap uses hosts.deny and hosts.allow. In particular
# you should know that NFS uses portmap!
##################################################
[root@localhost root]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
##################################################
[root@localhost root]# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.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
##################################################
 
Old 03-07-2004, 05:37 PM   #5
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
Quote:
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
This strikes me as a bit odd. I'm not sure why you would have two entries like this for eth0, particularly since the second (169.254.0.0) looks like a real IP address.

Also from your ifconfig
Quote:
inet6 addr: fe80::207:e9ff:feb3:7c8d/64 Scope:Link
Are you running IPv6? I know it is supposed to work with IPv4 as well, but I wonder if this is part of the problem.
 
Old 03-07-2004, 07:09 PM   #6
quantumechanix
Member
 
Registered: Jan 2003
Posts: 47

Rep: Reputation: 15
to my knowledge, i'm not running IPv6. i've checked the system-config-network and it is unchecked. also, my eth0 cfg shows it disabled:

[root@localhost root]# cat /etc/sysconfig/networking/devices/ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
USERCTL=no
PEERDNS=yes
TYPE=Ethernet
IPV6INIT=no
DHCP_HOSTNAME=www.earthlink.net
HWADDR=00:07:e9:b3:7c:8d
IPADDR=192.168.1.100
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
#############################################

could there be some config file that still has it enabled?

also, i have no idea where the entry "169.254.0.0" came from. how do i delete if? there are a lot of files in /net/proc/ that look to have info about the routing tables. thanks for your help

Last edited by quantumechanix; 03-07-2004 at 07:10 PM.
 
Old 03-08-2004, 07:35 AM   #7
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
I'd use grep in some of your startup directories and see if you can find out which scripts are using eth0. That might reveal where the other IP address is coming from.

Also, if you look at your ifconfig you see this:
Quote:
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)
It sure looks to me like something is using IPv6 but isn't seeing packets. Maybe you can take down sit0 and see if that makes a difference. Of couse it would be nice to know what sit0 is. Do you know or does lspci show anything interesting?

Of course, I'm doing a bit of guessing here as to what may be wrong. If anyone else has any ideas, please chime in.
 
Old 03-08-2004, 05:58 PM   #8
quantumechanix
Member
 
Registered: Jan 2003
Posts: 47

Rep: Reputation: 15
from google, i found:
Simple Internet Transition (SIT): used as an IPv6 over IPv4 tunnel device

it doesn't seem to be applicable except for people on some college campuses. i think it is an "Internet2" thing.

i looked through my bootup scripts and found nothing. i also plugged directly into the cable modem, bypassing the router, and the problem was still present.

i haven't found anything in my system concerning the weird ip address 169.254.0.0. although, i did try to delete it using the route command ( i don't remember all the options i used). however, when i restarted the network connection the entry REAPPEARED!

this is becoming ridiculous. is there something akin to a debugger that i can run to follow a request to an ip address?

also, let me say thanks HangDog42. i really appreciate your help
 
Old 03-09-2004, 05:45 PM   #9
quantumechanix
Member
 
Registered: Jan 2003
Posts: 47

Rep: Reputation: 15
i posted this same solution on thread http://www.linuxquestions.org/questi...hreadid=154806

i found the problem. it is with Explicit Congestion Notification (ECN). if you are having these problems check whether ecn is on. to do this, on the command line type:

cat /proc/sys/net/ipv4/tcp_ecn

if this returns "1" then ecn is on. to turn it off type:

echo 0 > /proc/sys/net/ipv4/tcp_ecn

now try and go to www.mwave.com

Last edited by quantumechanix; 03-09-2004 at 08:56 PM.
 
Old 03-09-2004, 07:26 PM   #10
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
That's a nice piece of detective work.....What lead you to ECN? And, of course, can you now connect to your linksys router?
 
Old 03-09-2004, 09:28 PM   #11
charon79m
Member
 
Registered: Oct 2003
Distribution: Just about anything... so long as it is Debain based.
Posts: 297

Rep: Reputation: 30
APIPA is your 169 addressing...

Automatic Private I P Addressing is what that 169.254.x.x addressing is. It's an industry standard for when you system dosen't get a DHCP address it automatically assigns itself a 169.254.x.x address.

Most of the Win poeple will have seen it before... Most of the *nix people never see the 169 addressing scheame.

I don't believe it's a true RFC standard, though I know it's mentioned.

Cheers,

MrKnisely
 
Old 03-09-2004, 09:42 PM   #12
quantumechanix
Member
 
Registered: Jan 2003
Posts: 47

Rep: Reputation: 15
charon, thanks for that info. now, everything is explained.

hangdog, i found the solution at http://lists.debian.org/debian-user/.../msg04129.html

and, yes, i can now connect to my router. why would the 2.6 kernel enable ecn by default?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Linux can't connect to internet with DHCP through Linksys wired router ruslan40321 Linux - Networking 9 03-30-2008 02:08 PM
Setting up router (Linksys WRT54G v5) to connect to internet (SUSE 9.3) Jongi Linux - Networking 2 11-15-2005 01:33 PM
Non-DHCP connect on a Linksys WRT54G router Zyk Linux - Wireless Networking 1 07-11-2005 05:13 PM
Linksys router lets Linux connect, but not windows Fear58 Linux - Networking 2 07-15-2004 11:24 PM
MDK9.1 can't connect to linksys router (to ADSL) A.J.Gibson Mandriva 14 01-27-2004 06:52 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 09:40 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration