Connecting to a wireless router Netgear WGR614 with firewall enabled using DSL
I am installing Damn Small Linux version 4.2.5 on a computer that has previously run Xandros just fine using a Linksys router (not wireless capable). I now use a Netgear WGR614 for its wireless capability, but cannot get connected to the router through an wired ethernet connection. I do have the firewall enabled on the router.
The computer is running an AMD Duron 1.2 MHz with 64 Meg cache. The network card is an Intel Ethernet Pro 100 and still seems to be OK.
I am ready to dump the Xandros if I can just get DSL installed properly. I am still feeling my way into Linux (hence the Xandros) so detailed instructions (and/or patience) will be greatly appreciated.
Some additional info
Router MAC Address Use Default Address
Account Name WGR614v6
Firmware Version V1.0.11_1.0.7NA
Newer version (version 2.0.19_1.0.19) is available (dated May 8, 2007) for download.
MAC Address 00:14:6C:9B:AA:2C
IP Address 192.168.1.1
IP Subnet Mask 255.255.255.0
Opened a browser and tried to contact the router directly by typing in the IP Address (as directed by the Netgear setup directions) but got a message--'Connection refused'
I have another computer that does successfully connect to this router using DSL. This box has Window XP installed but I use a DSL CD to boot it up and connect to the internet.
How did you try to connect to that router? Via LAN?
Is your computer set to getting its address via dhcp from the router? - It should!
Is your computer plugged into one of the 4 LAN-Ports? (The 5-th slightly separated one is the WAN where your "internet" connection goes to)
I have exactly the same model (version 6) and it works flawlessly.
The firewall should not be the problem - unless it was misconfigured. But you should still be able to get to the routers admin-interface.
Before I upgraded the firmware the default address to get to the admin-interface was 192.168.1.1
After the upgrade the default address was 10.0.0.1
Yes I am connected via a cable to one of the LAN ports and the computer is set to get the IP address by DCHP.
I am also surprised that it doesn't work since (as noted in the edited version of my first post) it does work with my other computer.
I have tried to get to the admin-interface but cannot get connected, so I am puzzled.
Thanks for the quick response.
I always wanted to try it - downloading the "current" now and will test it first in virtualbox.
My connection is really bad - will take some time.
Booted in VirtualBox - no problem.
Burned it to CD - booted - no problem - it found my network-card and used dhcp to get an IP - and it worked just like that.
One thing: maybe it did not recognize your network-card? During boot you should see a line saying:
Network device eth0 detected, Broacasting for IP: done
You can also check with: /sbin/lsmod if the module is loaded
mine is called: 8139too
Another thing to look at would be:
right below that
If you have a narrow netmask there - and configured the address-reservation (by mac) then your computer might not be given an address.
Check starting IP/ending IP
I have the exact same router connected to laptop, server and desktop. Server and laptop is wireless. When I tried to install a new OS (Debian Lenny) on the laptop I couldn't get the wireless to work. I could ping the server (also wireless) but couldn't ping the desktop (wired) or the router. I fiddled around with the wireless drivers for days. Then I noticed that the server couldn't get on the net (though I could log in from my desktop). This problem might very well have existed for a couple of months as my server is mainly for internal use and I hadn't used the laptop for a good while so I don't know when it arose. If I hadn't gotten the problem with a laptop I might not have noticed for another couple of months. But, when trying to fix the laptop I got the advice to reset the router. I tried but it didn't help. I then upgraded the firmaware, because, well, I hadn't done it (ever) and now I already had all the settings written down so I might as well get it done. Everything worked like a charm after the firmaware update. Beat's me why but it did. If your firmaware is outdated I'd give it a go.
Yep - now that I read this: the reason for doing the mentioned firmware-upgrade was some wierd problems.
I did not want to sort them out - since I had not changed anything on my network, the only option was the router.
Made the upgrade - no problems ever since.
Updated firmware--still no luck
Jomen and Count Zero: Thanks for all your help. Here is a quick update from my end.
I did update the Netgear firmware but still don't connect to the internet. I do see the port #2 light up on the router, so I think I have a good connection and the router recognizes that a device is attached.
I think the network card is good. The following lines are from the DSLpanel dmesg file
eth0: Intel Ethernet Pro 100, 00:90:27:BD:07:91, IRQ #3
Primary Interface chip: i82555 PHY #1
General Self test: passed
Serial sub-system self test: passed
ROM Checksum self test: passed
Another thing to look at would be:
right below that
last one first:
You would type that in a terminal-window and hit "Enter" ...
About "mastering the file layout":
I have always found it hard to use the graphical file-managers and from the beginning always used "mc" (midnight-commander) for this.
You open a terminal - type mc - and you can navigate easily using the keyboard (or mouse) - wether on console or in an xterm does not matter.
I love it!
You will probably have to install it first.
If that tells you something: it is alike to the back then popular program "nc" (Norton Commander) for Windows (3.1) - simple but efficient.
On the system-message during boot:
If you see a different message than I do then this can have different reasons:
- you use another version than I do
- it takes longer for you and the process is backgrounded to continue the boot-sequence
- something else
That is why I asked for the output of ifconfig
Since you know that your router is on 192.168.1.1 you could try to set a static address:
ifconfig eth0 192.168.1.10/24 up
and then to try to get to the router.
(is it still saying 192.168.x.x ? After the update the default for me was 10.0.0.X)
I was just whining about the arcane (to me, anyway) UNIX file system. I have worked a little with Midnight Commander in Xandros and DSL has emelfm that is similar. It just takes me a long time to climb out of the gravity well of my ignorance.
I did find a useful resource page on a blog by Peter Upfold.
Is this a command that must be executed by root?
The LAN Setup is still showing tcp/ip as 192.168.x.x.
I did also check my router firmware to make sure it updated. It now shows a firmware version: V.2.0.19_1.0.19NA. I am confident it did update.
For other newbies, I also found a good listing BASH commands (An A-Z Index of the Linux BASH command line) at Linux bash MAN pages.
/sbin/ifconfig is the full path - it works as normal user without parameters
as root you can just use ifconfig -and also with parameters like:
ifconfig eth0 192.168.1.10/24 up
But there is an easier way in DSL:
from the menu:
Setup --> Net Setup --> netcardconf
set your interface "eth0"
set it to "dhcp-broadcast=yes"
check: save config
But rigth there it became clear what was already to be seen from /sbin/ifconfig
There should have been an interface name eth0 in addition to just lo
DSL did not find your network-card - it is not active and thus - nothing will work.
This might be a problem of you having an outdated version of DSL - or the problem is that DSL uses a 2.4.31 kernel (mine does) and this just does not yet support for your relatively new NIC.
Don't know - but I suspect the latter.
What network-card do you have anyway?
The intel ethernet pro 100 should work.
as root issue:
also the output of
would be helpful
maybe a suitable module is there and just the autodetection did not work. You could then insert it "by hand"...
network Card is suspect
Joman, I successfully booted another old computer with DSL and ran lspci and now I see what you mean about the eth0 being missing.
For now, I think I will suspend my efforts on this box. It is getting unstable (overheating) and now the network card is questionable. I think I need to address these hardware issues and then come back to DSL. I need to do some more basic Linux learning too.
Thank you so much for the patient help you have given me. I am confident that we would have worked out any non-hardware problems so I look forward to coming back to DSL.
One more thing to try - chances are it will not work though under the conditions you describe.
lsmod should have shown (among the others) a module named e100 or eepro100 as loaded. This is the module that would be inserted for your brand of NIC.
If it is not loaded you could try to load eigther one with:
Does lspci on that machine even show your network-card?
If it does not show up then there is something not right with eighter the card itself or the electrical connection of the card to the slot it is in.
|All times are GMT -5. The time now is 07:30 PM.|