#18141: UDP and established TCP connections/NAT holes get terminated
---------------------------+-----------------------------------------------
  Reporter:  mravouk       |      Owner:  developers
      Type:  defect        |     Status:  new
  Priority:  response-     |  Milestone:
  needed                   |    Version:  Trunk
 Component:  kernel        |   Keywords:  UDP TCP NAT connection terminated
Resolution:                |
---------------------------+-----------------------------------------------

Comment (by mravouk):

 I've finally solved the problem. It was a combination of two factors where
 one had nothing to do with OpenWRT. On my end it was a script that
 triggered a '''/sbin/fw3 restart''' on external input at certain times,
 and on the OpenWRT side it was the above mentioned change to
 '''firewall3''' which introduced nat flushes.

 I changed the script to execute '''/sbin/fw3 reload''' instead and hacked
 the firewall3's '''main.c''' to load user script '''/etc/firewall.user'''
 on reload.

 My question is: Is the default behaviour of not loading the
 '''/etc/firewall.user''' on reload desirable?

 The ticket may be closed.

--
Ticket URL: <https://dev.openwrt.org/ticket/18141#comment:8>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to