coldwizard
Regular Contributor
See this post....
http://www.snbforums.com/threads/fork-update-for-374-43-available.18914/page-41#post-157359
From the reading I did, it's basically a quirk in INVALID state processing that can sometimes hit packets it shouldn't.
You should not delete the INVALID state rule. I believe one of it's purposes is to block invalid packets that hackers use like xmas configured packets.
I should tell you that my network is subneted over two routers and I can print from one subnet to a printer in the other IPV4 subnet with no problems. My configuration is even a little more complicated than that, the guest port on the gateway router is also on its own bridge. The second router (running in router mode with NAT disabled) is connected to that port with it's own subnets (both IPV4 and IPV6).
Reading top down what I have is
Internet connection
|
Gateway router
- some ports and the WiFi are private network (IPV4 -1/ IPV6-1)
- the printer is connected to this private network (wired)
- some ports are split off onto a br3 bridge forming my guest network (IPV4-2/IPV6-2)
- custom iptables rules limit the guest network to just the Internet or the printer. Also of course DHCP and DNS on the router itself.
|
| one of the guest ports is connected router#2
|
Router#2
- gets its wan connection DHCP from the Gateway router for both IPV4/IPV6 (It also gets a delegated IPV6 prefix)
- Its WiFi and network have guest access since the port it is connected to is limited to guest.
- It is configured with NAT disabled.
- It serves out it's network to (IPV4-3 / IPV6-3)
|
Notebook obtains an IPV4-3 and IPV6-3 address.
I hope that makes sense. Anyway from the Notebook on IPV4-3 network I can print to the printer on IPV4-1 network. It also works if the notebook is connected to either IPV4-2 or IPV4-1 locations. Because of my custom iptables, when connected to the IPV4-3 network, the notebook cannot connect to anything else on the IPV4-1 network.
And before you ask:
- The IPV4 networks are all normal /24 mask
- The IPV6 networks are all /64 mask
- Yes IPV6 also works between the subnets where permitted by the firewall.
- No I do not use the GUI to configure the subnet routing. I had the configure the br3 in scripts so just added the IPV4/IPV6 routing there.