Hello Greg Kochanski, have your problem with Fiaif been settled? If not let me suggest some means for diagnosing your difficulties. In a probably related report #560008, the only solution was to downgrade Fiaif.
First off, that entry [FIAIF_ZONE_MISS_INTD] concerns traffic generated by CUPS as it broadcasts to its local segment about its presence. Your problem is that forwarding between network segments is not properly working. What output do you get from this? $ sysctl -a 2> /dev/null | grep 'ipv4.*\.forward' You should at least get value 1 for 'eth1' and for 'eth2'. If this is not the case, issue # sysctl net.ipv4.conf.eth1.forwarding=1 # sysctl net.ipv4.conf.eth2.forwarding=1 and test your inter-ubuntu connection. In the following I suppose you have some knowledge of 'iptables'. Otherwise, please tell me to rephrase my explanations. The next test is to issue print-outs similar to # iptables -nvL FORWARD by using successively progressing targets in place of 'FORWARD' that will appear in the netfilter rules printed from a previous command. In the output, do you find the expected ACCEPT-rules that use 'state RELATED,ESTABLISHED'. Does the DROP policy at the table head claim many blocked packages? That would indicate that the desireable forwarding rule is never reached. General questions: Are eth1 and eth2 assigned to the same networks as before the upgrade? I am considering the possibility that udev have made other assignment decisions of some unknown reason. Have you double checked the definitions you feed into Fiaif? The difficulty is that your problem report leaves very large room for guessing, and small aid in determining the cause. Kind regards, -- Mats Erik Andersson, fil. dr
signature.asc
Description: Digital signature
