Re: [Shorewall-users] Shorewall system hosting KVM virtual machines

[Tom E. <te...@sh...>]

On 9/8/12 4:16 PM, Steve Thompson wrote:
> On Sat, 8 Sep 2012, Tom Eastep wrote:
> 
>> If you can't get it sorted out, please post the output of 'shorewall
>> dump' as a compressed attachment.
> 
> Thanks Tom. The basic configuration has been in operation for over 5
> years with no problems. It is only when I introduce a virtual machine on
> the firewall system, and desire to communicate with it using any of its
> IP addresses, that this problem occurs. I've attached the dump, since I
> am stuck.
> 

Here's a clue. We see this log message:

Sep  8 19:14:37 br2_rec:REJECT:IN=br2 OUT=br1 SRC=192.168.0.23
DST=192.168.4.2 LEN=76 TOS=0x00 PREC=0x00 TTL=127 ID=6379 PROTO=UDP
SPT=123 DPT=123 LEN=56

It is being rejected because there is maclist no entry for 192.168.0.3
on br2 (which is the bridge on which this packet was received).

In fact, there is no maclist entry for that IP address at all. When you
see packets being rejected in one of the _rec chains, you must check
your maclist entries.

Let's try to solve the other problem where no 'maclist' entries are
present. Please:

1. Remove 'maclist' from all interfaces.
2. Restart the firewall.
3. Try a connection that fails.
4. Capture and post the output of 'shorewall dump'.

-Tom

PS -- What in the world are you trying to accomplish with this
configuration? I've never seen anything so bizarre (dozens of RFC1918
addresses being DNATed to public IPs). Surely there has to be a better way.
-- 
Tom Eastep        \ When I die, I want to go like my Grandfather who
Shoreline,         \ died peacefully in his sleep. Not screaming like
Washington, USA     \ all of the passengers in his car
http://shorewall.net \________________________________________________