[ previous ] [ next ] [ threads ]
 
 From:  "Michael Iedema" <iedemam at pluto dot dsu dot edu>
 To:  "'Frans King'" <kingf at f333 dot net>, <chris at logics dot co dot uk>, <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Re: [m0n0wall-announce] pb19 released - lots of changes!
 Date:  Sun, 2 Nov 2003 10:46:39 -0600
Hey all,

I was uploading stuff to my site this morning so I added a mirror as
well.

It's at http://students.dsu.edu/iedemam/m0n0wall/

--Michael I.

> -----Original Message-----
> From: Frans King [mailto:kingf at f333 dot net] 
> Sent: Sunday, November 02, 2003 10:20 AM
> To: chris at logics dot co dot uk; m0n0wall at lists dot m0n0 dot ch
> Subject: RE: [m0n0wall] Re: [m0n0wall-announce] pb19 released 
> - lots of changes!
> 
> 
> I've but such an image at the following URL:
> 
> http://www.f333.net/downloads/m0n0wall/generic-pc-ad2-pb19r535.img
> 
> The md5 checksum is here:
> 
> http://www.f333.net/downloads/m0n0wall/generic-pc-ad2-pb19r535.img.md5
> 
> It's not a very quick link so perhaps someone would like to put it up
> somewhere a little faster.
> 
> Regards,
> 
> Frans
> 
> 
> -----Original Message-----
> From: chris at logics dot co dot uk [mailto:chris at logics dot co dot uk] 
> Sent: 02 November 2003 11:35
> To: m0n0wall at lists dot m0n0 dot ch
> Subject: [m0n0wall] Re: [m0n0wall-announce] pb19 released - lots of
> changes!
> 
> Any chance the person who builds the releases could do a pc-image that
> works 
> on the equiv of /dev/hdc (so the Light Systems can work from compact
> flash!).
> 
> Would be brilliant if you could as its a right pain to get the image
> right 
> from the standard one.
> 
> Quoting Manuel Kasper <mk at neon1 dot net>:
> 
> > After working on m0n0wall for about 10 hours today, I'm happy to 
> > announce that m0n0wall pb19r535 is now available for downloading.
> Among 
> > many other small changes, three contributed patches have been 
> > integrated (listed in the order they were submitted in):
> > 
> > - Petr Verner's "more-advanced advanced outbound NAT patch"
> > 
> > - Bruce A. Mah's filtering bridge patch
> > 
> > - Jim McBeath's filter rule patch
> > 
> > Guys - thank you for contributing!
> > 
> > All these patches have been modified a little to suit my tastes - I 
> > especially found my fulfillment in tweaking the last one to 
> make it as
> 
> > self-explaining, simple, consistent and beautiful as 
> possible. ;) It 
> > was really about time that m0n0wall supported "block" 
> rules, so kudos 
> > to Jim. Thanks also to Bruce for figuring out why bridge(4) 
> wouldn't 
> > behave as expected (because it needed to be compiled into 
> the kernel -
> 
> > the module doesn't work properly).
> > 
> > OK, so here's the change log:
> > 
> > - block rules are now supported, the rule order can be changed,
> logging 
> > may be enabled per rule and rules may
> > be disabled individually
> > 
> > - filtering bridge support (see Diagnostics: Advanced page)
> > 
> > - destination for advanced outbound NAT is now configurable
> > 
> > - removed ng_bridge code, always use bridge(4)
> > 
> > - fixed ping/syslog to hosts on optional interfaces
> > 
> > - fixed interface status display when 1:1 NAT mappings are defined 
> > (subnet mask)
> > 
> > - static routes are no longer lost when modifying 1:1 NAT entries
> > 
> > - print a warning on the console if a newer configuration 
> file version
> 
> > is found than the current m0n0wall version was designed for
> > 
> > - upgraded system to FreeBSD 4.9
> > 
> > - upgraded MPD to 3.14
> > 
> > - some cosmetic HTML fixes
> > 
> > As this is quite a huge amount of changes for just one 
> version step, 
> > there may be some bugs left (as always)... I'm sure the 
> user community
> 
> > will notice and report (and fix?) them as they show up. :)
> > 
> > Note that bridging behavior is now slightly different than before - 
> > even when the filtering bridge is not enabled. You now need 
> to add a 
> > filter rule on bridged interfaces if you want to access the 
> webGUI (or
> 
> > other services on m0n0wall itself, for that matter). e.g. 
> if you have 
> > your wireless interface bridged to LAN, you must add a rule to pass 
> > traffic on WLAN to m0n0wall's LAN IP address in order to access the 
> > webGUI from WLAN.
> > 
> > Since it is now possible to specify block rules, the rule order has 
> > become relevant. Rules are no longer auto-sorted by port and other 
> > various criteria anymore. You can use the up/down arrows to reorder
> the 
> > rules, as well as the "+" button provided next to each rule 
> to insert
> a 
> > new rule right after the one in question. If you want to painlessly
> add 
> > a rule at the top of an interfaces' rule list, use the "+" 
> button at 
> > the very bottom (the one that has always been there). Of course, if
> you 
> > only use pass rules (as in earlier versions), you obviously 
> don't have
> 
> > to worry about rule order.
> > 
> > Well, this will have to do for a while - I can't afford to spend a 
> > whole day working on m0n0wall every week. ;)
> > 
> > - Manuel
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: m0n0wall dash announce dash unsubscribe at lists dot m0n0 dot ch
> > For additional commands, e-mail: 
> m0n0wall dash announce dash help at lists dot m0n0 dot ch
> > 
> > 
> 
> 
> 
> 
> ----- End forwarded message -----
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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
> 
> 
> ---------------------------------------------------------------------
> 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
>