On Sat, 12 Feb, 2005 at 18:00:05 -0500, Gene Smith wrote:
I am running a bering-leaf system with 2.4.18 kernel that I setup about
two years ago (not sure of exact version). It has been working fine
except for one problem. When the cable goes down and eventually comes
back up the bering-leaf
I started to build the upnp package based upon the
current linux-igd and libupnp packages in
sourceforge's cvs, but got hung up with some
development environment issues setting stuff up (I'm
running gcc 3.3.5 and kernel-2.6 on the host
environment and got sick and tired of running into
Jon Clausen wrote, On 02/13/2005 03:27 AM:
On Sat, 12 Feb, 2005 at 18:00:05 -0500, Gene Smith wrote:
I am running a bering-leaf system with 2.4.18 kernel that I setup about
two years ago (not sure of exact version). It has been working fine
except for one problem. When the cable goes down and
Hi folks,
I'm setting up a new Bering-uClibc 2.2.3 box, and I've added Tom's latest
stable shorwall.lrp package to it before starting any setup. I've got my
NICs configured (both use DHCP), and both NICs receive their addresses fine.
However...I have no internet access. :-( When I try to ping a
Craig Caughlin wrote:
Hi folks,
I'm setting up a new Bering-uClibc 2.2.3 box, and I've added Tom's latest
stable shorwall.lrp package to it before starting any setup. I've got my
NICs configured (both use DHCP), and both NICs receive their addresses fine.
However...I have no internet access.
Tom Eastep wrote:
Craig Caughlin wrote:
Hi folks,
I'm setting up a new Bering-uClibc 2.2.3 box, and I've added Tom's latest
stable shorwall.lrp package to it before starting any setup. I've got my
NICs configured (both use DHCP), and both NICs receive their addresses fine.
However...I have no
Hey, good call, Tom. That solved the /etc/shorewall/shorewall.conf: 1:
/shorewall/shorewall.conf: not found error message (I saw Andrea Galmacci's
post, too.). My policy file looks pretty vanilla:
#SOURCE DESTPOLICY LOG LIMIT:BURST
#
Craig Caughlin wrote:
Hey, good call, Tom. That solved the /etc/shorewall/shorewall.conf: 1:
/shorewall/shorewall.conf: not found error message (I saw Andrea Galmacci's
post, too.). My policy file looks pretty vanilla:
#SOURCE DESTPOLICY LOG
Tom Eastep wrote:
Craig Caughlin wrote:
Hey, good call, Tom. That solved the /etc/shorewall/shorewall.conf: 1:
/shorewall/shorewall.conf: not found error message (I saw Andrea Galmacci's
post, too.). My policy file looks pretty vanilla:
#SOURCE DESTPOLICY LOG
Tom Eastep wrote:
Nevermind -- I see the problem. The policy file in the .lrp is missing
the all-all policy.
I've added a corrected policy file to the 'errata/LRP' sub-directory at
the primary download site:
http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.0/errata/LRP
Hi folks,
I'm not sure if this is related to my other hiccups, but I don't think so.
My problem is that I don't seem to be able to resolve DNS names. I can
connect to web sites if I know their IP address, but I can't ping anyone via
FQDN either from my LAN or from the firewall. Suggestions?
Thank
Craig Caughlin wrote, On 02/13/2005 05:22 PM:
Hi folks,
I'm not sure if this is related to my other hiccups, but I don't think so.
My problem is that I don't seem to be able to resolve DNS names. I can
connect to web sites if I know their IP address, but I can't ping anyone via
FQDN either from my
Hi folks,
Thank you for the reply, Gene. I actually discovered two things I was doing
wrong.
1.) I had assumed I needed to use the dhcpd.lrp package that I used
to use when I no longer used pump.lrp to service my LAN DHCP clients.
Obviously, I didn't need to do that. I didn't realize that
13 matches
Mail list logo
