Re: IPFW portforwarding / kernel question

mailist_at_whoweb.com
Date: 08/23/04

  • Next message: Oliver Gould: "XFree86 Question" 
    To: Henk <dontspamhenk@xs4all.nl>, freebsd-questions@freebsd.org
Date: Sun, 22 Aug 2004 19:49:01 -0400

    I'd suggest using port forwarding with NATD instead since I'm assuming you are
    already running NAT between 192.168.1.1 and your ADSL public address. The
    natd man page covers port and address forwarding pretty well.

    On Sunday 22 August 2004 10:02 am, Henk wrote:
    > Dear FreeBSD addict,
    >
    > I am running FreeBSD 4.9-RELEASE on a machine with 4 ehternet devices.
    > 192.168.1.1 is connected to my ADSL router. My FreeBSD machine nicely
    > routs all traffic between the 4 devices.
    > rl0 192.168.1.1/24 (WAN-side)
    > rl1 10.0.10.1/24 (LAN)
    > rl2 10.0.20.1/24 (LAN)
    > rl3 10.0.30.1/24 (LAN)
    >
    > My wish is to forward all incoming tcp traffic that arrives on
    > 192.168.1.1:4265 to 10.0.10.151:4265 in the local network.
    >
    > Question 1:
    > Can somebody help me out with the right ipfw command to achieve this (or a
    > link to where *forwarding* is explained).
    >
    > Question 2:
    > Do I need to recompile my kernel with the IPFIREWALL_FORWARD option?
    >
    > My kernel is compiled with the following options:
    > # options for IPFW / NATD
    > options IPFIREWALL
    > options IPFIREWALL_VERBOSE
    > options IPFIREWALL_VERBOSE_LIMIT=10
    > options IPDIVERT
    >
    > _______________________________________________
    > freebsd-questions@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    > To unsubscribe, send any mail to
    > "freebsd-questions-unsubscribe@freebsd.org"

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

  • Next message: Oliver Gould: "XFree86 Question"

    Relevant Pages

    • Re: Need help with strange routing situation
      ... the examples for natd suggest something like: ... > work" and won't require special port forwarding or other such nonsense. ... The server is the only thing connected to the DSL modem. ... > Ideally I'd like to do this setup on the existing hardware. ...
      (freebsd-net)
    • Re: Need help with strange routing situation
      ... the examples for natd suggest something like: ... > work" and won't require special port forwarding or other such nonsense. ... The server is the only thing connected to the DSL modem. ... > Ideally I'd like to do this setup on the existing hardware. ...
      (freebsd-questions)
    • RE: Question abt NATD
      ... natd does not use the kernel for NAT - it is a user land process and uses ... Subject: Question abt NATD ... It is extreemly necessary to be able to view the NAT ... with "unsubscribe freebsd-security" in the body of the message ...
      (FreeBSD-Security)
    • Re: ipnat memory leak?
      ... It also avoids at least 2 context switches per packet... ... goes into natd and one when it goes back to the kernel. ... > natd chokes on the latest windoze worms and I have implemented some DoS ... Not to mention the syntax for doing things like stateful firewalling is much ...
      (freebsd-current)
    • Re: natd -redirect_address
      ... >> I am trying to set up natd to redirect public ips to my private ... Steve ... >> To unsubscribe, send any mail to ...
      (freebsd-questions)