Shorewall error after system change

AmokPaule

Member
May 10, 2010
44
0
6
Hello,
my system is moving to new hardware. Im using the exact same configuration for shorewall as i used on my old system (ips changed of course) just with debian 6 as host.
When i now start shorewall it starts to spam my terminal with the follwoing message:
sShorewall:net2dmz:DROP:IN=eth0 OUT=venet0 SRC=77.186.239.1 DST=<ipv4 ve ip> LEN=40 TOS=0x00 PREC=0x00 TTL=115 ID=6386 PROTO=UDP SPT=54655 DPT=64738 LEN=20
topShorewall:net2dmz:DROP:IN=eth0 OUT=venet0 SRC=77.186.239.1 DST=<ipv4 ve ip> LEN=40 TOS=0x00 PREC=0x00 TTL=115 ID=6387 PROTO=UDP SPT=54655 DPT=64738 LEN=20
Shorewall:net2dmz:DROP:IN=eth0 OUT=venet0 SRC=77.186.239.1 DST=<ipv4 ve ip> LEN=40 TOS=0x00 PREC=0x00 TTL=115 ID=6388 PROTO=UDP SPT=54655 DPT=64738 LEN=20

I have no clue on whats going on.
I followed this guide to set shorewall up
http://montanalinux.org/proxmox-ve-with-shorewall.html
 
That is traffic being blocked by shorewall. Do you have "info" set within your policy file for the block line?

You won't get much help with shorewall from this forum as it has absolutely nothing to do with proxmox.

If you run "shorewall check" does it come back without any errors reported?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!