Displaying 20 results from an estimated 100 matches similar to: "ipsec net-to-net problem"
2007 Sep 03
3
Shorewall + IPSec: help debugging why gw1<->gw2 SA works, but loc<->gw2 traffic doesn't trigger SA
Dear list,
I''m running Shorewall on a dedicated Fedora 7 box. Shorewall is working
well as an office DSL router (dynamic IP) with loc and dmz zones. I am now
trying to configure IPSec to connect a VPS, "casp", with a static IP to both
the firewall and to the loc network behind it. The host to host SA works
fine. However, pings from "loc" to "casp" can be
2004 Mar 11
1
Linux routing newbie Help!!
Hi,
I need some help with a routing/shaping setup that is a bit beyond my
current linux routing knowledge. I''ve read the how-to and most of the
related mailing list topics, but I still need some help to solve this
problem. I''ve been asking questions on various lists, but it seems like the
answers just add additional confusion. I decided to just describe what I''m
trying
2013 Apr 19
1
Can't connect to DSL modem on em1
Shorewall 4.5.15
3 Interface setup
em1
p3p1
p4p4
ppp0
Hi,
Since changing to NetworkManger on Fedora 18 I can no longer connect to the
DSL Modem, which is connected to Interface em1.
When the NetworkManger brings up the interfaces and ppp0, it no longer
assigns an IP to em1.
If I have ppp0 disabled and NetworkManger brings up the interfaces, em1
gets an IP of 192.168.1.2.
Then when I get
2006 Nov 21
0
Re: One bug in the SVN and rtp wrapper issue
> 1) First, I think there is a bug in libspeex/lsp.c line 512.
>
> /* hard limit ak's to +/- 32767 */
> if (a < -32767) a =32767; // This line should be changed to if
> (a < -32767) a = -32767;
> if (a > 32767) a = 32767;
> ak[j-1] = (short)a;
Oops. Thanks for pointing that out. It's fixed in svn.
> 2) About the RTP wrapper for VoIP
2006 Nov 21
0
Re: One bug in the SVN and rtp wrapper issue
lianghu xu wrote:
> In a word, I don't what's the standard of speex payload format.
> The file doc/rtp.txt is for what? Is it not for rtp payload?
> I find that rtp.txt is more detail that draft02.txt
>
> Which rtp docment should be followed?
> Anyone else has written the RTP wrapper already?
Oh, I see. doc/rtp.txt was a very, very early draft. See the manual for
a
2006 Nov 21
0
Re: One bug in the SVN and rtp wrapper issue
There's a field in the SDP description for
narrowband/wideband/ultrawideband.
Jean-Marc
lianghu xu wrote:
> if the new draft in the manual is used. I don't find how to tell the
> decoder which mode(NB/WB/UWB) is used
> in the encoder. The RTP header don't contain the mode field and I don't
> find the mode information in the
> coded frame either.
>
>
2006 Nov 21
2
One bug in the SVN and rtp wrapper issue
Hi Jean-Marc and All,
Two things need your confirmation/suggestion.
1) First, I think there is a bug in libspeex/lsp.c line 512.
/* hard limit ak's to +/- 32767 */
if (a < -32767) a =32767; // This line should be changed to if (a <
-32767) a = -32767;
if (a > 32767) a = 32767;
ak[j-1] = (short)a;
2) About the RTP wrapper for VoIP
I'd like to use the
2014 Jul 03
0
ctdb split brain nodes doesn't see each other
Hi,
I?ve setup a simple ctdb cluster. Actually copied the config file from an existing system.
Thats what happens:
Node 1, alone
Number of nodes:2
pnn:0 10.0.0.1 OK (THIS NODE)
pnn:1 10.0.0.2 DISCONNECTED|UNHEALTHY|INACTIVE
Generation:1369816268
Size:1
hash:0 lmaster:0
Recovery mode:NORMAL (0)
Recovery master:0
Node1, after start of ctdb on Node 2
Number of nodes:2
pnn:0
2006 Nov 21
2
Re: One bug in the SVN and rtp wrapper issue
In a word, I don't what's the standard of speex payload format.
The file doc/rtp.txt is for what? Is it not for rtp payload?
I find that rtp.txt is more detail that draft02.txt
Which rtp docment should be followed?
Anyone else has written the RTP wrapper already?
Lianghu
On 11/22/06, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote:
>
> > 1) First, I think there is
2014 Feb 26
0
CTDB Debug Help
Hello,
I've got a two node CTDB/Samba cluster that I'm having trouble with trying
to add back a node after having to do an OS reload on it. The servers are
running CTDB 2.5.1 and Samba 4.1.4 on AIX 7.1 TL2. The Samba CTDB
databases and Samba service work fine from the node that was not reloaded.
The rebuilt node is failing to re-add itself to the cluster. I'm looking
for
2006 Nov 21
2
Re: One bug in the SVN and rtp wrapper issue
if the new draft in the manual is used. I don't find how to tell the
decoder which mode(NB/WB/UWB) is used
in the encoder. The RTP header don't contain the mode field and I don't
find the mode information in the
coded frame either.
Does this mean we have to use NB decoder in all cases?
Lianghu
On 11/22/06, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote:
>
>
2015 Apr 23
4
Machine choosing unexpected logonserver in multi-dc domain 4.2.1
I have the following setup in a samba 4.2.1 multi-dc domain
DC1 - 10.10.2.50
DC2 - 10.10.2.60
DC3 - 192.168.103.2
I have a site and subnet setup for each DC in Active Directory Sites
and Services
DC1 server in site DC1 with subnet 10.10.2.50/32
DC2 server in site DC2 with subnet 10.10.2.0/24
DC3 server in site DC3 with subnet 192.168.103.0/24
DC3 has dhcpd setup giving machines on it's
2009 Feb 16
2
[Bug 577] New: cannot set spi/reqid numbers higher than 0x7fffffff (policy match)
http://bugzilla.netfilter.org/show_bug.cgi?id=577
Summary: cannot set spi/reqid numbers higher than 0x7fffffff
(policy match)
Product: iptables
Version: unspecified
Platform: i386
OS/Version: All
Status: NEW
Severity: normal
Priority: P1
Component: iptables
AssignedTo: laforge
2004 Aug 16
2
Re: [Shorewall-announce] Shorewall 2.1.4
Magnus Hyllander wrote:
>
> I guess what I''m wondering is, how does Shorewall (netfilter) know which
> zone a certain road warrior belongs to?
I''ve just completed getting dynamic zones working with ipsec again. A
dynamic IPSEC zone is defined in /etc/shorewall/zones by following the
short name (first column) with ":ipsec". The code is in CVS.
There are a
2011 Jul 15
0
S3 and CTDB errors in logs
I am seeing these errors every night in the logs. Should I be worried
about any of them? The only thing I have noticed is slow log ons.
Jonn
CentOS 5.6 x86_64
Samba 3.5.8
CTDB 1.0.114
DRBD/GVFS
--------------------- samba Begin ------------------------
**Unmatched Entries**
auth/token_util.c:525(debug_nt_user_token) NT user token: (NULL) : 1 Time(s)
2019 May 16
0
CTDB node stucks in " ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445"
Hi Benedikt,
On Thu, 16 May 2019 10:32:51 +0200, Benedikt Kaleß via samba
<samba at lists.samba.org> wrote:
> Hi everybody,
>
> I just updated my ctdb node from Samba version
> 4.9.4-SerNet-Debian-11.stretch to Samba version
> 4.9.8-SerNet-Debian-13.stretch.
>
> After restarting the sernet-samba-ctdbd service the node doesn't come
> back and remains in state
2005 Apr 27
5
26sec kame ipsec tunnel : packets leave unencrypted...
Hi everyone,
First of all, this is my first post in this ML, so I''m not sure that this
is the right place for my question (please don''t shoot me down ;)). For
the record, I''ve been reading and using LARTC for almost 3 years now, and
it''s a great help for anyone who wants to learn linux networking.
My problem:
I want to setup a tunnel for the following
2015 May 19
0
ctdb_client.c control timed out - banning nodes
Hello,
We are using CTDB / Samba to serve a number of windows users, at this point around 1200. We have a 4 node CTDB setup.
CTDB version - ctdb-1.0.114.7-1
Samba Version - sernet-samba-4.1.16-10
In recent months we've seen a big problem when 1 of the CTDB nodes is stopped or disconnected either manually or resulting from a problem. On some occasions, all other nodes get banned if a node
2024 Jul 16
0
[ANNOUNCE] nftables 1.1.0 release
Hi!
The Netfilter project proudly presents:
nftables 1.1.0
... after a release cycles of 8 months.
This release contains mostly fixes, listed in no particular order:
- Restore compatibility set element dump with <= 0.9.8
add element t s { 23 counter packets 10 bytes 20 timeout 10s }
add element t s { 42 timeout 10s counter packets 10 bytes 20 }
- Disallow ifname less than
2004 Aug 28
0
Shorewall 2.1.7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In this release:
1) Dynamic Ipsec Zones now work.
2) Output Traffic Accounting by user/group is supported (thanks to
Tuomas Jormola).
3) The following negative test options are added in /etc/shorewall/ipsec
and /etc/shorewall/masq:
reqid!=<number>
spi!=<number>
proto!=esp|ah|ipcomp
mode!=tunnel|transport