[ previous ] [ next ] [ threads ]
 From:  "PaulPigster" <paul dot pigster at cox dot net>
 To:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Modified pb20 image
 Date:  Tue, 25 Nov 2003 05:56:54 -0500
I did a firmware upgrade from a hacked net45xx-pb19 to this new
net48xx-pb20r555 image successfully after renaimng the file net45xx :-)
For reference my SanDisk 256M CF card comes up as ad0.

-----Original Message-----
From: Manuel Kasper [mailto:mk at neon1 dot net]
Sent: Monday, November 24, 2003 2:31 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: [m0n0wall] Modified pb20 image

In order to solve that pesky is-it-ad0-or-ad1-or-ad2-now problem once
and for all, I've modified the m0n0wall booting process to probe all
devices from ad0 to ad3 until the right one (mountable and with a
configuration file on it) is found (this of course doesn't apply to the
CD-ROM version). The fstab is then generated on-the-fly.

I don't want to make this an official release yet, because I think it
needs some testing. Those who are willing to try it can find it on


...look for the pb20r555 images. Make sure to test the firmware upgrade
facility, too.

These images also have a new kernel that includes a patch for the PPTP
VPN problems (lots of errors, packet loss). It's probably not a 100%
solution, but it seems to greatly lower the impact of the problem. In
any case, this is not specific to m0n0wall - it's a problem in MPD and
netgraph's PPTP node. It's being discussed on the mpd mailing list
(http://sourceforge.net/mailarchive/forum.php?forum_id=32902), but
nobody seems to have a real fix for it yet.



To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch