Displaying 10 results from an estimated 10 matches for "iqom".
Did you mean:
idom
2010 Feb 02
17
WG: Suddenly DMZ can't access to internet
net dmz:192.168.0.1 tcp 80
I forgot to mention that this should be put to rules file, sorry.
_____
Von: Michael Weickel - iQom Business Services GmbH [mailto:mw@iqom.de]
Gesendet: Dienstag, 2. Februar 2010 17:37
An: ''Shorewall Users''
Betreff: AW: [Shorewall-users] Suddenly DMZ can''t access to internet
No.
For example. If you want to grant access from net (whole internet) to dmz´s webserv...
2010 Feb 02
8
Suddenly DMZ can't access to internet
Hello
We are using old version ( shorewall-3.0.7-1) with Centos 5.3
The shorewall has three zones (net / loc / dmz).
Loc can access to internet with no problem and can access to DMZ.
DMZ can''t access to internet.
Net can''t access to DMZ with NAT.
I tried to restart the machine / check Lan card / check cable , they were work find.
Is it DMZ Lan card problem? but it can
2010 Feb 20
0
Request for iproute2/shorewall engineer
...ing.
The request is only about design and not about implementation.
I would be happy if someone thinks that his expertise meets my need. If this
is true feel free to ping me by e-mail.
Mit freundlichen Grüßen / with best regards
---------------------------------------------------------------
iQom Business Services - Part of your Business
---------------------------------------------------------------
iQom Business iQom Business Services GmbH
Michael Weickel Mergenthaler Allee 77
65760 Eschborn
e-mail. mw@iqom...
2010 Mar 01
1
WG: NAT Issue
Forget about my part to nat file. I was wrong. Try my masq configuration.
_____
Von: Michael Weickel - iQom Business Services GmbH [mailto:mw@iqom.de]
Gesendet: Dienstag, 2. März 2010 00:17
An: ''Shorewall Users''
Betreff: AW: [Shorewall-users] NAT Issue
Try
1.1.1.198 eth0 172.16.1.23 no no
INTERFACE - interfacelist[:[digit]]
Interfacees that have the EXTERNAL ad...
2010 Feb 05
16
DNAT Problem
Hi,
I have a client behind shorewall which has 2 IP:
192.168.8.35 is the real IP and 192.168.8.37 is the virtual IP.
I have added DNAT rules into shorewall:
DNAT net loc:192.168.8.35 tcp 11008 - 1.2.3.4
DNAT net loc:192.168.8.37 tcp 55000 - 1.2.3.5
1.2.3.4 and 1.2.3.5 is virtual IP
2009 Nov 21
5
WG: Policy make troubles once multiple zones are applied
...horewall to the public internet.
So from my side there stays nothing against configuring 0.0.0.0/0 in
multiple zones but I am still interested why the need occurs in my special
environment.
Any help would be appreciated.
Cheers
Mike
-----Ursprüngliche Nachricht-----
Von: Michael Weickel - iQom Business Services GmbH [mailto:mw@iqom.de]
Gesendet: Samstag, 21. November 2009 01:17
An: ''Shorewall Users''
Betreff: Policy make troubles once multiple zones are applied
Hi all,
I am running into some curious problems with hosts and interfaces.
My interface vlan3005 has the i...
2010 May 22
12
[ASK]How Many Interfaces Supported?
Hi,
I have 8 ethernet cards installed. Is it possible to use eth0-eth6 as the net interface for shorewall and eth1 as the lan network? Thanks.
sangprabv
sangprabv@gmail.com
------------------------------------------------------------------------------
2008 May 30
3
shorewall vrf support
Hey guys,
I have a question regarding shorewall and vrf functionality.
I have shorewall 3.4.8 and kernel 2.6.24-gentoo-r8
I have tried to use iproute2 (ip route and ip rule) to establish multiple
routing tables. The biggest problem seems to be, that I cannot add
interfaces such as vlan interfaces to the routing table.
My target is that linux takes attention of on which vlan interface
2010 Apr 16
3
Route availability check
Hi list,
is it true that Shorewall is not willing to forward traffic from a source-ip
which is not reachable by a static route from Shorewall itself? To say it on
another way. If Shorewall´s routing interface is neither connected nor able
to reach that source ip does it forward or deny it?
So the situation is the following. I send from an ip which is not part of
interface nor hosts file. But
2010 Nov 25
13
VLAN martians
I''m playing around with VLAN''s and I have a VLAN capable (layer 2) smart
switch. I see a steady stream of martians in the logfile if I have the
routefilter option set on the loc zone interfaces in
/etc/shorewall/interfaces. I have two interfaces in the loc zone, eth1
and vlan2 respectively. vlan2 is an 802.1q trunk going towards the switch.
Is this the expected behavior in