similar to: Sanity, Manners and Shorewall Support

Hi, I just wonder, if it is possible, to suppress my own number on outbound dials with chan_capi. I took a look into the sources and think it might work with toggeling the "@" in front of the outbound msn in the dialstring. (Dial(CAPI/@msn... vs. Dial(CAPI/msn... But it doesn't work. Maybee I'm wrong and misunderstood the code. Thanks for any answers! Karsten

An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20031207/e5e9b8eb/attachment.htm -------------- next part -------------- Hello all, I am newbie to Telephony world (IP and PSTN). Please excuse me if you find my questions very dumb. I am trying to configure my IP 7940 with the Asterisk, when phone boots up it only shows the message "Phone

Hi all, I compiled/installed chan_capi.so without problems. When I launch Asterisk, I get the following error: --- [chan_capi.so] => (Common ISDN API for Asterisk) == Parsing '/etc/asterisk/capi.conf': Found Mar 30 19:47:52 NOTICE[16384]: chan_capi.c:2338 mkif: ast_capi_pvt(91xxxxxx,*,pstn,0x2,2) (1,2,64) (0)(0.800000/0.800000) 0 Mar 30 19:47:52 NOTICE[16384]: chan_capi.c:2338

It is with regret that I announce that Shorewall development and support is officially ended. Sean''s post has finally driven it home to me that in the long term, trying to support a project like Shorewall is impossible for a person of my personality and age. Sean -- please believe that this isn''t about you or your post -- your post was just the proverbial straw on this old

I''m just looking for a quick sanity check to make sure what I''m finding is really all necessary here. I''m upgrading a gateway/firewall from Linux 2.4 to 2.6 using Mandrake 10.1. In the old 2.4 kernel I structured my firewall rules around the ipsec0 interface, which I understand isn''t present with Openswan running under 2.6 (no KLIPS). Ok, So as I start to

I am setting to a shorewall system with 4 NIC''s as per the outline specification below. Can anyone please have a look and let me know what I have missed and what I have got wrong as I want to take this system live ASAP but do not want to kill internet access and the hosting for too long ! I have listed below the system outline & have attached the config files that I have changed, if

This one is really throwing me. Thanks in advance for any advice. I''m working on a 4 port firewall system. It is running heartbeat+drbd. Primary box looks like this: eth0 -> net/cicso router 192.168.144.2/29 eth1 -> drbd/heartbeat crossover cable 192.168.254.253/30 eth2 -> dmz 192.168.144.10/24 eth3 -> loc 192.168.101.2/24 The IP''s

Please excuse my ignorance as I''m a linux newbie. Basically I have a setup of an adsl ethernet modem (nated and then everything forwarded to the external ip of my Mandrake mnf firewall) connected to the mnf firewall which then connects to the lan. internet <--> adsl modem <--> mnf firewall <--> lan There''s only 2 nics in the mnf firewall so it''s a

Shorewall 3.4.6 running on SuSE Linux 10.2 Compiling Rule Activation... Shorewall configuration compiled to /var/lib/shorewall/.restart Processing /etc/shorewall/params ... Restarting Shorewall.... /sbin/shorewall: line 665: 6782 Segmentation fault $SHOREWALL_SHELL ${VARDIR}/.restart $debugging restart got this with V3.4.4, updated to 3.4.6 this morning, but that didn''t help.

Before wasting a lot of time going at this in the wrong list, I would like to confirm whether my thinking is on or off base with respect to source and destination ports. Samba is being blocked by fw2loc even though I have accept rules set up. I believe I can explain why, but I could be wrong. I think that for some reason, samba is sourcing stuff on the commonly used port 137, but trying to send

An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20031208/0128c586/attachment.htm -------------- next part -------------- Thanks alot. I found the problem, with SIP firmware image was 2.* large size SIPDefault.cnf leads to Buffer overflow, I kept firmware_version field and deleted rest. That helped in upgrading the firmware to higher version.

Hi, I have been running Shorewall (v 2.0.15 nowadays) for some time to act as a firewall between my LAN and my ISP where I have a fixed IP WAN address. Recently, I got an allocation of a /28 range of public IPs to do a DMZ. The ISP tells me that they are routing the /28 range via the existing WAN address. The WAN address is not part of the /28 range. This setup should be fairly simple, from

Im new to shorewal but have read the docs includint the ping section of the FAQ but I cant seem to get the fw to respod to pings.... my policys are ... loc net ACCEPT info net fw ACCEPT info loc loc ACCEPT info fw net ACCEPT info net all DROP

This article describes how to implement "Port Knocking" in Shorewall. http://shorewall.net/PortKnocking.html -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key

I just installed Fedora Core 3 uname -r 2.6.9-1.667 I got the latest shorewall''s rpm: http://www.shorewall.net/pub/shorewall/2.2/shorewall-2.2.0/shorewall-2.2.0-1 .noarch.rpm Made my changes Attempted to run shorewall and got: [root@demo shorewall]# shorewall start ERROR: Can''t find iptables executable I haven''t seen this before. I tried to go through all the

Having moved from a "cascading LANs" configuration to two independent LANs on eth0 and eth1, I still get some "state INVALID" for which I am not sure what the cause is. Can somebody help me understand its probable origin? Thanks, Costantino [see attachment]

Hi guys, I''m not sure where to post for help on this one, shorewall or lvs, I''ll start with shorewall (only cause Tom is a gun at this stuff, and is polite enough to tell me to bugger off to the LVS list if I''m posting in the wrong one ;) I have a single box that is my router/firewall/LVS. Internet -- eth0 - router/firewall - eth1 --- internal lan | eth2

Hello, I reinstalled my Slackware 10.1 a few days ago, before i did that i stored all files in /etc/shorewall to an external HDD. After reinstallation was complete i installed shorewall and restored the config files i backed up before, but now if the FW is running i can´t ping the adsl modem and so i can´t connect to the internet using pptp. Note, it worked before with exactly the same

Dear All I have added the following line to /etc/shorewall/rules: ACCEPT net fw tcp 4662 However, the program aMule continues to give me the following error: NG : Your 4662 port is not reachable. Any further ideas? Thanks in advance, Paul

I just setup the Shorewall in my school, but now all clients can''t through to internet, all servers can through to internet with NAT, when I disabled NAT that all servers can''t through to internet. Below is my school network: internet ---> shorewall ----> loc ---> ciso router ---> loc1 Below is my config files: policy: # If you want to force clients to