Results 11 to 14 of 14
yup, i will try to look into the iptables again...atreyu, thanks so much for your help!!...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 11-22-2011 #11Just Joined!
- Join Date
- Nov 2011
- Posts
- 7
yup, i will try to look into the iptables again...atreyu, thanks so much for your help!!
- 11-22-2011 #12Trusted Penguin
- Join Date
- May 2011
- Posts
- 3,657
Just a thought - you might want to back up your existing iptables config file, and essentially start from scratch. Just add your rules one-by-one until you hit a snag.
- 11-23-2011 #13Just Joined!
- Join Date
- Nov 2011
- Posts
- 7
Hi atreyu, you are RIGHT!!
I have solved the issue after removed the entries from FORWARD chain:
obviously it reject packets after NAT chain finish...that's why the port forward not working...I have no idea why these rule exist (or maybe it already exist before reboot, just don't know why no effect at all)Code:-A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -s 192.168.122.0/24 -i br0 -j REJECT --reject-with icmp-port-unreachable
Thanks again for your help!
- 11-23-2011 #14Trusted Penguin
- Join Date
- May 2011
- Posts
- 3,657
w00t! glad its sorted...


Reply With Quote
