I have a successfully working bering1.2 installation.
I download the latest shorewall package v1.45 from TomEastep at
www.shorewall.net
I followed the upgrade procedure --see below
...
after the upgrade, the firewall performs correctly but the
shorewall.log is now broken. Can anyone determine
after the upgrade, the firewall performs correctly but the
shorewall.log is now broken.
What does that mean exactly?
Shorewall functions as it did before the upgrade...
allows traffic that is allowed by the rulesets to get through
and denies those that should be denied.
shorewall status
---
a) Are you using syslogd or ulogd for logging?
which syslogd
returns /sbin/syslogd
which ulogd
returns /usr/sbin/ulogd
###forgive me master, my meager skills are unable to determine.
###I am using whatever the
Your Shorewall configuration is using syslogd -- The Bering 1.2
Shorewall
package has been modified to use ulog. Looks like the upgrade
instructions
that you followed are incomplete with respect to Bering 1.2.
I'm not surprised the instructions are incomplete.
I cobbled the HOWTO together from
How To set Date Time - 3 questions
I ) Is there a DateTime HowTo for leaf?
II ) I've forgotten how to set the date, time timezone under leaf
(bering)
for the system, user, and the cpu's clock. Where are examples of
the
correct usage for the commands documented?
is ntpdate available in a .lrp
for leaf dachstein/bering?
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
leaf-user
I'm probably going to have less than 253 computers connected to my LEAF.
More likely, there will be a maximum of 5.
If I define my internal network as being a Class C:
net addr: 192.42.97.16 /29
mask: 255.255.255.248
broadcast: 192.42.97.23
Hosts: 17-22
Is there an advantage or
Note: Harry Kitt's message his problem
driver appeared to work, but would randomly drop the connection.
Probably not recompiled for the Bering's kernel/compiler.
---was because he used drivers from his Dachstein disk.
I've tried editing shorewall to use each of them as the external
interface
swfla.rr.com == aka == timewarner/roadrunner cable
I'm using the default setup on the Bering_1.0rc3 floppy1680 image
---except I went ahead and removed norfc1918 from
/etc/shorewall/interfaces' eth0
Initially the users connected behind the firewall are able to use
services, then after a
swfla.rr.com == aka == timewarner/roadrunner cable
I'm using the default setup on the Bering_1.0rc3 floppy1680 image
---except I went ahead and removed norfc1918 from
/etc/shorewall/interfaces' eth0
I'm still having the outside world suddenly disappear.
I can login to the firewall itself and
OK, I'm confused about what pump gives for statistics.
If my ISP is possibly using an RFC 1918 IP address on their DHCP server,
shouldn't Pump list the Boot Server as such?
If Pump lists my renewal time as being ten (10) hours from now,
and the expiration as being eleven (11) hours from now,
Can you dump
ipchains -t nat -vnL
and
ipchains -vnL
#
ipchains: not found
Bering1.0 rc3, after a random time period, the internet disappears from
eth0.
I have to reboot Bering and
power-cycle the cable modem as well.
pump -s gives me addresses outside of RFC1918 (65.34.x.x), so I don't
12 matches
Mail list logo