search for: ppp0_masq

...pt in out source destination 73 3585 net_dnat all -- ppp0 * 0.0.0.0/0 0.0.0.0/0 54 9296 masq_dnat all -- eth1 * 0.0.0.0/0 0.0.0.0/0 Chain POSTROUTING (policy ACCEPT 1290 packets, 83016 bytes) pkts bytes target prot opt in out source destination 2 96 masq_snat all -- * eth1 0.0.0.0/0 0.0.0.0/0 9 585 ppp0_masq all -- * ppp0 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT 1113 packets, 73755 bytes) pkts bytes target prot opt in out source destination Chain masq_dnat (1 references) pkts bytes target prot opt in out source destination 0 0 DNAT tcp -- * * 192.168.0.0/24 209.5.63.205 tcp dpt:5903 to:192.168.0...

...fw to net using chain fw2net Policy ACCEPT for loc0 to net using chain loc02net Policy ACCEPT for loc1 to net using chain loc12net Policy ACCEPT for wlan to net using chain wlan2net Masqueraded Networks and Hosts: iptables: Invalid argument ERROR: Command "/sbin/iptables -t nat -A ppp0_masq -s 192.168.11.0/24 -d 0.0.0.0/0 -j MASQUERADE" Failed Processing /etc/shorewall/stop ... IP Forwarding Enabled Processing /etc/shorewall/stopped ... My masq file is: ppp0 eth0 ppp0 eth1 ppp0 eth2 When I''m starting connection and shorewall on the real nic''s without UML and...

...5.240.15 table 12 My iptables "nat" setup looks like this: Chain POSTROUTING (policy ACCEPT 364 packets, 26735 bytes) pkts bytes target prot opt in out source destination 258 19801 eth1_masq all -- * eth1 0.0.0.0/0 0.0.0.0/0 0 0 ppp0_masq all -- * ppp0 0.0.0.0/0 0.0.0.0/0 Chain eth1_masq (1 references) pkts bytes target prot opt in out source destination 252 19021 SNAT all -- * * 10.75.22.0/24 0.0.0.0/0 to:24.235.240.15 0 0 SNAT all -...

Hi All, As you probably all know :-) I''m trying to do the multi-isp thing. I''ve resolved my last issue with the route_rules as suggested by Tom and Jerry suggested. Lately I have been seeing "transient" (I say transient because the problem will persist for a while and then magically clear itself up some number of minutes later) situations where my gateway will log:

Dear List! I use a shorewall 2.0.8 on a Debian sarge system. I use a DSL connection to the Internet (ppp0 - eth1 to the modem) and a bridge to the local lan. The bridged config i''ve made with bridge.html from the shorewall site. The Bridge is between local net and a openvpn tap device. This works. I ccan make tunnels, and a can make a lot of things through the firewall. I can get a list

...of suck with OpenSwan with kernels prior 2.6.4). The problem seems to be similar or identical mentioned here: http://archives.msfree.ca/shorewall-users@shorewall.net/2003-09/msg00491.html The difference in contrast the above post is : IN THE POST: "The same command line that fails with -A ppp0_masq succeeds with -A POSTROUTING." AT MY HOST: iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -d 0.0.0.0/0 -j MASQUERADE iptables: Invalid argument I tried some variation: iptables-1.2.9 kernel-2.4.25.7mdk-1-1mdk (default 2.4 in MDK10) kernel-i686-up-4GB-2.6.3.15mdk kernel-i686-up-4GB-2.6.8...

Hi, I have a install of shorewall I have 2 interfaces(I think) ppp0[connection device] and eth0 [LAN device], I want to allow all traffic from the the internet in or aleast port 80 and CVS and webmin and mail and everything normal to the main machine with shorewall on it. I changed to policy file but it just gave me errors as to double interfaces. I also what still to alow connection sharing

...ain PREROUTING (policy ACCEPT 5 packets, 750 bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 6 packets, 294 bytes) pkts bytes target prot opt in out source destination 3 188 ppp0_masq all -- * ppp0 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT 12 packets, 1664 bytes) pkts bytes target prot opt in out source destination Chain ppp0_masq (1 references) pkts bytes target prot opt in out source...

...O=UDP SPT=513 DPT=513 LEN=92 NAT Table Chain PREROUTING (policy ACCEPT 287K packets, 35M bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 8723 packets, 382K bytes) pkts bytes target prot opt in out source destination 91 5894 ppp0_masq all -- * ppp0 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT 8828 packets, 412K bytes) pkts bytes target prot opt in out source destination Chain ppp0_masq (1 references) pkts bytes target prot opt in out source destination 0 0 MASQUERADE all -- *...

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

...ey have a source *address of the interface* while SNAT mangles the packets so they have the address you specify.. I''m hoping by using masquerade only the conntrack entries will be destroyed when the pppoe ip changes. Here''s part of my "shorewall show nat" output Chain ppp0_masq (1 references) pkts bytes target prot opt in out source destination 4860 467K SNAT all -- * * 0.0.0.0/0 0.0.0.0/0 policy match dir out pol none to:67.56.105.20 0 0 MASQUERADE all -- * * 192.168.32.0/24 0.0.0.0/0 policy matc...

Hello all, I''m somewhat new to networking, and I''m having trouble masquerading connections that are coming over a bridge. The bridge only has a single port for now, but I''m going to add more ports later. I''m basing my configuration on the two-interface quick start guide. I''m using Shorewall 3.0.4 on Ubuntu Dapper. My network looks like this: * The

...ROUTING (policy ACCEPT 88769 packets, 5812K bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 718K packets, 43M bytes) pkts bytes target prot opt in out source destination 21 1260 ppp0_masq all -- * ppp0 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT 722K packets, 43M bytes) pkts bytes target prot opt in out source destination Chain ppp0_masq (1 references) pkts bytes target prot opt in out source...