streeter

Shouldn't make any difference, unless it's faulty. Try unplugging all the cables, then plugging them back in to dirfferent ports on the switch (in case one is in an uplink socket - this should be marked). You will need the gateway address when you want to access the internet... Chris

Or you have one cable plugged into the uplink socket of the hub?

Just happen to be sat here... So your network cards are working OK - the problem lies between the machines. (assume you don't have another firewall installed, perhaps on windows). Check the cabling / hub is switched on... If you can try a crossover cable, that will eliminate the hub and existing cables. Is it possible one of your cables IS a crossover? That would also stop it working. chris

>>The command iptables -nvL >>command not found Means theres no firewall - OK for now. eth0 looks like it's set up OK - where are my ping results? :) The routing table is good. Again, though your resolv.conf is wrong - should contain the same DNS addresses as windows, it won't stop PC->PC comms. Chris

What output do you get from the query modem dialogue? Chris

It's very encouraging, all these new Linux users - we'll soon be able to TAKE OVER THE WORLD HAHAHAHAHAHA!!! Ok - you need to be the root user (administrator) to be able to run system commands, so in the console, type su <enter> followed by your root password at the prompt. 7- Enter a hostname - anything you like. "linux" will do. You don't need hotplugging unless you are using a laptop - turn it off. The DNS setting should be the same as on your windows machine, though that will not stop the PCs talking to each other. (/etc/resolv.conf is the file that should contain the DNS setting once configured correctly). The rest should be OK. Then reboot (you don't normally need to reboot with Linux, but it's easier than explaining what to type etc..). Become root as above and post the results of the commands I asked for above. Do the pinging - on the LINUX box, type: ping -c 4 192.168.0.2 This will tell you if the linux network card is working (or not...). And on the WINDOWS box, type ping 192.168.0.1 This will tell you if the windows network card is working. Then try pinging each PC from the other. Post results. Chris

You need to open ports 6881-6889, now I don't use Mandrake wizards, because of the potential for them to mess up, (or bittorrent for that matter) but I expect that if you go to the Mandrake control center (mcc)->security->firewall and choose advanced, you could type in 6881:6999/tcp. And it may all work... Chris

Prerequisites for any net problem (for you and anybody else with a problem reading this): Please post output of "ifconfig", "iptables -nvL" , "route -n", and contents of /etc/resolv.conf. If you post this info, we can almost certainly help. In particular, I too have a satellite connection, from Central point, using Astra - I connect through Linux. What provider do you use? Can you ping your Linux network card from the Linux box and the windows card from windows? If above works, try connecting machines together directly with a crossover cable if you have one. Chris

Do a search for easyurpmi on this forum Chris

You say you need to configure the IP address of Mandrake to 10.0.0.2, then you try to access the same address - what you are doing here is trying to access your own computer, not the modem.... Try typing 10.0.0.1 into your browser - I expect that is the address you need. If not, have a look at the manual. Chris

Have a look at http://www.netfilter.org/documentation/ind...mentation-howto More info needed - you don't say how far you have got (ie what works so far), how you connect to the net, do you use public IP addresses or NAT etc. The concept is : Set up 2 NICs with different network addresses Enable packet forwarding Set up firewall Chris

PS - step by step guide: 1) Learn all about networking 2) Learn all about Linux 3) Set up your network :D Seriously, there are howtos out there on the net, but a little background knowledge goes a long way - a step by step guide is not really possible in a forum - we don't have the time, and each case is a little different... Chris

Read the posts again - you don't set the IP address to 192.168.2.0 - this is what is known as the network address - it describes the numbering policy for the entire network segment. Your IP addresses should be: eth0 192.168.1.104 eth1 192.168.2.1 windows 192.168.2.2 All subnet masks should be 255.255.255.0 Just as an exercise to make sure it is not Mandrakes wizards messing things up, don't use them to set the IP addresses - type the following as root: ifconfig eth0 192.168.1.104 up ifconfig eth1 192.168.2.1 up Once you have this set up, try typing (from both computers - leave out the "-c 4" on windows) ping -c 4 192.168.1.1 You should get an output similar to: 64 bytes from ap (192.168.1.1): icmp_seq=3 ttl=30 time=1.47 ms If this works, your network is OK. Next try accessing the router's set up - does it work now? If not, what command are you using? Let us know how you get on Chris

Yup - /etc/urpmi/proxy.cfg Might look something like: http_proxy=iproxy.work.ch:8080 ftp_proxy=iproxy.work.ch:xxxx Your IP addresses /hosts and ports may differ Try commenting them out or deleting them. Chris

As Ixthusdan says - run menudrake. Make sure the command entry corresponds to where the xmule binary is installed - you can find this by typing "which xmule" at the command line. Will be something like /usr/bin/xmule . Assuming you are logged in as a user, not root in the console. The kicker is a bit of a red herring - this appears whenever you click on an entry in the menu, and stays for a pre-set time - adjustable in the control panel. Chris

I would rather have a windows PC masqueraded behind a (well set up) Linux firewall (double security!), but you do have a point, assuming the ports (or a hub/switch) are there, and this isn't a learning exercise/necessary. Why didn't I spot this much simpler answer??? Chris

Have seen something similar a long time ago - think it something to do with a cd drive or hard drive , but cannot remember the exact details. If you press <control, alt, F12> at the same time you might get a clue (does MDK10 log events here as standard? I upgraded, so am not sure) - I certainly remember a whole list of repetative disk read failures logged here. Alternatively, check the logs for any odd behaviour under /var/log Please also clarify: when you issue a command, does your PC freeze permanently, or for a period, then return to normal? Also, do you get the same problem logged in at a terminal screen, i.e. press <control, alt, F1>, log in and issue a command. Chris

eth1 (and your other PC) MUST have a different network number from eth0, eg 192.168.2.0 instead of 192.168.1.0 . Network number in this case is the first 3 numbers (octets) of the IP address. Your Linux PC will then be able to route packets between the 2 networks. So change eth1 to 192.168.2.1 and your Windows PC to 192.168.2.2 and it may all start working. leave eth0 alone. Phew - not awake enough to look through and follow all that iptables output, so do above first - if it doesn't work, we can look at the firewall then. Please post output of "iptables -nvL -t nat" if it doesn't work. Chris

Also, if the new kernel source you are using is not from Mandrake - ie a plain, vanilla kernel, you may need patches, depending on your hardware/requirements Chris

1) Your old config should be in /boot - the file will be called config-2.6.xxx. Copy this to your new kernel source directory, rename to .config and type "make oldconfig". Rename any other .config file as a backup. 2) After you compile the new kernel, you will also compile and install the new modules to go with it. 3) Things can go wrong - the main thing to do is make sure you keep the old kernel intact and bootable - ensure there is an entry for it in lilo.conf or the grub equivalent if you use that, then you can just revert to your old kernel. Or perhaps a copy of knoppix if you know what you are doing. Perhaps the best thing to do is to not change/remove too much from the kernel in one go - the speed difference will probably not be noticable anyway, and you can always recompile again later when you are happy - perhaps just change the processor type on your first attempt. Good luck ! Chris

If you open a console and type su (lower case) you will be prompted for the root password. Then all commands typed in that console are run as the root user. Of course, you need to know what those commands are called... The other way is if you choose an option from the menu that needs root privilages, like install new software, or running mcc (mandrake controle centre) then you will be prompted for the password with a graphical dialogue box. The KDE control centre has a button at the bottom for gaining root if you need to alter anything, in this case the login manager. Again - in Linux (and any other OS for that matter) it is generally a bad idea to log in fully as root (administrator) - you can do a lot of damage... Chris

It's a bad idea to log in as root - better to su at a command prompt. However (assuming you use KDE), if you log in as a normal user, go to "start"->system->configuration->configure your desktop (launches the KDE control center) and choose the system->Login manager you can set it up from there. Chris

Have a look in /var/log - should keep you busy for a bit. The file you need is called dmesg. Chris

Might sound daft, but as it's a new board - has it got a cmos battery jumper? It is set? Chris

Whoops Gowator- typo :) - that should be "iptables -nvL" - order is important in this case. Chris