I am forwarding this to the list,
Regards
Harry
[EMAIL PROTECTED] wrote:
I am trying to setup Bering uClibc 3.1 beta 1,
=20
However When I try to insert some config in shorwall/tcdevices and tccl=
asses=20
shorewall check complains with these
--
I am faced with this problem
After ./buildtool.pl remove shorewall
and
./buildtool.pl source shorewall
to get it from CVS but for some reason it downloads some
page from sorceforge instead of buildtool.cfg
My CVS checkout is
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf login
cvs -z3 -d
Thanks Martin
It seems that tinyproxy ( running on my firewall or its parent, I use my
providers proxy gateway ) did something bad.
After I bypassed the proxy it seems to be running ok.
Regards,
Harry.
PS. By the way I have compiled dansguardian for Bering-uClibc and it seems ok -
so far.
I am trying to setup Bering uClibc 3.1 beta 1,
However When I try to insert some config in shorwall/tcdevices and tcclasses
shorewall check complains with these
--
Validating /etc/shorewall/tcdevices...
sed: bad option in substitution expression
sed: bad
Sorry pal,
I was in a hurry and pressed reply ... you have made it up though,
Now in the real fun stuff,
I 've downloaded the dansguardian tgz file from the dansG site ..
It builds ok somehow
However
ldd shows
linux-gate.so.1 = (0xe000)
libz.so.1 = /usr/lib/libz.so.1 (0xb7f56000)
Hi all,
I would appreciate any help regarding dansguardian compilation for our uClibc
buildtool env.
I' ve managed to reach installation but for some reason ( my buildtool.mk is
screwed ) it tries to install everything under / and not in staging.
Also ldd gives some weird results.
Thanks
That Did it ... :-)
Thanks a lot ...
Given the chance, how am I about to cover the moh asterisk issue ??
From What I realize moh is an issue with this asterisk version
The manual from asterisk.org states that the required version of mpg123 is
v0.59r however the one that is in the cvs is 0.60
I am trying to compile the entire source tree ( buildtool )
However Asterisk + zaptel + bristuff get stuck.
I seem to miss newt-x-xx packages ??
Any clues is my cvs correct ??
export CVS_RSH=ssh
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf login
cvs -z3 -d :pserver:[EMAIL
Thanks anyway,
What I was looking for is located in shorewall/netmap,
Still though I am wondering whether there is a chillispot.lrp package
Kind Regards
Harry
Harry Lachanas wrote:
I Would like to connect 2 lans over NET with openvpn ... problem is that
both are using the same subnet
Is there any trial to port LEAF into 2.6 kernel???
I need the ipt_CLASSIFY which I am not able to locate it in the 2.4 kernel
tree.
Is there some link in the CVS tree that I can download and compile ( or at
least try ).
Regards
Harry..
I am Trying to connect 2 Bering-uClibC v2.0 boxes --together--.
dialin and dial out ON BOTH
+-+ +--+
|LRP1 | -- | LRP2 |
|ttyS0| | ttyS0|
+-+ +--+
That is Both Having mgetty and Both Having pppd dial out connections.
Both being
Hi
At 16:28 20.08.2004 +0300, [EMAIL PROTECTED] wrote:
I am trying to apply the wshaper script included=20
however I am gettting=20
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
after this=20
tc filter add dev $DEV parent 1: protocol ip prio 0 handle 2 fw
I am trying to apply the wshaper script included
however I am gettting
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
after this
tc filter add dev $DEV parent 1: protocol ip prio 0 handle 2 fw classid 1:20
and this
tc filter add dev $DEV parent 1: protocol ip prio
At 16:44 15.07.2004 +0300, [EMAIL PROTECTED] wrote:
I 've noticed that when installing the default shorewall configuration of=
Bering-*
there is no block of rfc1918 packets going out to NET
That is traceroute from LOC of any address not included in LOCAL LAN but in=
the RFC1918
Hi!
I 've noticed that when installing the default shorewall
configuration of=
Bering-*
there is no block of rfc1918 packets going out to NET
That is traceroute from LOC of any address not included in
LOCAL LAN but in=
the RFC1918 range will go out and traverse the
I 've noticed that when installing the default shorewall configuration of Bering-*
there is no block of rfc1918 packets going out to NET
That is traceroute from LOC of any address not included in LOCAL LAN but in the
RFC1918 range will go out and traverse the net( Default route ).
Who is
I'am Trying to figure out some solutions with VOIP + VPN.
There are three locations connected to each other with OPENvpn
Over aDSL.
I've looked at Asterisk.org and digium.com. ( HARDWARE )
Has any body accomplished somthing similar in any way ??
From my Point of view it would be great
Have a look in here
http://www.openbrick.org/en/Members/seb/doc/reliable_vpn/view
Hi everybody
I am playing with ppp/pppoe and VPN connections on Bering boxes. The nature=
of VPN requires the ipsec connections to be restarted when the IP address=
on the gateway changes, Having little
18 matches
Mail list logo