Re: [leaf-user] (!NF) at boot.

2004-02-10 Thread sak
Looks like that was the problem. lrpkg.cfg did the trick. Thanks everyone, Sak. On Tue, 10 Feb 2004, K.-P. Kirchdörfer wrote: > Am Dienstag, 10. Februar 2004 21:46 schrieb [EMAIL PROTECTED]: > > Hey everyone, > > > > I'm having a little problem with a couple of packages loading during boot > >

RE: [leaf-user] (!NF) at boot.

2004-02-10 Thread Simon Bolduc
Hey, It sounds to me like you've hit the character limit of 255 characters for the line loading the package. As such lrpkg isn't receiving the entire name of the package -thus the NF or not found message. I believe there is another file in which you can specify packages, but as I'm not near

Re: [leaf-user] (!NF) at boot.

2004-02-10 Thread K.-P. Kirchdörfer
Am Dienstag, 10. Februar 2004 21:46 schrieb [EMAIL PROTECTED]: > Hey everyone, > > I'm having a little problem with a couple of packages loading during boot > time. I'm running Bering 1.2, configured to boot and load packages from > /dev/hda1. There are two packages that don't want to load at boo

[leaf-user] (!NF) at boot.

2004-02-10 Thread sak
Hey everyone, I'm having a little problem with a couple of packages loading during boot time. I'm running Bering 1.2, configured to boot and load packages from /dev/hda1. There are two packages that don't want to load at boot time: tcpdump.lrp and ntpsimpl.lrp. When I include either of these

Re: [leaf-user] Port forwarding - DMZ problem

2004-02-10 Thread Tom Eastep
On Tuesday 10 February 2004 11:55 am, Stephen Lee wrote: > > Thanks much Tom. It works now. Now I understand what ORIGINAL > DESTINATION and DETECT_DNAT_ADDRS means ;-) > You're welcome, Stephen. For the benefit of those searching the archives, the option in shorewall.conf as actually named DETE

Re: [leaf-user] Port forwarding - DMZ problem

2004-02-10 Thread Stephen Lee
On Tue, 2004-02-10 at 10:51, Tom Eastep wrote: > On Tuesday 10 February 2004 10:17 am, Stephen Lee wrote: > > Hi, > > > > I'm running a Bering1.2/CD system with a lan(eth1) and a proxy > > dmz(eth2). There's workstation on the lan running a pcAnywhere host and > > a server in the DMZ running pcAnyw

Re: [leaf-user] Port forwarding - DMZ problem

2004-02-10 Thread Tom Eastep
On Tuesday 10 February 2004 10:17 am, Stephen Lee wrote: > Hi, > > I'm running a Bering1.2/CD system with a lan(eth1) and a proxy > dmz(eth2). There's workstation on the lan running a pcAnywhere host and > a server in the DMZ running pcAnywhere as well. I can connect to the lan > pcAnywhere via the

[leaf-user] Port forwarding - DMZ problem

2004-02-10 Thread Stephen Lee
Hi, I'm running a Bering1.2/CD system with a lan(eth1) and a proxy dmz(eth2). There's workstation on the lan running a pcAnywhere host and a server in the DMZ running pcAnywhere as well. I can connect to the lan pcAnywhere via the public IP on eth0. The problem is that attempting to connect to the

Re: [leaf-user] How do I route 255.255.255.255 to my internal network?

2004-02-10 Thread Ray Olszewski
At 08:26 AM 2/10/2004 -0800, Mark Ivey wrote: I'm trying to set up the wake-on-lan proxy (http://freshmeat.net/projects/wolp/) on my Bering machine and it isn't working. Here is a snippet from the README file: "If the target LAN is not the route taken by packets to the broadcast address 255.255.25

[leaf-user] How do I route 255.255.255.255 to my internal network?

2004-02-10 Thread Mark Ivey
I'm trying to set up the wake-on-lan proxy (http://freshmeat.net/projects/wolp/) on my Bering machine and it isn't working. Here is a snippet from the README file: "If the target LAN is not the route taken by packets to the broadcast address 255.255.255.255, e.g. on a firewall, where the default