MOL networking

davidgurvich · Veteran Joined: 23 Apr 2004 Posts: 1063

An aid to those having trouble.
The package does not place the tun.ko driver in the correct place.
Instead the driver is placed in
/usr/lib/mol/v#/modules/tun.ko

It needs to go in
/usr/lib/mol/v#/modules/`uname -r`/tun.ko

In addition the following needs to be enabled in your kernel

ipt_MASQUERADE 3236 1
iptable_nat 7844 1
ip_nat 18008 2 ipt_MASQUERADE,iptable_nat
ip_conntrack 50804 3 ipt_MASQUERADE,iptable_nat,ip_nat
ip_tables 24128 2 ipt_MASQUERADE,iptable_nat
appletalk 39728 2
psnap 3720 1 appletalk
llc 7104 1 psnap

I have them as modules.

JoseJX · Retired Dev Joined: 28 Apr 2002 Posts: 2774

The tun.ko module is not required by MOL (on 2.6 kernels anyway), in the latest MOL it should not build tun.ko. You do need to have tun/tap support in your kernel for MOL networking to work.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml

davidgurvich · Veteran Joined: 23 Apr 2004 Posts: 1063

The tun.ko module works perfectly well with 2.6.13 and 2.6.14. For networking you need to have it where mol can find it. It will automatically load when you start mol. The alternative, sheep, does not work.

EDIT:
My system is a powermac G4. Perhaps the sheep driver is needed for other systems.

JoseJX · Retired Dev Joined: 28 Apr 2002 Posts: 2774

Sheep is for OS9 and does not work with OSX. I'm certain the that the tun.ko module built by MOL will work, the build process builds the tun module from the current kernel sources (it links it in, the included sources are for 2.4 kernels), so it's useless. Just build it in your kernel or as a module with your current kernel like the ebuild suggests now.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml

davidgurvich · Veteran Joined: 23 Apr 2004 Posts: 1063

Is the faq out of date or is there a further link there? I see an option in .config for a tun/tap but not in the faq.

JoseJX · Retired Dev Joined: 28 Apr 2002 Posts: 2774

The FAQ is out of date. I just recently changed MOL's behaviour a few days ago, I'll fix the FAQ when I get a chance. The ebuild does report the correct information after emerging though.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml

davidgurvich · Veteran Joined: 23 Apr 2004 Posts: 1063

I was just glancing through the ebuilds and was wondering at the purpose of this line

MAKEOPTS="${MAKEOPTS} -j1"

zeekec · Posted: Mon Dec 05, 2005 2:50 pm Post subject:

davidgurvich · Veteran Joined: 23 Apr 2004 Posts: 1063

From the line, it appears that MAKEOPTS can use multiple settings. Both the original value of MAKEOPTS in /etc/make.conf and the value assigned -j1.

Since it tells the compiler how many builds to run in parallel that doesn't make sense to me.

Let's say I have MAKEOPTS of -j5. How would the compiler do 5 parallel builds and 1 build? Or is it that the final value overrides the initial value?

JoseJX · Retired Dev Joined: 28 Apr 2002 Posts: 2774

Indeed, the final value overrides the previous. It's done this way so additional parameters are preserved.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml

nokilli · Apprentice Joined: 25 Feb 2004 Posts: 196

These latest versions of MOL have broken my ability to run MacOS. Panther runs beautifully however, and I can always run classic from with that.

At first it looked like the problem was with networking... it would complain about not being able to find the sheep driver. I fixed that by doing

JoseJX · Retired Dev Joined: 28 Apr 2002 Posts: 2774

You haven't provided enough information to really debug the problem. Are you booting it from it's own partition? Does it still boot natively? Are you sure you're using the correct OF Device Tree? The newer builds do identify as New World machines instead of OW machines, make sure you're booting with a New World OF Device Tree.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml

nokilli · Apprentice Joined: 25 Feb 2004 Posts: 196

Yes, MacOS 9 has it's own partition, and it boots natively, as well as under Panther. Also, MacOS 9 *was* working back before we started getting the Tiger-patched versions of MOL (well into 2.6)

This is a Pismo, so it's New World. Dunno about the OF device tree, thought all I had to do was specify the partitiion via molrc.macos (which I do as /dev/hda14 and, again, which used to work).

nokilli · Apprentice Joined: 25 Feb 2004 Posts: 196

OK, I guess I was lying. Just now tried to boot into Mac OS 9, and it just redisplayed the boot menu. Tried it again and the screen went dark; had to reset.

I could've sworn I had tested it before, but what with Mac OS X Classic Mode and MOL and Virtual PC and VNC and so forth it can sometimes be hard to know exactly what it is you're running.

Anyways, reinstalling Mac OS 9 now lets me access it without event from Linux using MOL. So that's one problem solved.

Now I want to figure out why it got corrupted in the first place. I rarely do anything with Mac OS 9, and while in the distant past the OS was prone to crashing hard and corrupting data that sort of thing hasn't happened to me now for years (can't remember the last time I even saw Macsbug.)

The one thing I did do which strikes me as being a likely candidate is copy a big file from within Linux to the partition hosting Mac OS 9. The file size was maybe 5GB. I recall also having to rename the file as for some reason the original name was truncated.

Does this seem a likely cause for my problems? On the one hand, it would be nice to know, but on the other hand, one of the ways I justify keeping Mac OS 9 around is as a kind of spare partition where I can copy big files when the need arises. If I can't have confidence in that anymore, well, that would suck.