Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I am trying to set up a PXE server for Knoppix. The server already serves DSL(the variant that runs completly from RAM), and floppy images for DOS. This is the first time I've used NFS for booting, although the DSL has been using it for file sharing.
In DSL, and if I boot Knoppix off the CD, I can use the command:
sudo mount -t nfs 10.1.1.1:/mnt/f/Public/PXE/syslin/KNOPPIX /mnt/nfs
to mount the location of the Knoppix files as well as read and write them, so there isn't a problem with the NFS server.
however, if I add the following to the pxelinux configuration
(which is mainly copied from the Knoppix PXE server) Knoppix will start booting, but will search for the main image (stored on the NFS share) and not find it. If the CD is in the drive at startup the PXE booted machine will find the main image on the CD and continue booting from that.
If I use:
rem append root=/dev/nfs nfsroot=10.1.1.1:/mnt/f/Public/PXE/syslin/KNOPPIX ip=auto
Which I am given to understand would mount / as the listed folder, produces a kernel panic error, saying the filesystem can't be synced, and that /dev/nfs dosen't exist.
My guess is that the kernel isn't comunicating with the NFS server corectly. Also, becuase my NFS server is Cygwin wich only serves version 2, not version 3 this might be cuasing the kernel greif.
Realy, I'm happy with the kernel mounting anything from the NFS server, and working around this. I get the feeling it's something stupidly simple
After feriting about in the /tftpboot/ folder of the CD driven knoppix, I have discovered that I need a diferent initrd file. I happly splaped that onto the NFS server along with the code I found in the pxelinux.cfg/defualt file, which was slightly diferent from what I had so, now I'm using:
APPEND secure nfsdir=10.1.1.1:/mnt/f/Public/PXE/syslin/KNOPPIX/ nodhcp lang=us ramdisk_size=100000 init=/etc/init apm=power-off nomce vga=791 initrd=KNOPPIX/boot/isolinux/test.gz quiet BOOT_IMAGE=knoppix
And now I have an all new error message!
Found network device(s) handled by tulip.ko.
Can't NFSmount KNOPPIX filesystem, sorry.
I'm still running with the NFS server not interacting correctly with the Knoppix kernel
It ocured to me that I might get more helpfull errors if I tryed mounting the NFS share using the limited shel that Knoppix provides after a failue. using the command
mount -t nfs 10.1.1.1:/mnt/f/Public/ /mnt/
(creating folders isn't supported in the limited shell) produces an error similar to data missing or invalid input (sorry I don't have the exact error, I only have one machine now it's the one I using to post this and boot to PXE) I tryed adding the nfsvers=2 option, becuase that's all the server produces, but was given the unkown option error.
From the quasi english that the traslator produces, I have gathered that this problem can be cuased by the /etc/exports file on the NFS host, but not what to do to it to fix the problem. I think that I will have to boot back to knoppix and have a look at the exports file that it produces.
I have replaced my cygwin /etc/exports file with /tftpboot/exports from Knoppix, then changed the folder that it pionts to (10.1.1.1:/Knoppix rather than 192.168.0.1:/cdrom).
This has made no diference what so ever
I have also found that the miniroot.gz that comes with knoppix (and my test.gz that I took from the CD run terminal server) are in fact tiny liniux enviroments that are booted from vurtual floppy disks and mount the knoppix files (on CD and NFS respectivly) then hand controll over to Knoppix, so my idear with vurtual Floppies served through Memdisk is already built into the Knoppix system.
This however, still leaves me with the problem that the miniroot.gz can't mount anything from my NFS server, even though the fully booted Knoppix can. What I think is happening is that the kernel is expecting NFS version 3, and has no backwards compatablity to mount version 2 untill the rest of system is booted. The SMB version (from http://knoppix.manty.net/) also encounters a similar problem, but it can't mount the SMB share becuse it requires authentication, even though I pass it a username and password as such:
which, once again works once the main system has started.
On a side note I have never compiled my kernel nor kernel modules, however the file that apears to be causing the problem is NFS.ko (the NFS kernel module that comes with Knoppix).
I have no idear what so ever how to go about compiling a new NFS.ko with version 2 backwards compatablity. If anyone knows if there is a precompiled one for the knoppix 4.0 kernel (2.6.4 I think) avalible for download, that would help emensly
If I boot up with the samba minirt, and get dropped into the limited shell, I did wonder if attempting mount the share would give me the information that I need to work this out. So, entering the command:
mount -t cifs //user:Pass@10.1.1.1/knoppix /tmp
mount -t cifs //10.1.1.1/knoppix /tmp
gives the error "CIF VFS: cifs_mount failed with return code = -22"
also, changing this to
mount -t cifs //10.1.1.1/knoppix /tmp -o user=user,pass=pass
A wondorusly simpile somution to a diobolicaly dificult problem!
Pity it dosnn't work. Changing the nfs share to 10.1.1.1:/cdrom made no diference:
mount -t nfs 10.1.1.1:/cdrom/ /mnt/
mount -t nfs 10.1.1.1:/cdrom /mnt/
mount -t nfs wibblewibbleIamatree /mnt/
all produce the error "NFS_read_super: missing data argument". After I discovered that last one, I tryed unpluging the network, and repetting which produced identical results. What ever the problem is, it's centered around the PXE or the kernel/intrid served by the PXE not driving the network correctly. I tryed again on another machine (admitedly they where both HPs) witch did exactly the same thing. Is there an issue here with knoppix 4.0 or with it's kernel? should I be using 5.0? or an earlyer version?
I fnialy worked out what the korean site was saying to do to the /etc/exports file: add "/cdrom access = mount" to the bottom. After I tryed this without success, I turned my attention to the initrd file. If this was built at setup, and one of the options was to set what network cards to probe for, what if I set it up to probe for every single card it could, that would work wouldn't it? No. And neither would using the misteriously appearing kernel, referenced in the pxeconfig file, produced when the intrid file was generated.
I have just spotted somthing that cheared me up. Go to the korean link above (http://translate.google.com/translat...ial_s%26sa%3DN)
and click on "FAQ" in the menu up the top. There's only the one FAQ, check out question number one on it. Makes you wonder just what the koreans are using their embedded linux for exactly