similar to: Dumb Question for Interface Variable

I have an old Pentium II which I use as a gateway and firewall for a home network. The external interface is a modem on ppp and the internal interface is ethernet. I have had this setup running successfully for many years starting with the early 2.x series Shorewall. My ISP recently changed my dial-up ''phone number and presumably also the system at the other end of my modem (they

I have several computers connected to the internet through a DSL router that assigns rfc1918 (192.168.1.x) addresses to the systems connected. I have a server where shorewall is installed with one interface eth0, with a static ip (192.168.1.3). The router is configured to forward all connections from the internet to the linux server. I''d like to know how I can configure shorewall to

I want to use fprobe-ulog (http://fprobe.sourceforge.net/) to generate NetFlow information about traffic going through my router. The question is how to get the logging rules added to the appropriate chains (I''m assuming eth2_in and eth2_out in my case)? I''m using the perl version of shorewall 4.0.6. -- Orion Poplawski Technical Manager 303-415-9701

Hi all! I am a long time lurker, but have not posted until now. My old trusted firewall machine broke a couple of weeks ago and I replaced it with a XEN domU that is using DNAT and has two interfaces. The firewall domU and the FTP server domU are both guests on the same dom0. All three machines are running Debian/etch (stable) and Shorewall has version 3.2.6. I can''t get FTP to work

Attempting to setup a dual ISP on a gentoo box but I''m not sure how to configure the routing in the /etc/conf.d/net configuration file. Does shorewall do all the routing or do I set just the default route to the PRIMARY outbound ISP? Vernon ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net

Hi, I am running OpenVPN where i have one central hub VPN server, and multiple spoke VPN clients. I can ping from each client to the server and each client to computers on the subnet which the server resides (192.168.2.0/24) so it works ok there. I cannot however, ping from one client to another client. I guess the packet path would go: clienta -> vpn -> shorewall/router -> vpn ->

Guys, After i got the port forwarding and everything else working as per my previous post, i ran a shields-up scan from grc.com on the firewall, i.e. a scan of the external interface. I m a little suprised at the results. On the firewall i have postfix running ( smtp port 26 ), openssh ( ssh port 22) and port forwarding of port 85 (on the firewall ) to an internal host. The Shields-Up scan

Hi folks, I had a few questions in regards to the CentOS AMI: Are there instance backed versions of the AWS marketplace CentOS builds? It looks like there might have been at one point, but I'm not seeing them now, and since they're marked as being from the marketplace we're having some difficulties attaching the volumes to another system to create an instance backed version of it.

Given that a 4-day silence on this list is almost unprecedented, thought I had better send a test post. Apologies for the spam. ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB

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

hi, I am running shorewall 3.2.9 on Mandriva2007 with 2 ISPs. Certain local IPs are directed to a specific ISP in route_rules, and this was working perfectly. I had to reinstall Mandriva, and after that this redirection is not working. My files are: masq: eth1 192.168.10.3 202.71.146.210 eth2 202.71.146.210 192.168.10.3 eth1 eth0 202.71.146.210 eth2 eth0 192.168.10.3 interfaces:

>> Only one remark. Information about 'init' file i found only in >> releasenotes.txt for 4.1.6 (for setting up 'ifb' module) and i found >> 'initdone' file in Shorewall config directory and without manfile also. >> For me not very clearly as it use. > > http://www.shorewall.net/shorewall_extension_scripts.htm On this page i found a

Hello, I searched centos7 in the AWS marketplace for the at-time-of-writing-latest centos7 image: https://aws.amazon.com/marketplace/pp/B00O7WM7QW?qid=1524138193326&sr=0-1&ref_=srh_res_product_title I built a standard free tier t2.micro from this putative 1803_01 AMI. I see from the docs, this is thus a March 2018 compilation. When I get CLI, I get this: [centos at ip-172-31-27-32

Hi, I recently discovered http://zaf.github.com/asterisk-mstts/ . In the page above, it is mentioned you have to subscribe to Microsoft Translator API on Azure Marketplace. In Azure Marketplace, I found something called "Microsoft Translator". This API is free within a 2 000 000 characters per onth limit. Is this the API needed for MS TTS ? If not, where and how can I find the good

Greetings! Can someone please explain the process for publishing CentOS 7 AMI's to AWS? I see the "official" CentOS marketplace page here: https://aws.amazon.com/marketplace/pp/B00O7WM7QW However, if I select us-west-2 and launch based on the current AMI that was released on 2/26/2016, I see that it is CentOS 7.2.1511 at boot up. Do new AMI's get published on a particular

On Wed, Apr 29, 2015 at 11:33 PM, Kelly Prescott <kprescott at coolip.net> wrote: > to follow-up, I will give an example. > Here is the listing for the official centos AMI: > > IMAGE ami-96a818fe aws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS > HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace > available public [marketplace:

https://forums.aws.amazon.com/thread.jspa?messageID=481859&#481859 https://forums.aws.amazon.com/thread.jspa?messageID=453572&#453572 This is a timebomb waiting to strike so many people who like do daily snapshot backups and keep them for few weeks and not realizing their snapshots are useless if they had accidentally mess up some boot related file earlier on. Another scenario you mess

Hi, I'm seeing some strange behavior when trying to use the latest CentOS 7 AMI from the AWS marketplace. The AMI that we've been using previously is "ami-02eac2c0129f6376b" released January 30, 2019 at 6:40:58 PM Today I saw a new AMI with ID "ami-0c3b960f8440c7d71" that was released February 21, 2020 at 3:50:07 Both these AMIs are owned by AWS account

I''m looking over this traffic shaping available in the tc* files. I went through this when I did my own traffic shaping outside of shorewall previously. For the average (i.e. home, perhaps) user, I''ve never understood why we use these more complicated shaping algorithms that define classes and guaranteed minimums and maximums and so forth. For most home, or other small use

Hi all, Another Debian Etch fan here, running shorewall (shell) 3.2.6-2 (and Yes I''m going to upgrade when Lenny goes stable). I already have the SSHKnock working, as documented on the website: http://www.shorewall.net/PortKnocking.html Thanks, works great! In addition to the knock to open 22, I want to also ADD a redirect, from 2222 to 22 on an internal box. So, when I knock on 1600