MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello to all. I just installed Mandrake 10.1. I decided that this was the linux to use as a newbie. While I managed to install it with little problem. I am having a few problems. I'm not completely new to Linux, I have played with it on other boxes of my friend, and know my way around the terminal a little bit. But the whole networking thing has me stumped, as does installing any kind of software where I can find it.
First I don't have internet access on my linux box, because we are running a wireless network. My box would be using a Linksys WUSB54G card. I was wondering if anybody could help me with getting this card to work, if that is possible.
I am also having a problem getting Mandrake to connect to my Windows XP computer, via a crossover cable. I have not been able to find Samba , as it is said to be included in the install, and I installed LinNeighborhood, but I have also been unable to find that program either.
So if anybody could possible help me, it would be much appreciated.
Dom
I'm also using KDE v.3.2
Last edited by eaterofsmoke; 12-29-2004 at 02:18 AM.
did you already properly set up yout network card?
First, you need to set up a kernel driver for the card because its a wireless / WiFi thingy - maybe the HCL Forums plus a little google might help, for I have no experience with a Linksys WUSB54G.
Done this, you have to ifconfig (see man page for that, too) your eth interface - usually, it is eth0.
Example:
Code:
ifconfig eth0 inet addr 192.168.8.15 netmask 255.255.255.0 broadcast 192.168.8.255 up
If you do not use DHCP, add your nameserver to the file /etc/resolv.conf - Example:
Code:
nameserver 192.168.8.254
If you use DHCP, you have to ask Google again, I do not use this in my little home network. In Knoppix, there is a nice utility "netcardconfig", I think it is a script. If you try to analyze this, it might give you some enlightenment.
Got it? OK, then try to ping around - first local, then in the Internet. If local works, but not the Intenet, there may be something wrong with your nameserver, try numerical IP addresses you know in the Internet. If this succeeds, use a different (or the proper) nameserver.
Well, usually you configure your router as a DNS proxy; if you have not, choose the DNS address your ISP provides.
Giving "an address that works" is a hard thing, because this specific DNS server will be contacted every time you have to resolve an address - if it is "far away", your performance will be poor and this will yeild high long-distance traffic.
So, best is to choose the DNS server your ISP provides.
There should be. The router I use (SMC) has a configuration option "primary DNS Server" and "secondary DNS Server" where I put the IPs of two DNS server my ISP provides. Alternatively, you can take those and put them into your /etc/resolv.conf
Code:
nameserver <here goes the numerical IP address of the DNS server you want to ask by default>
Got it?
Using the router DNS "proxy"
makes it easier to change the default DNS server for the whole network
Well, just that you can keep all the DNS queries in you local network and do not have to open the DNS port (destination: 53) for outgoing DNS connections.
That's not too much of a problem to keep it open, but it is always a good idea to minimize the number of ports that can bypass your firewall.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.