Hello,
Handbook section 31.9 describes the setup of NAT.
Section 31.9.3 suggests net.inet.ip.fw.default_to_accept=1 during
the first attempts to setup a firewall and NAT gateway.
Section 31.9.5 suggests I specify a predefined firewall ruleset that
allows anything in with firewall_type=OPEN
On Fri, 11 Oct 2013 04:38:45 +0200, Chris Stankevitz
chrisstankev...@gmail.com wrote:
Hello,
Handbook section 31.9 describes the setup of NAT.
Section 31.9.3 suggests net.inet.ip.fw.default_to_accept=1 during
the first attempts to setup a firewall and NAT gateway.
Section 31.9.5 suggests I
On Thu, Oct 10, 2013 at 8:22 PM, Michael Ross g...@ross.cx wrote:
ipfw always has one default rule, standard is
[snip]
Specifing firewall_type=OPEN gives you an additional rule
Michael,
Thank you that is exactly what I am seeing.
Chris
___
Does anyone know how to get NAT loopback (aka NAT hairpin or NAT
reflection) working with natd and ipfw? It seems to work with the
in-kernel NAT without the need for configuration, but not if you're
using natd.
I have a feeling it may be something do do with the ipfw
diverted-loopback test
Hi all
I'm on 192.168.1.62, the server running on 192.168.1.3 and listen to port 1234.
I want any connection going out of my machine to port 1234 to port forward to
192.168.1.3:1234.
But when I attempt to connect to 192.168.1.1:1234 , natd shows following
verbose message:
natd[2051]: Aliasing
Will natd forward rtmp:// ???
freebsd# cat /etc/natd.conf
use_sockets
redirect_port tcp 192.168.0.3:3389 10.1.10.172:3389
redirect_port tcp 192.168.0.2:1935 10.1.10.172:1935
redirect_port tcp 192.168.0.2:8790 10.1.10.172:8790
redirect_port tcp 192.168.0.2:6000-6100 10.1.10.172:6000-6100
On 8/27/2010 9:14 PM, Michael J. Kearney wrote:
Will natd forward rtmp:// ???
I am sure libalias and natd know nothing about rtmp.
freebsd# cat /etc/natd.conf
use_sockets
redirect_port tcp 192.168.0.3:3389 10.1.10.172:3389
redirect_port tcp 192.168.0.2:1935 10.1.10.172:1935
redirect_port
Hi there, a few months ago I inquired about an issue where using
ipfw+natd worked on 8.0 but produced errors in 8.1. After searching the
bugs database, I found multiple reports about it -
http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/148137 and
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern
Since a rebuild to FBSD 8.1, I can't get natd to function correctly. Below is
my ipfw config. It closely follows the example in the Handbook.
http://www.freebsd.org/doc/en/books/handbook/firewalls-ipfw.html (30.6.5.7 An
Example NAT and Stateful Ruleset -- Ruleset #1)
firewall config (logging
Здравствуйте, Casey.
00300 0 0 deny ip from 192.168.0.0/16 to any in via fxp0
00301 0 0 deny ip from 172.16.0.0/12 to any in via fxp0
00302 0 0 deny ip from 10.0.0.0/8 to any in via fxp0
00303 0 0 deny ip from 127.0.0.0/8 to any in via fxp0
00304 0
I haven't had a chance to work on this yet. I'll be out of town for a little
while, and will update the thread upon my arrival.
Thanks.
Casey
- Коньков Евгений kes-...@yandex.ru wrote:
Здравствуйте, Casey.
What does natd with '-v' options shows? what is aliasing?
You must bind
I recently rebuilt a server from 7.x to 8.x. Using the exact same firewall
natd config, natd appears not to be aliasing the private address when the
traffic leaves the external interface. When sniffing traffic w/ tcpdump, I see
the private address as the source address on the outbound
Здравствуйте, Casey.
What does natd with '-v' options shows? what is aliasing?
You must bind natd to external interface
NEVER DO: any to any divert!!!
NOTICE: no traffice go through this rule
CS 05000 00 divert 8668 ip from any to any out via fxp0
NEVER DO: open firewall because
Just a sidenote:
On Sat, 15 May 2010 02:33:10 +0200, umage theultram...@gmail.com wrote:
However, if I
run the script manually, or call it from the end of /etc/rc, it will add
these rules as well. Currently I am using a workaround.
It's not a good idea to modify /etc/rc. In your case, using
I performed a kernel+world update of my freebsd router, RELENG_8 branch,
apparently from the version 6 months ago to current. I use ipfw and a
shell script that gets loaded at startup. I noticed after rebooting that
ipfw did not load two rules, both of type divert natd. However, if I
run
rules, both of type divert natd. However, if I
run the script manually, or call it from the end of /etc/rc, it will add
these rules as well. Currently I am using a workaround.
Best to ask -STABLE. There's been some breakage of ipfw since end of
April. I'm unsure as to whether they've all
Hey there, I run a test server here at the house that also runs natd to
share internet across the network. The past few weeks my free space on
/var was running dangerously low. After some investigation, I found out
that the used space was actually an open file, and here is what lsof
showed me
Is there a good guide somewhere for migrating from ipfw and natd rules
to pf? I had pretty much gotten used to ipfw, and now pf seems very
different to use and understand.
--
John Lind
j...@starfire.mn.org
___
freebsd-questions@freebsd.org mailing
On Tue, 9 Feb 2010 08:59:07 -0600
John j...@starfire.mn.org wrote:
Is there a good guide somewhere for migrating from ipfw and natd rules
to pf? I had pretty much gotten used to ipfw, and now pf seems very
different to use and understand.
http://www.openbsd.org/faq/pf/index.html
On Tue, 9 Feb 2010 10:54:45 -0600
John j...@starfire.mn.org wrote:
On Tue, Feb 09, 2010 at 03:31:34PM +, RW wrote:
On Tue, 9 Feb 2010 08:59:07 -0600
John j...@starfire.mn.org wrote:
Is there a good guide somewhere for migrating from ipfw and natd
rules to pf? I had pretty much
The natd man page says it is still necessary to create a customer
kernl with
options IPFIREWALL
options IPDIVERT
Is that still true, or can it be accomplished vi a loader.conf?
Thanks!
--
John Lind
j...@starfire.mn.org
___
freebsd-questions
On Mon, 8 Feb 2010, John wrote:
The natd man page says it is still necessary to create a customer
kernl with
options IPFIREWALL
options IPDIVERT
Is that still true, or can it be accomplished vi a loader.conf?
It's a kernel option, so you probably can't do it at runtime.
Consider using pf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/2010 15:39, Warren Block wrote:
On Mon, 8 Feb 2010, John wrote:
The natd man page says it is still necessary to create a customer
kernl with
options IPFIREWALL
options IPDIVERT
Is that still true, or can it be accomplished vi
On Mon, Feb 08, 2010 at 08:39:14AM -0700, Warren Block wrote:
On Mon, 8 Feb 2010, John wrote:
The natd man page says it is still necessary to create a customer
kernl with
options IPFIREWALL
options IPDIVERT
Is that still true, or can it be accomplished vi a loader.conf?
It's
Hello,
The natd is with 100% cpu usage. What is the issue ? can you help
me with that ?
CPU: 3.4% user, 0.0% nice, 22.2% system, 9.5% interrupt, 64.9% idle
Mem: 161M Active, 493M Inact, 345M Wired, 652K Cache, 417M Buf, 2934M Free
Swap: 4096M Total, 4096M Free
PID USERNAME
Please copy me on replies.
I am testing ipfw and natd on a gateway machine running FreeBSD
7.2-STABLE #0: Tue Oct 27 00:12:39 PDT 2009 with the generic
kernel. ipfw.ko and ipdivert.ko are loaded as modules, since
they're not part of the GENERIC kernel.
The symptom is that scp uploads from
In freebsd-questions Digest, Vol 286, Issue 4, Message 16
On Mon, 23 Nov 2009 15:28:12 -0800 James Long l...@museum.rain.com wrote:
Please copy me on replies.
I am testing ipfw and natd on a gateway machine running FreeBSD
7.2-STABLE #0: Tue Oct 27 00:12:39 PDT 2009 with the generic
On Wed, Sep 2, 2009 at 1:02 AM, Razvan Cristea cristea.raz...@yahoo.comwrote:
Hello,
i have a webserver useing freebsd 7.2 and i user the same server to route
internet to a local network.
the internet on the local network is working fine but the sites from the
webserver are loading verry
odhia...@gmail.com wrote:
From: Odhiambo Washington odhia...@gmail.com
Subject: Re: webserver and natd
To: Razvan Cristea cristea.raz...@yahoo.com
Cc: freebsd-questions@freebsd.org
Date: Thursday, September 3, 2009, 1:07 PM
On Wed, Sep 2, 2009 at 1:02 AM, Razvan Cristea cristea.raz...@yahoo.com
Hello,
i have a webserver useing freebsd 7.2 and i user the same server to route
internet to a local network.
the internet on the local network is working fine but the sites from the
webserver are loading verry slow.
i fave this configuration in rc.conf:
firewall_enable=YES
Razvan Cristea wrote:
Hello,
i have a webserver useing freebsd 7.2 and i user the same server to route
internet to a local network.
the internet on the local network is working fine but the sites from the
webserver are loading verry slow.
i fave this configuration in rc.conf:
firewall the webserver seems to be overloaded
or something and loads the pages verry slow.
The problem is that natd is not working without firewall activated.
i have apache (directadmin cpanel)
It's been years since I've needed to use NAT, so unfortunately, I can't
help here.
I'm
Hi,
I'm trying to build a server that will act as a gateway between my wireless
network and the rest of the world. Here's an overview of the current setup:
1. FreeBSD 7.1
2. isc-dhcp3-server-3.0.5_2
3. natd configured to connect fxp0 (public network, dynamic IP) to fxp1
(private network, static
Tim Gustafson wrote:
Hi,
I'm trying to build a server that will act as a gateway between my wireless
network and the rest of the world. Here's an overview of the current setup:
1. FreeBSD 7.1
2. isc-dhcp3-server-3.0.5_2
3. natd configured to connect fxp0 (public network, dynamic IP) to fxp1
I'm trying to build a server that will act as a gateway between my wireless
network and the rest of the world. Here's an overview of the current setup:
1. FreeBSD 7.1
2. isc-dhcp3-server-3.0.5_2
3. natd configured to connect fxp0 (public network, dynamic IP) to fxp1
(private network
Hello,
I recently upgraded to 7.0-STABLE and have setup an ipfw+natd combo on
my dual homed host. I have two interfaces:
em0 - external interface to the net 24.205.x.x
sk0 - internal interface 192.168.x.x
When users connect on the 192.168.x.x internal network everything works
great. Packets
and 7.x and I simply
missed it, or that I have something configured completely improperly,
but after hours of tinkering I've yet to fix the problem.
Initially I figured it might be NAT in PPP which was causing the
problem, so I backed it out and used NATD but the same thing happens to me.
uname
I am trying to have both
natd (divert) and loadsharing (pipe/queue)
in the same IPFW2 firewall script.
It works partly. That is, something is wrong because,
pipe-bandwidth does not at all match the measured
and
by using the log-facility I found that
the following package enter the script
mr. phreak [EMAIL PROTECTED] writes:
Hi, I am having trouble with my IPFW+NATD forwarding. I know a lot of
people have
and I've googled my ass off. Still I can't get it right. I'm trying to
forward port 1213 in/out for dc++ usage.
this is my setup:
__WAN router (192.168.1.1
Hi, I am having trouble with my IPFW+NATD forwarding. I know a lot of
people have
and I've googled my ass off. Still I can't get it right. I'm trying to
forward port 1213 in/out for dc++ usage.
this is my setup:
__WAN router (192.168.1.1)
|
|
(FreeBSD gateway/fw NIC1:ath0 (public) NIC2:rl0
Joe wrote:
I have a question about natd/ and ipfw. I am running natd on my external
interface and I have some services on my internal interface.
The services seem to be getting their ip addresses nat'd and some of them
work and some of them dont.
Any idea how to prevent things
to just insert a rule like quot;ipfw add xxx allow ip from
gt; mynet/mask to mynet/maskquot;, where quot;xxxquot; is the rule-number
BEFORE your
gt; natd redirection rule-number and mynet/mask describes your internal
network
Joe wrote:
I have a question about natd/ and ipfw. I am running natd on my external interface and I have some services on my internal interface.
The services seem to be getting their ip addresses nat'd and some of them work and some of them dont.
Any idea how to prevent things from going
I have a question about natd/ and ipfw. I am running natd on my external
interface and I have some services on my internal interface.
The services seem to be getting their ip addresses nat'd and some of them work
and some of them dont.
Any idea how to prevent things from going into natd
Hello everyone :)
I'm trying to get some natd stats such as
number of active connections
List of active connections and originating IP
Destination ports
Destination IPs...
I would grab those informations from 5 to 5 minutes or so...
Even better would be to be able to grab those through snmp
I'm trying to add a second IP address to an existing jail
using natd and I must be missing something.
Setup:
HOST_IP The host, attached to fxp0
JAIL_IP The existing, working jail
2ND_IP The IP address I'm trying to natd to the jail
I've got ipfw rules to catch traffic
Ross Penner [EMAIL PROTECTED] writes:
I've configured my freebsd computer to be the gateway for my home network
using the guidelines in the handbook. All the required kernel options are
enabled and the entries in /etc/rc.conf have been added. I'm unsure what the
problem could be and I'm
Hello Ross,
FreeBSD as a gateway is very easy and simple to setup, but a very small
mistake could
stop your box from acting as a gateway,
1)
Please send the follow :
the output of #ifconfg -a
2) output of #uname -a
3) copy of rc.conf file
4) Whats the lines you have changed in your
I've configured my freebsd computer to be the gateway for my home network
using the guidelines in the handbook. All the required kernel options are
enabled and the entries in /etc/rc.conf have been added. I'm unsure what the
problem could be and I'm hoping somebody can give me some advice on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have strange situation on one my server:
Before restart natd
#df -hi
/dev/ad0s1d5.2G4.3G433M91% 170252 489202 26% /var
But
#du -sh /var
1.3G/var
lsof shows:
natd 310 root 4w VREG 4,17 2946973785 244973 /var
[Fratiman Vladut]
This is because u try to access an ip that have same ip like your
gateway, but from internal lan, so packets are sends to gateway but
cannot be redirected back to the http server according with redirect
rules.
To resolve this situation, configure a simple dns server on your
a number of port redirects in the gateway, for svn, http,
https, ssh, etc using natd. However, these port redirects do not work
from inside the LAN.
For instance, if I point my browser to http://external.com and I'm in
the LAN, then it will not work. I can't use the internal address of
the web
using natd. However, these port redirects do not work
from inside the LAN.
For instance, if I point my browser to http://external.com and I'm in
the LAN, then it will not work. I can't use the internal address of
the web server because none of the links will work on the web page.
In summary, I want
Hello,
I have set myself up a nice FreeBSD router, but im having trouble getting my
firewall and NAT configured. I have a basic setup at the moment that is
working well, using IPFW for a firewall and also running natd because i have
a few computers here on my LAN that want Internet access
On 10/18/06, Chris [EMAIL PROTECTED] wrote:
Hello,
I have set myself up a nice FreeBSD router, but im having trouble getting
my
firewall and NAT configured. I have a basic setup at the moment that is
working well, using IPFW for a firewall and also running natd because i
have
a few computers
keep this in mind if you
add rules)
add allow ip from any to any
/etc/natd.conf contains:
redirect_port tcp ip_to_goto:port local_port
Did you setup ipfw and directed packes to natd?
You also need to setup i
--
Alex
Please copy the original recipients
rl0
/sbin/ipfw add 5000 divert natd ip from 192.168.0.0:255.255.255.128 to any
out xmit rl1
/sbin/ipfw add 5100 divert natd ip from any to 192.168.0.1
/sbin/ipfw add 5500 deny all from 192.168.0.0/24 to not 192.168.0.0/2480,21,443
/sbin/ipfw add 600 allow all from any to any
-
my ifconfig
rl0
/sbin/ipfw add 4100 deny udp from any to any 137-139 via rl0
/sbin/ipfw add 5000 divert natd ip from 192.168.0.0:255.255.255.128 to any
out xmit rl1
/sbin/ipfw add 5100 divert natd ip from any to 192.168.0.1
you should have a look at http://www.freebsddiary.org/ipfw.php -
especially
a
seperate D Link card, that is supported. My question is, all the online
documentation has indicated the usage for the natd daemon is used for Network
Address Translation, however it doesnt indicate weather I can use all 8 ports (
4 from each card) as LAN ports, with the DLink's connection
indicated the usage for
the natd daemon is used for Network Address Translation, however it
doesnt indicate weather I can use all 8 ports ( 4 from each card) as
LAN ports, with the DLink's connection as the WAN port. Is this
possible?
If you can configure all 8 ports with ifconfig,
you
Hi there,
What is the procedure to make active changes made to /etc/natd.conf?
Sometimes, restarting the natd process with an HUP drops my connection.
Other times the restart didn't seem to make any difference. The only
way I've ever updated natd rules was to restart the server and never
On Jul 14, 2006, at 4:00 PM, Darek M wrote:
What is the procedure to make active changes made to /etc/natd.conf?
Sometimes, restarting the natd process with an HUP drops my
connection. Other times the restart didn't seem to make any
difference. The only way I've ever updated natd rules
Summary: NATD translates source addresses even though it should not because
unregistered_only is set and the IPs do not belong to RFC 1918 (like
192.168)
Hi List,
I have a very strange problem in my
FreeBSD bigb3 6.1-STABLE FreeBSD 6.1-STABLE #0: Tue Jun 6
I am using
BigBrother-{BigB3} wrote:
[ ... ]
I have trouble making a passive ftp connection to work, because every
time natd changed source port even though it should not. Sometimes it
changes within the IP_PORTRANGE_DEFAULT but sometimes it changes it to
something completely irrelevant like 3
On Fri, 7 Jul 2006, Chuck Swiger wrote:
BigBrother-{BigB3} wrote:
[ ... ]
I have trouble making a passive ftp connection to work, because every time
natd changed source port even though it should not. Sometimes it changes
within the IP_PORTRANGE_DEFAULT but sometimes it changes
I just cvsup'ed the source and rebuilt world, and now natd starts on
boot-up just fine. I don't have any idea what changed, although I did
notice that when I ran mergemaster there was new text in
/etc/defaults/rc.conf, which I installed without examining too closely. The
thing is, I looked
At 07:21 AM 6/9/2006 -0800, you wrote:
On 6/6/2006 21:13, Roger Merritt seems to have typed:
Everything
starts on boot-up as it should -- except natd. I can start it manually
from
the command line after booting up and logging in and it works fine, but I
can't tell what's going on that it's
'? I have ip6 enabled, too,
although as far as I know I only deal with ip4. Something new to research.
Otherwise, perhaps it's worthwhile chucking a debug echo or two
about the place (for instance, in /etc/rc.d/natd and /
or /etc/rc.d/ipfw) and rebooting. Something like this should do
the trick
On 6/6/2006 21:13, Roger Merritt seems to have typed:
Everything
starts on boot-up as it should -- except natd. I can start it manually from
the command line after booting up and logging in and it works fine, but I
can't tell what's going on that it's failing to start.
Try adding
On 6/6/2006 21:13, Roger Merritt seems to have typed:
Everything
starts on boot-up as it should -- except natd. I can start it manually from
the command line after booting up and logging in and it works fine, but I
can't tell what's going on that it's failing to start.
Try adding:
natd_flags
seems to be
working the
way it should, Apache, MySQL, PHP, syslog, Samba -- except natd.
Everything
starts on boot-up as it should -- except natd. I can start it
manually
from
the command line after booting up and logging in and it works
fine, but I
can't tell
to be working the
way it should, Apache, MySQL, PHP, syslog, Samba -- except natd. Everything
starts on boot-up as it should -- except natd. I can start it manually from
the command line after booting up and logging in and it works fine, but I
can't tell what's going on that it's failing to start
Hello Roger,
what happens if you type
/etc/rc.d/natd start
after boot-up?
Björn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
At 08:46 AM 6/7/2006 +0200, you wrote:
Hello Roger,
what happens if you type
/etc/rc.d/natd start
after boot-up?
The script prints out the string natd, leading space but no newline, and
a process is started for natd.
--
Roger
___
freebsd
install. Everything now seems to be working the
way it should, Apache, MySQL, PHP, syslog, Samba -- except natd.
Everything
starts on boot-up as it should -- except natd. I can start it manually
from
the command line after booting up and logging in and it works fine, but I
can't tell what's
. Through laziness I didn't follow the instructions and
had
to make a completely new install. Everything now seems to be working the
way it should, Apache, MySQL, PHP, syslog, Samba -- except natd.
Everything
starts on boot-up as it should -- except natd. I can start it manually
from
transferred my FreeBSD
system to
a new hard drive. Through laziness I didn't follow the instructions and
had
to make a completely new install. Everything now seems to be working the
way it should, Apache, MySQL, PHP, syslog, Samba -- except natd.
Everything
starts on boot-up as it should
,
Samba -- except natd. Everything starts on boot-up as it should --
except natd. I can start it manually from the command line after
booting up and logging in and it works fine, but I can't tell what's
going on that it's failing to start.
My /etc/rc.conf contains the following:
# This file now
, MySQL, PHP,
syslog, Samba -- except natd. Everything starts on boot-up as it
should -- except natd. I can start it manually from the command
line after booting up and logging in and it works fine, but I can't
tell what's going on that it's failing to start.
My /etc/rc.conf
thoroughly puzzled. Over the weekend I transferred my FreeBSD
system to
a new hard drive. Through laziness I didn't follow the
instructions and
had
to make a completely new install. Everything now seems to be
working the
way it should, Apache, MySQL, PHP, syslog, Samba -- except natd
put this script into /usr/loca/etc/rc.d/
# cat /usr/local/etc/rc.d/natd.sh
#!/bin/sh
/sbin/natd -n rl1
Roger Merritt wrote:
I'm thoroughly puzzled. Over the weekend I transferred my FreeBSD
system to a new hard drive. Through laziness I didn't follow the
instructions and had to make
At 01:34 PM 6/7/2006 +0300, you wrote:
Try to comment the line natd_enable=YES and then add
a new line at the end of rc.conf:
/etc/rc.d/natd start
Well, that looks like it would work. I'll keep it in mind as a last resort.
if this doesn't work, try to put
natd_flags=
I'll give it a try
I'm thoroughly puzzled. Over the weekend I transferred my FreeBSD system to
a new hard drive. Through laziness I didn't follow the instructions and had
to make a completely new install. Everything now seems to be working the
way it should, Apache, MySQL, PHP, syslog, Samba -- except natd
computer should speak
IPSec with one other computer, from which it mounts home directories via NFS.
When I enable natd, ipfw, and IPSec, the connection to the computer with which I
speak IPSec breaks, but the NAT functions properly (can ping everything except
the IPSec-speaking NFS server).
My ipfw
董佑龍 [EMAIL PROTECTED] writes:
Hello:
My English is not good. I am sorry about this first. ~_~
You made yourself clear. Better than good enough.
My system: FreeBSD + IPFW + NAT
Question 1: about NAT (in FreeBSD)
I built a natd.conf and it's contents are
Hello:
My English is not good. I am sorry about this first. ~_~
My system: FreeBSD + IPFW + NAT
Question 1: about NAT (in FreeBSD)
I built a natd.conf and it's contents are below:
redirect_address 192.168.0.1 140.115.10.22
I
machine) and then there's everything else.
The biggest problem I've runinto is that because natd gets the packets first
thing the only way to catch outgoing traffic is on the internal network
interface. That is if you want to limit based on which internal machine is
generating the traffic like
problem I've runinto is that because natd gets the packets first
thing the only way to catch outgoing traffic is on the internal network
interface. That is if you want to limit based on which internal machine is
generating the traffic like in my case. After the divert rule for natd the
src-ip field
My system has recently locked up after 65 days uptime, running only natd for
my local network. Natd still works fine and routes information properly - but
I am no longer able to telnet or login to my machine even from a local
console(alt f1-fx). After I enter my root or user name at the login
On Wed, 19 Apr 2006, Ben and Jen wrote:
My system has recently locked up after 65 days uptime, running only
natd for my local network. Natd still works fine and routes information
properly - but I am no longer able to telnet or login to my machine even
from a local console(alt f1-fx). After
On 3/12/06, Nagilum [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
How about interface bonding/aggregation ? Check ng_fec(4) for details.
Hope this helps,
Nagilum.
I checked the man page but really didn`t understand - it will forward the
traffic
Iantcho Vassilev wrote:
On 3/12/06, Nagilum [EMAIL PROTECTED] wrote:
[ ... ]
I checked the man page but really didn`t understand - it will forward the
traffic simultaneously threw two interfaces ? Based on IP?
No, you would use IPFW to forward different IP ranges through one interface or
the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
How about interface bonding/aggregation ? Check ng_fec(4) for details.
Hope this helps,
Nagilum.
Ramiz Sardar wrote:
Dears, I am using freebsd machine in office as a gateway and using
ipfw+natd for internet sharing. I have two dsl connections
Dears,
I am using freebsd machine in office as a gateway and using
ipfw+natd for internet sharing. I have two dsl connections but i using just one
at a time. when ever first dsl connection create any problem then i have to
switch to second connection manually.
Tell me any
natd about the following options for 1-to-1 NAT translation, which
can
be put into /etc/natd.conf and processed automagicly when the machine boots:
-redirect_address localIP publicIP
That's one trick. Do you use it in production? How many
hosts do you have mapped this way? How do you get
, what can you do to alias
some of them to one ip, others to another and so on.
See man natd about the following options for 1-to-1 NAT translation,
which can
be put into /etc/natd.conf and processed automagicly when the machine
boots:
-redirect_address localIP publicIP
That's one
I wonder, what tricks do you use to use more than
one alias IP? I mean, if you have hundreds of
hosts behind your firewall, what can you do to alias
some of them to one ip, others to another and so on.
I know pf can probably do it in a better fashion, I just
wonder how we can do it with natd
, 2006 3:45 PM
To: FreeBSD Questions
Subject: natd with several alias IPs
I wonder, what tricks do you use to use more than
one alias IP? I mean, if you have hundreds of
hosts behind your firewall, what can you do to alias
some of them to one ip, others to another and so on.
I know pf can probably do
frameworks. The question is, how to do
that with natd (and ipfw). Could you be so kind and
throw an example of a round-robin setup without
several natd processes, 'cuz I can hardly imagine
that?
___
freebsd-questions@freebsd.org mailing list
http
Subject: Re: natd with several alias IPs
On 2/16/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I am not sure just what you are asking about.
Are you saying that you have 4 static public ip address assigned
to
you by your ISP and you want to round robin those 4 in the NATing
process to your
1 - 100 of 550 matches
Mail list logo
