Horty

Thanks for the link, streeter. I'll definately use it. For the moment, though, I'm going to sort out what has happened to the Shorewall rules, policies, etc. If Shorewall is supposed to simplify iptables, I'd hate to configure iptables itself! Might get firestarter. Horty

Unfortunately still not working. I hashed out this line in /etc/shorewall/rules: REDIRECT loc 3128 tcp www - and this line in masq: ppp0 192.168.x.x/255.255.255.0 but still no go, and new REDIRECT line added in rules on reboot.

Thanks for the reply, streeter. I (briefly) turned off the firewall, and was able to browse each computer again, so I assume that the redirection to squid rule which was added to the firewall was the culprit. I had a look in /etc/shorewall/rules and found the redirection to squid, which I disabled. Is there anything else I have to disable?

Hi all. I have a small peer to peer network consisting of one XP box and one MDK 10 OE box. Both systems are configured with static ip addresses and could see each other no problems. Until tonight that is. I decided it was time to play around with connection sharing, and tried enabling it with the supplied MCC wizard. The result being that connection sharing didn't work (I'll sort that out later), and I can no longer see the other computer or its shares. I've tried disabling connection sharing through the wizard, but to no effect. I also disabled squid, also to no avail. No luck with ping either. My network is a simple crossover cable connection, while my internet connection is dial up. What can I do to get my shares back? Thanks. ipconfig as follows : eth0 Link encap:Ethernet HWaddr 00:00:21:E0:64:FD inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::200:21ff:fee0:64fd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1981 errors:0 dropped:0 overruns:0 frame:0 TX packets:2350 errors:2063 dropped:0 overruns:0 carrier:4124 collisions:35060 txqueuelen:1000 RX bytes:289330 (282.5 Kb) TX bytes:523385 (511.1 Kb) Interrupt:11 Base address:0xe800 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:2475 errors:0 dropped:0 overruns:0 frame:0 TX packets:2475 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:195813 (191.2 Kb) TX bytes:195813 (191.2 Kb) ppp0 Link encap:Point-to-Point Protocol inet addr:203.214.106.205 P-t-P:203.89.203.11 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:576 Metric:1 RX packets:1723 errors:0 dropped:0 overruns:0 frame:0 TX packets:1339 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:679392 (663.4 Kb) TX bytes:141313 (138.0 Kb) [moved from Software by spinynorman]

OK. Thanks for that. I"ll stick it in a spare partition........just in case......!

I've been using Mdk 10 OE for a few months now, and after a lot of tinkering, experimenting and researching, I've nearly got it set up just nicely. I now have access to a copy of 10.1 OE, and I am wondering if it is worth the hassle upgrading to it. Is 10.1 a huge improvement over 10? Can I easily upgrade 10 to 10.1, or do I have to do a fresh install. Thanks.

Well, it certainly has to be in the root directory (just found out by trial and error). I noticed from a bit of googling that names different to bootsect.lnx have been used, so i'll try those.

bvc, I'm assuming its a case of making up a bootsect.lnx for the second distro, copying to a different folder on the primary drive to that of the first distro's bootsect.lnx, and telling ntloader where to find it. Or does bootsect have to be on the root folder of the primary drive/partition?

Thanks guys. Thats actually how I am booting Mandrake at the moment. (Using grub on the Linux partition). My main reason for the post was because I am adding Suse 9.2, and I assumed it would be easier to add another boot option to lilo / grub if they were in the MBR. Or can you boot two LInux distros from Ntloader? Horty.

Hi all. For about 3 months now, I have dual booted XP and Mandrake 10 OE using Lilo as installed in the MBR of my primary drive. Recently I had cause to boot the Mdk recovery CD in order to make changes to lilo.conf and subsequently reinstall lilo. Upon rebooting and selecting windows from within lilo, instead of staring at the ntloader, I was faced with a blinking cursor on the top left of the screen. I was able to restore ntloader with no hassles, but this meant overwriting lilo. Is there a workaround or fix to this issue? I've done a bit of googling on it, but haven't turned up much. Regards, Horty

Thanks for your reply, Crash. I had no idea that a GUI front end existed for Shorewall. It seems a bit ironic though that Webmin configures Shorewall, which itself configures iptables. Horty

Hi all. I've been able to get my palm to access the internet via Mandrake 10 OE and Bluetooth, but only with Shorewall turned off. I am wondering as to how I can edit one of the Shorewall configuration files (masq.conf?) to do the equivalent to the following commands : echo '1' >/proc/sys/net/ipv4/ip_forward iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE iptables -A FORWARD -i ppp1 -j ACCEPT I have assigned two ip addresses in the 192.168.0.x range to the palm and pc respectively using DUND. Regards, Horty

Thanks for your help, pmpatrick. I've just managed to get the time to try your suggestions, and it worked. I can boot up Fedora. Funny thing is, I got Mandrake to recognise the Fedora boot partition using MCC / diskdrake, and I could browse the partition using Konqueror, but when I next booted into Mandrake, the boot process halted with a message to effect that it couldn't recognise the drive format. I had to edit fstab and delete the code relating to hdc in order for Mandrake to boot again. Ah well. Thanks again for your help. Horty

Thanks, pmpatrick, I'll look into it. Regards, Horty.

Tried your suggestion, Arctic, and same response. Lilo.conf as follows : timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hdb8 initrd=/boot/initrd.img append="devfs=mount acpi=ht resume=/dev/hdb9 splash=silent" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hdb8 initrd=/boot/initrd.img append="devfs=mount splash=silent acpi=ht resume=/dev/hdb9" read-only other=/dev/hda1 label="windows" table=/dev/hda other=/dev/fd0 label="floppy" unsafe image=/boot/vmlinuz label="failsafe" root=/dev/hdb8 initrd=/boot/initrd.img append="failsafe splash=silent acpi=ht resume=/dev/hdb9 devfs=nomount" read-only other=/dev/hdc1 label=Fedora Another thing that I just thought of, is that hdc is a drive that I recently popped into the system (as a FAT drive), and then reformatted to ext3 when I installed Fedora. I haven't mounted the /boot partition in MDK yet. Should I mount this under something like /dev/fd3? I have also included fstab. /dev/hdb8 / ext3 defaults 1 1 none /dev/pts devpts mode=0620 0 0 /dev/hdd /mnt/cdrom2 auto umask=0,user,iocharset=iso8859-15,codepage=850,noauto,ro,exec 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-15,sync,codepage=850 0 0 none /mnt/hd supermount dev=/dev/ide/host0/bus1/target0/lun0/part1,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,kudzu,codepage=850 0 0 /dev/hdc1 /mnt/hdc1 vfat defaults 0 0 /dev/hda1 /mnt/win_c vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 /dev/hdb1 /mnt/win_c2 ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hda5 /mnt/win_d vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 /dev/hdb5 /mnt/win_d2 ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hda6 /mnt/win_e vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 /dev/hdb6 /mnt/win_e2 ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hda7 /mnt/win_f vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 /dev/hdb7 /mnt/win_f2 ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hda8 /mnt/win_g vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 none /proc proc defaults 0 0 /dev/hdb9 swap swap defaults 0 0 Thanks again for your replies. Regards, Horty.

Update. I get this after editing llilo.conf and typing 'lilo' : "First sector of /dev/hdc1 doesn't have a valid boot signature" Hdc is the drive where Fedora is installed. hdc1 is /boot, hdc2 is the swap, and hdc3 is /. Thanks, Horty

Thanks, iphitus. Horty.

I'm keen on trying out FC3, on a seperate drive to MDK 10. I've found this thread; http://www.mandrakeusers.org/index.php?showtopic=5082 , and was wondering if the methodology explained here is the same for installing the latest LInux distros. Horty

OK. Here goes. Please bear in mind that I'm not overly experienced in use of Linux. After installing Samba, Drakwizard (to configure Samba) and Linneighbourhood (Network Neighbourhood equivalent), I found that I couldn't 'see' the Win98 box and vice versa. I also couldn't ping either machine. After a fair bit of research, I gave my Linux box a hostname other than the generic one, and edited /etc/samba/smb.conf in accordance to the guidelines located here : http://www.mandrakeusers.org/index.php?showtopic=16737 . After viewing examples of numerous .conf files posted by people experiencing networking problems, I then edited /etc/hosts, to give the Linux box the IP address and hostname of itself and the Win98 system, and also edited /etc/sysconfig/network to reflect the hostname change of my Linux machine. I also changed the IP address of the Linux box (from 192.168.15.1 to 192.168.0.1) to more closely match that of the Windows box (192.168.0.2). I then turned off Shorewall, tried pinging, and viola! /etc/hosts and /etc/sysconfig/network as follows : /etc/hosts 127.0.0.1 localhost 192.168.0.1 Linux 192.168.0.2 Sempron etc/sysconfig/network HOSTNAME=Linux NETWORKING=yes I got some good info from this site : http://info.ccone.at/INFO/Samba/integrate-ms-networks.html I have posted this purely as an account of what I did to resolve the problems I was experiencing with Samba / networking, and should be taken as such. Any implementation of the procedures outlined above should be taken at your own risk! To Qchem, thanks for your interest in my solution. If there is anything in this post that requires correction, debunking or further explanation, feel free to do what is necessary. Regards, Horty.

It's OK. I ended up getting the two systems to ping, and 'see' each other. The way I did it was a bit convoluted,not very pretty (I am a newbie) and probably not recommended by Linux gurus, so I haven't posted the procedure. I will be happy to post the procedure if anyone is interested (use at your own peril). Horty

I have installed Samba in order to network with a Win 98 computer (peer to peer), and cannot get either computer to 'see' the others shares. When attempting to troubleshoot, I have tried pinging each computer (with firewalls turned off) and either get timed out or an 'unreachable' message. I know that the hardware side of things is OK, because my Linux machine dual boots with XP, with which I have been able to connect to the Win 98 machine. My question is, do I need everything set up in Samba to be able to successfully ping the other machine, or can I fault find the pinging problem without running Samba? Sorry if this is a basic question, but I have done a fair bit of searching in an attempt to resolve this particular problem, and not come up with anything that directly answers the question. Regards, Horty

Thanks again for your help, artee. Forgot to include ls -l /boot in the last post. Here it is: -rw-r--r-- 1 root root 512 Sep 18 16:15 boot.0200 -rw-r--r-- 1 root root 512 Aug 14 03:07 boot.0300 -rw-r--r-- 1 root root 512 Aug 14 03:11 boot.0348 lrwxrwxrwx 1 root root 17 Oct 23 20:59 config -> config-2.6.3-7mdk -rw-r--r-- 1 root root 54087 Mar 17 2004 config-2.6.3-7mdk -rw-r--r-- 1 root root 5032 Feb 19 2004 diag1.img -rw-r--r-- 1 root root 16796 Feb 19 2004 diag2.img drwxr-xr-x 2 root root 4096 Sep 18 15:26 grub/ -rw-r--r-- 1 root root 136149 Aug 14 03:07 initrd-2.6.3-7mdk.img lrwxrwxrwx 1 root root 21 Sep 18 16:13 initrd.img -> initrd-2.6.3-7mdk.img lrwxrwxrwx 1 root root 25 Oct 23 21:00 kernel.h -> /boot/kernel.h-2.6.3-7mdk -rw-r--r-- 1 root root 537 Aug 14 03:55 kernel.h-2.6.3-7mdk -rw------- 1 root root 516096 Oct 22 19:45 map lrwxrwxrwx 1 root root 15 Oct 22 19:45 message -> message-graphic -rw-r--r-- 1 root root 442273 Aug 14 03:07 message-graphic -rw-r--r-- 1 root root 116 Sep 18 16:15 message-text lrwxrwxrwx 1 root root 21 Aug 14 03:53 System.map -> System.map-2.6.3-7mdk -rw-r--r-- 1 root root 898908 Mar 17 2004 System.map-2.6.3-7mdk -rw-r--r-- 1 root root 256 Aug 14 03:07 us-latin1.klt lrwxrwxrwx 1 root root 18 Sep 18 16:13 vmlinuz -> vmlinuz-2.6.3-7mdk -rw-r--r-- 1 root root 1440198 Mar 17 2004 vmlinuz-2.6.3-7mdk What information can you get from this? Regards, Horty

Thanks for your reply, artee. I think I know how to proceed, but I have included my fstab and lilo.conf for reference. Fstab /dev/hdb8 / ext3 defaults 1 1 none /dev/pts devpts mode=0620 0 0 /dev/hdc /mnt/cdrom auto umask=0,user,iocharset=iso8859-15,codepage=850,noauto,ro,exec 0 0 /dev/hdd /mnt/cdrom2 auto umask=0,user,iocharset=iso8859-15,codepage=850,noauto,ro,exec 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-15,sync,codepage=850 0 0 /dev/hda1 /mnt/win_c vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 /dev/hdb1 /mnt/win_c2 ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hda5 /mnt/win_d vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 /dev/hdb5 /mnt/win_d2 ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hda6 /mnt/win_e vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 /dev/hdb6 /mnt/win_e2 ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hda7 /mnt/win_f vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 /dev/hdb7 /mnt/win_f2 ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hda8 /mnt/win_g vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 none /proc proc defaults 0 0 /dev/hdb9 swap swap defaults 0 0 Lilo boot=/dev/hda default="linux" prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hdb8 initrd=/boot/initrd.img append="devfs=mount acpi=ht resume=/dev/hdb9 splash=silent" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hdb8 initrd=/boot/initrd.img append="devfs=mount splash=silent acpi=ht resume=/dev/hdb9" read-only other=/dev/hda1 label="windows" table=/dev/hda other=/dev/fd0 label="floppy" unsafe image=/boot/vmlinuz label="failsafe" root=/dev/hdb8 initrd=/boot/initrd.img append="failsafe splash=silent acpi=ht resume=/dev/hdb9 devfs=nomount" read-only I'm assuming that I hash out references to hdax, and change hdbx to hdax in both lilo.conf and fstab. I also have a boot disk on a floppy. Do I need to edit that as well? Thanks again. Horty

HI, I'm about to remove my primary master HDD (13 gb), which leaves a single 40 gb HDD on the system (currently the primary slave). The 40 gig drive has Mandrake 10 OE on it, and I am wondering as to how I can get it to boot when I have removed the 13 gb drive. I did a bit of Googling on the subject, and found a couple of ideas to the effect that I go into /etc/fstab and change all hdb entries to hda. Is this likely to work with Mandrake, and do I need to make any changes to lilo? Thankyou. Regards, Horty

rdbrooks, I've found this little partition to be a complete pain in the proverbial. At one stage it cost me the ability to boot into XP because the drive numbering system changed to accomodate it. I managed to get back in after a little edit of boot.ini, but just after a recent reinstall, I found that windows gave it a different designation letter, and subsequently reassigned most of my other drives. Anyway, I'd probably better stop moaning about Windows before the most noble and excellent moderator packs me off to an XP forum! As for lilo, I'm going to leave it in the MBR for the moment, for the main reason that I'm finding that I use Linux quite often now, and I quite like turning the computer on, going to make a cup of tea, and coming back to find Mandrake up and ready to go. Regards, Horty