Joey
for your reference, this is how the wondershaper installs the root qdisc
# install root HTB, point default traffic to 1:20:
tc qdisc add dev $DEV root handle 1: htb default 20
HTH
Erich
At 22:30 16.12.2003 -0600, Joey Officer wrote:
...
firewall: -root-
# tc qdisc add dev eth0 root handle
Leaf Users,
This is a general question about the capability of Bering. I am trying to
connect 2 VPN clients from inside my network to their respective VPN
concentrators. I have successfully set up the Cisco VPN client to communicate
to my wife's company. One of the clients is a Cisco and the
Hello Group
I have some problems in my connection to and from DMZ
and LOC
all other than LOC - DMZ works
I'm using shorewall 1.4.8 with the three interfaces
config examples
not only ping but also ssh can't connect
I imagine it's a small detail i missed
but hell i can't find it,
Regards
Lasse
I agree that I may have something that is bunk, which I have conceeded that
may require my replacing my boot image, and then just reconfiguring it.
Fortunately, for the most part it is a stock install. I'll try that this
weekend, and hope for the best.
Hopefully it has been just a matter of
I tried the below modifying the entry to point directly to eth0 and received
the following:
firewall: -root-
# tc qdisc add dev eth0 root handle 1: htb default 20
RTNETLINK answers: Invalid argument
I received an email off list that references a potential problem the with
tc.lrp package that I
I normally don't advertise for anyone, but I just read this on Marketwatch
about a company comming out with a card in January, with native support for
Linux (currently Redhat Timesys). For any of those specializing in this
type of configuration, enjoy.
At 04:03 PM 12/17/2003 +0100, and hansen wrote:
Hello Group
I have some problems in my connection to and from DMZ
and LOC
all other than LOC - DMZ works
I'm using shorewall 1.4.8 with the three interfaces
config examples
not only ping but also ssh can't connect
I imagine it's a small detail i
Hi Again
Hello Group
I have some problems in my connection to and from
DMZ
and LOC
all other than LOC - DMZ works
I'm using shorewall 1.4.8 with the three interfaces
config examples
not only ping but also ssh can't connect
I imagine it's a small detail i missed
but hell i can't find it,
The
Sorry - I was getting Dachstein and Bering muddled in my head when I
replied before. You're right -- no /etc/network.conf in Bering. And
apparently it is not a routing table problem, at least not on the Bering
router, based on your new report.
I can't figure out what you mean by i can ping
snip
You state here your subnets are 192.168.1.0/24 and 192.168.10.0/24
192.168.1.0/24 dev eth1 proto kernel scope link src
192.168.1.254
192.168.10.0/24 dev eth2 proto kernel scope link
src 192.168.10.100
128.142.112.0/20 dev eth0 proto kernel scope link
src 128.142.121.254
Eddie Wilson wrote:
I've included an ipsec-barf to demonstrate ipsec0 being assigned to an
address other than the primary for that interface.
very helpful IPSec barf snipped
-Original Message-
From: Eddie Wilson [SMTP:[EMAIL PROTECTED]
Sent: Saturday, December 13, 2003 9:48 AM
To:
to Tom:
you mix up the reply, see my first posting :)
it's the default example (192.168.1.x)
and RH FAQ info to Ray Olszewski
Linux firewall 2.4.20 #1 Sun May 11 18:53:34 CEST 2003
i586 unknown
1: lo: LOOPBACK,UP mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00
sorry Tony Tony..not tom :))
Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og
virusscan
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up
At 07:50 PM 12/17/2003 +0100, and hansen wrote:
[...]
and RH FAQ info to Ray Olszewski
[details deleted in reply]
OK. I read through the Shorewall rulesets you provided (as well as the rest
of the information), and it looks like the router should be letting you
ping both ways between dmz and
Ok so this should be an easy question for some people on the list. But for
some reason I can not get udp port 27015 open on my Bering firewall with
shorewall. I have fallowed the FAQ to a T. Still I can see the traffic being
blocked in the shorewall log. I want all traffic coming to upd port 27015
On Wednesday 17 December 2003 12:16 pm, Dalziel, Josh wrote:
Ok so this should be an easy question for some people on the list. But for
some reason I can not get udp port 27015 open on my Bering firewall with
shorewall. I have fallowed the FAQ to a T. Still I can see the traffic
being blocked
On Wednesday 17 December 2003 12:16 pm, Dalziel, Josh wrote:
Ok so this should be an easy question for some people on the list. But for
some reason I can not get udp port 27015 open on my Bering firewall with
shorewall. I have fallowed the FAQ to a T. Still I can see the traffic
being blocked
Eddie Wilson wrote:
Thanks Charles. I tried changing the interfaces statement and the result
was as expected. I am not sure how I would assign the extra addresses
differently. I am assigning the p-t-p address in my wanpipe configuration
and adding 2 of the extra 6 I have through Shorewall-NAT,
I don't get any pkts or bytes
even if i browse some web pages
only 0 0 ??
i have the info switch at on, in my policy ??
what have i done now :)
Shorewall-1.4.8 Chain at - Wed Dec 17 22:00:54 UTC
2003
Chain INPUT (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out
wait..now, i'm counting packets, so let me investigate
this...i'll be back :))
Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og
virusscan
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an
Now I got it :))
I have so big and red ears, shit they are hurting me
twice as big as my head
my gatewaydev on my dmz server were on 192.168.1.x
so why have i told you that i can ping net from
dmz...shit
sorry..and thanks for your help :)
Regards
Lasse
Yahoo! Mail
On Wed, 17 Dec 2003, Dalziel, Josh wrote:
That is what I put into my rules file and its still being blocked by the
firewall :(
Please post the output of shorewall show nat as a text attachment.
And please don't reply off-list.
-Tom
--
Tom Eastep\ Nothing is foolproof to a sufficiently
At 07:46 PM 12/17/2003 -0800, Tom Eastep wrote:
On Wed, 17 Dec 2003, Dalziel, Josh wrote:
That is what I put into my rules file and its still being blocked by the
firewall :(
Please post the output of shorewall show nat as a text attachment.
And please don't reply off-list.
Actually, I'd
OK sorry for the typos I was in a hurry to get out of my office and back
home to see if I can get this thing figured out. I know that there is no
UPD, and that it is UDP, and I know that I fat fingured the ip. I never said
anything about knowing what rule was blocking the traffic just that it is
24 matches
Mail list logo
