similar to: Shorewall 1.3.7

Dear All, After installing Shorewall, on a router with 4 NIC, seems running ok. Next day, when connecting from clients, (MS) we keep getting ip conflict for non-conflicting ip addresses. Any help is appreciated. Detals of Startup: + shift + nolock= + ''['' 1 -gt 1 '']'' + trap ''my_mutex_off; exit 2'' 1 2 3 4 5 6 9 + command=start +

I''m beginning to believe that the use of the last column in the rules file to designate redirection/forwarding is too subtle for many users. For 1.3, I think I''ll do something like the following: Current rule: ACCEPT net loc:192.168.1.3 tcp 80 - all New rule: FORWARD net loc:192.168.1.3 tcp 80 Current rule: ACCEPT net fw::3128 tcp 80 - all New rule: REDIRECT net

"shorewall refresh" is not handling FORWARDPING=Yes properly in 1.3.7a. After a refresh, the configuration is the same as it would be with FORWARDPING=No. There''s a corrected firewall script available from http://www.shorewall.net/errata.htm. Sorry for the inconvenience... -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ:

The rule: ACCEPT loc $FW::3128 tcp www doesn''t work propertly, the http access does not redirect to squid but directly exit. what''s wrong? Thanks ------- Dario Lesca (d.lesca@ivrea.osra.it) -------------------------------------- @@@@@@@ this is my shorewall-1.2.13 config: #[/etc/shorewall/common.def]-----------------------------------------------

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here's the output from running sshd in debug mode: debug1: sshd version OpenSSH_3.7p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA debug1: setgroups() failed:

the CNAM info in the Q.931 call setup message. I've tried all permutations of switchtype (dms100 & national) and facilityenable that I can think of, but I still don't see CNAM coming out the other side. Telco confirms that "Name Out" is enabled on our PRI. Any pointers on what I'm missing, and/or how to debug further? zapata.conf: --- [channels] context=3Ddefault

I apologize for the first message. :) --------------------------------------- I have an FTP server running in the DMZ section of my home network. It uses port 23000 for connection and ports 19990 to 19994 for data transfer. I have setup the following rule for outside people to connect to it: DNAT net dmz:192.168.2.2 tcp 23000 I''m at work right now and I can''t use

I''ve begun to think about 2.0. I would like to hear any ideas about what you would like to see included. Before I decide what new things will be implemented though, I want to nail down what WON''T be included. Here is my list: a) Old Ping Handling. There won''t be any ''noping'' or ''forwardping'' interface options and there

Dial(UniCall/g1|300|) Where is the number you want to reach? I'd expect to see Dial(Unicall/g1/1234567890|300) To reach number 1234567890 - Mois=E9s Silva On Jan 30, 2008 1:21 PM, Roger C. Beraldi Martins <rogerberaldi at gmail.com> wrote: > Dears, > > After weeks trying to contact support of my telecom about 'Seize Ack' > because that is not returned, was a

The first 1.4.0 Beta is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta Function from 1.3 that has been omitted from this version includes: 1) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4 behavior is the same as 1.3 with MERGE_HOSTS=Yes. 2. Interface names of the form

Here is the proposed content -- I''m looking for a Beta to start in the next week or so with release around the middle of next month. The main focus of 1.4 will be to provide external behavior similar to the upcoming 2.0 release. Function from 1.3 that has been omitted from this version includes: 1) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4

Hi, I just install Mandrake Linux 9.0 and it use shorewall. My first impression are extremily positive. But I simply can''t ping outside my machine. I verify that my route table is ok. It just cant''t ping in the same network! :( Any sugestions? # iptables -L | grep icmp ACCEPT icmp -- anywhere anywhere state NEW,RELATED,ESTABLISHED ACCEPT icmp

1.3.7 was not a resounding success :-( 1.3.7a is now available... -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

Regarding consistency of the FrontPages: For example the pages wiki.centos.org/de wiki.centos.org/zh wiki.centos.org/zh-tw contain "#redirect XX/FrontPage" and the "XX/FrontPage" contain the actual wiki pages /"Source codes"/ In case of wiki.centos.org/fr wiki.centos.org/es for example, the wiki.centos.org/YY contain the actual pages and the YY/FrontPage have an

Thanks. I changed translation block in http://wiki.centos .org/Manuals/ReleaseNotes/CentOS7 <http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7/Korean> . And, Is there any method to view wiki raw source of http://wiki.centos.org/FrontPage for translation ? Maybe i don't have enough permission. I'm planning to translate FrontPage and sub menus (Download , Search, Contribute....)

My wiki username is HoLee . Now, the simplified chinese frontpage is maintained by TimothyLee. Because of his efforts ,the Traditional Chinese Frontpages and Simplified Chinese Frontpages are created and maintained very well. I know that TimothyLee is from Taiwan,so the Simplified Chinese Frontpage is translated from Traditional Chinese Frontpage directly.So,there are some sentences is

On 9 December 2014 at 13:50, Ho Lee <huanying2000a at gmail.com> wrote: > My wiki username is HoLee . > Now, the simplified chinese frontpage is maintained by TimothyLee. > Because of his efforts ,the Traditional Chinese Frontpages and > Simplified Chinese Frontpages are created and maintained very well. > I know that TimothyLee is from Taiwan,so the Simplified

hi, I have the following configuration: Grandstream --> NAT (Netgear RP614)-->Internet-->Asterisk(public IP) i can register fine and call ringing is working as good. The problem is = i cant hear audio both ways and i get this error: WARNING[22544]: File rtp.c, Line 375 (ast_rtp_read): RTP Read error: Resource temporarily unavailable my sip.conf file is as follows:

I am setting up my httpd.conf file so I can secure a site create in RubyonRails. The problem that I am having is: File does not exist: /usr/home/mhale/hieraki-1.0.2/public/frontpage/index File does not exist: /usr/home/mhale/hieraki-1.0.2/public/frontpage/index File does not exist: /usr/home/mhale/hieraki-1.0.2/public/frontpage/index So apache is reading "frontpage/index" as a

Shorewall 1.3.3 is now available for download. In this release: 1. Entries in /etc/shorewall/interface that use the wildcard character ("+") now have the "multi" option assumed. 2. The ''rfc1918'' chain in the mangle table has been renamed ''man1918'' to make log messages generated from that chain distinguishable from those generated