Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • X xcap-capability-linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • xcap
  • xcap-capability-linux
  • Repository
Switch branch/tag
  • xcap-capability-linux
  • net
  • ipv4
  • netfilter
  • ip_conntrack_helper_h323.c
Find file BlameHistoryPermalink
  • Patrick McHardy's avatar
    [NETFILTER]: H.323 helper: replace internal_net_addr parameter by routing-based heuristic · e44ab66a
    Patrick McHardy authored May 29, 2006
    
    
    Call Forwarding doesn't need to create an expectation if both peers can
    reach each other without our help. The internal_net_addr parameter
    lets the user explicitly specify a single network where this is true,
    but is not very flexible and even fails in the common case that calls
    will both be forwarded to outside parties and inside parties. Use an
    optional heuristic based on routing instead, the assumption is that
    if bpth the outgoing device and the gateway are equal, both peers can
    reach each other directly.
    
    Signed-off-by: default avatarPatrick McHardy <kaber@trash.net>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    e44ab66a