MEPISThis forum is for the discussion of MEPIS Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just installed the newest SimplyMepis, looks great! Everything was configured from the start except my wireless card. I set up NDISWRAPPER to work with my D-Link DWL-G510 on the Marvell W8300 chipset and that seemed to work with my DWL-624 router.
However, when I try to load a page in firefox, it just times out when resolving the domain. Obvious DNS issue, but where? I can log in to my router admin page - 192.168.0.1 - without a hitch so are there any settings I should change there or in the Mepis control panel? If I use DHCP or manually input the settings, I get the same result.
I'm using a managed connection, no wep or wpa.
It's late so I'm sure it's necessary to include more info than I've included to diagnose this, but I'm hoping it's an easy fix, and if not... I'll post it tomorrow.
Here's my Lan:
DHCP Client Connected
I've posted this question on the mepislovers.org forum and I was told to guarddog firewall is the reason why I can't connect to domain names. If this was the case why can I login to my router address - 192.168.0.1 - as I assume this is connecting through port 80. I am able to ping my wan IP 65.7.xxx.xxx so I believe there is something I'm missing.
Right now I'm using DHCP, if I use manual settings what is the broadcast iP supposed to be, default? 192.168.0.255?
Ok, disabling the firewall didn't do anything for me. the solution seems obvious to you guys but to me, I just need help putting it all together. Here's all the info out on the table. Hopefully this will yield success.
Here's the output of netstat -rn:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
0.0.0.0 0.0.0.0 0.0.0.0 UG 0 0 0 wlan0
...something seems off here?
Here's the output of cat /etc/resolv.conf:
....it looks like my router has become my name server?
Here's my setup in MEPIS OS Center > Network Interfaces:
lo ip: 127.0.0.1
eth0 ip: down
wlan0 ip: 192.168.1.100
wireless is: on wlan0
ess id: xxxxxx
#then i have none of the following checked
nwid/domain (cell id)
[x] Use DHCP for IP
Timeout: 15 sec
Westell Wirespeed DSL Modem >
D-Link DWL-624 Router >
Now I have one desktop hardwired (XP) and 3 computers wireless: Desktop w/ MEPIS using DWL-G510 PCI Card(suspect in question), IBM Laptop (XP), Compaq Laptop (win2000)
Sincerely, thanks for your time everyone in diagnosing this for me.
The router runs on a default IP address of 192.168.1.1 and can be accessed using your favourite web browser by pointing it to http://192.168.1.1. By default, the inbuilt DHCP server is operational and will assign your computer a suitable IP address if configured to accept one (described within the quick start guide). The unit does not support access via other means, such as telnet.
No, the thing is every computer works, besides my Linux box running MEPIS. I have just set up this computer with MEPIS and am just trying to get the same settings I have on my windows boxes (which detected it automatically btw) running with MEPIS.
I do believe that my wi-fi is supported because it's known to work with ndiswrapper for others. And also, like I said, I can connect to my router. Also, using kWiFiManager, when I scan for networks I am able to see my router's SSID and it appears to connect.
Here's my ifconfig output:
Link encap: Local loopback
inet adddr: 127.0.0.1 Mask: 255.0.0.0
inet6 addr: ::1/128 scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric: 1
RX packets: 10 errors: 0 dropped:0 overruns:0 frame:0
TX packets: 10 errors:0 dropped:0 overruns: 0 carrier:0
collisions: 0 txqueuelen:0
RX bytes: 500 (500.0 b) tx bytes:500 (500.0 b)