Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
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.
  1. #11
    Just Joined!
    Join Date
    Nov 2011
    Posts
    7

    yup, i will try to look into the iptables again...atreyu, thanks so much for your help!!

  2. #12
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    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.

  3. #13
    Just Joined!
    Join Date
    Nov 2011
    Posts
    7
    Hi atreyu, you are RIGHT!!
    I have solved the issue after removed the entries from FORWARD chain:

    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
    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)

    Thanks again for your help!

  4. #14
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    w00t! glad its sorted...

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •