Displaying 20 results from an estimated 8000 matches similar to: "start error "invalid interface" on shorewall 2.08"
2004 Sep 29
4
Re: start error]
thanks again for your sharp eye and speedy response. i have corrected the typos in the IP in the masq file. I am sorry to have to ask for more help but my pc''s on the local network can''t reach the dmz webserver using the webserver''s local or Public IP address. I need to be able to do this in order to test the split DNS setup for the network. Using ethereal on the
2004 Sep 15
15
re: start error
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The original post was over 300,000kb so I didn''t spam the list with it -TE.
|
|
| Thank you for your quick and helpful response.
|
| I didn''t understand that the virtual interface eth0:1 doesn''t count as
a separate instance from eth0.
| I am sorry to ask for further assistance and would appreciate any
help. The error
2004 Sep 10
1
Is ProxyARP or NAT entries really neccesary for DNAT to work?
I have been trying to get DNAT to work and I actually have succeeded
too, however, not how I thought it would work when reading through the
documentation.
1. No matter what I do I cannot get DNAT to work unless I have an entry
in eiter the nat or the proxyarp file. Is that really how it''s supposed
to be? I can''t find anything about it in the documentation.
2. Also, in the
2004 Sep 22
3
Strange DNAT problems with shorewall 1.4.8
I''ve had some issues with my network, and I''ve had to reconfigure my
Gibraltar CD. It runs shorewall 1.4.8, and I have a 2-interface setup, so
I downloaded the relevant files from the install page.
Masq and such works, but I''m having a problem with my port forwarding. It
works for port 22, but it doesn''t seem to work for any other port.
I''ve turned
2003 Feb 24
5
Bug in Shorewall check?
I made a boo boo in my config and put in this rule
#PPTP
DNAT net:213.67.241.162/217.209.46.204/32
loc:192.168.221.200 tcp 1723
DNAT net:213.67.241.162/32,217.209.46.204/32
loc:192.168.221.200 47 -
And the the following happened.. and I wonder why it didn''t complain? I
am sure I am just misunderstanding some doc
2005 Jan 02
1
Dnat problems with adsl-box
Hello!
So i got this problem. I have a debian sarge (with 2.6 kernel) box with
shorewall up and network something like this:
(net-ip)adsl-router(10.0.0.2)->(10.0.0.5)debian(192.168.0.1)->(192.168.0.x)lan-machines
Everything works just great but i cant get port forwarding to work.
shorewall show nat shows the traffic (to port 2002) but the machine
(192.168.0.3) isnt getting it.. I have
2005 Jan 11
2
All traffic is on the same adress
Hi
I have a trouble with my shorewall.
I have 5 Ips adresses on my internet interface.
I can ping any of these adresses, but the traffic take always the base adresse
on my interface. All the traffic is on the same adress, but I what to know
the traffric for each of these adresses.
I search a lot to find the setting for do that, I don''t know what is wrog in
my config, somebody can
2003 Sep 05
3
Confused about approach
Greetings all,
I''m a bit of a linux rookie, but a friend and I have built a
firewall running Shorewall 1.4.6c over a minimal install of Redhat 9.
Out network setup looks something like this:
Cable Modem : eth0 :12.xxx.xxx.3 (Zone is named INSIGHT)
Campus Lan : eth1 : 10.176.9.21 (Zone is named MULAN)
DMZ : eth2 : 192.168.1.0 255.255.255.0 (Zone is named DMZ)
Currently, I
2003 Jan 14
3
Shorewall-1.3.13
Just some stuff that was laying around in CVS:
1. Added ''DNAT-'' target.
2. Print policies in ''check'' command.
3. Added CLEAR_TC option.
4. Added SHARED_DIR option.
[teastep@wookie Shorewall]$ cat releasenotes.txt
This is a minor release of Shorewall that has a couple of new features.
New features include:
1) A new ''DNAT-'' action has been
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
2005 Apr 27
1
Problems with DNAT
Hi, i''m a shorewall users and i have the following problem:
I have one class C range of IP''s and i have three zones (net, dmz , loc)
I need create one rule to dnat one valid ip address (but not in use in
one computer) to one invalid host in my loc zone.
How i do?
I try this:
DNAT net:200.200.200.200 dmz:200.193.137.38 tcp
137,138,139,445 -
2004 Oct 09
2
odd problem with proxyarp and DNAT
I have some hosts in a DMZ zone with proxyarp. In my local zone I have a host to which I DNAT.
I have discovered that I can reach the host in the local zone by attempting to connect to the fw (As expected) or ANY proxyarped host in my dmz zone (as not expected). Is this normal ?
(I''ve just discovered that actually the dnated host answers to requests sent to any IP routed to my host!)
2011 Apr 15
1
Proxyarp vs DNAT
Hello list,
I am in the process of switching from IPCOP to Shorewall s the firewall
for our small office. I very much like the fact that Shorewall runs on
top of the same OS (openSuSE 11.4) that I run on the server and my desktop.
Our setup is fairly straightforward. We have 8 static ip addresses from
our ISP, which provides a cable modem and a Cisco 800 series router.
The ip addresses are
2007 Sep 25
1
DNAT PREROUTING issue with iptables
Hi,
I have an DNAT ISSUE with PREROUTING.
This is my setup.
I have 2 firewalls running iptables.
Pls asume 1.2.3.4/29 is the internet interace of FIRST firewall.
2.3.4.5/29 is the internet interface of SECOND firewall. it has DMZ zone. in
that DMZ zone, mail server runnig @ 192.168.100.3
Now I want to DNAT port 25 of FISRT firewall (i.e - its ip address -
1.2.3.4/29) to the internet ip
2005 Mar 06
1
3 Interface problem
Having a problem with the 3 interface setup. I can get DMZ hosts, and
FW to see internet, but anything on LOC interface is unable to get
out. My first post to the list didn''t have the information needed,
sorry for that, but thank you for pointing me to more resources. I''ve
looked at the problem myself some more, but am still stuck.
Shorewall Version: 2.2.1
ip addr show
1:
2004 Oct 08
6
clean install with 3 ip addresses
i am doing a clean install on fedora
core 2 using the shorewall rpm and the
Shorewall Setup Guide for multiple
IP''s using a stock configuration except
for AllowDNS and AllowWeb on the
firewall (so i can post this message).
my shorewall status file is attached.
my setup
69.17.65.105 = firewall
69.17.65.22 = dmz server 1
69.17.65.161 = dmz server 2
my local network is
2004 Aug 22
6
LAN to DMZ zone issues.
Hello all,
Name is Andrew and in desperate need of some info.
Setup:
- Mandrake 9.1 with three interfaces
(eth0 --> WAN) C-class /28 network (with tree virtual addresses which I
am DNAT-ing to the DMZ)
(eth1 --> LAN) A-class 10.0.0.0/8
(eth2 --> DMZ) A-class subnet 10.1.123.0/24
- Running stock Shorewall ver: shorewall-1.3.14-3.1.91mdk
Dilemma:
- LAN can not access the DMZ zone
2008 Oct 01
2
DNAT Issue
Hi.
Im setting up a web farm test lab. I have a number of machines in the
test last on a dmz zone on network 10.20.30.0.
The test lab firewall has two NICS. One (eth0) has two ip addresses,
eth0 10.161.101.40 and eth0:0 10.161.10.49. The other one, eth1 is
on a private network, 10.20.30.0.
I want to use DNAT to allow test engineers to ssh into the machines in
the web farm. I have
2003 Oct 21
2
problems
In the last 15 minutes I have had a major firewall running Shorewall display
some problems. This machine has been working fine for the better part of a
year, no changes made in the last week. This machine has three zones. There
is a DNAT running from the net zone and the loc zone to a webserver in the
dmz port 80 only. The DNAT from the loc zone seems to not be working
correctly. If I make a web
2005 Jan 25
2
DNS, DNAT and Notifies
I have a pretty straightforward shorewall (v 2.0.12) setup in my Phoenix
office.
IP addresses on the firewall
eth0 172.16.10.249
eth1 12.47.198.100
eth1:1 12.47.198.108
eth1:2 12.47.198.101
eth2 172.16.11.249
interfaces:
loc eth0 detect
net eth1 detect blacklist
dmz eth2 detect
vpn1 tun1 192.168.124.255
zones
net Net