On Jun 7, 2012, at 10:29 AM, Michael Sierchio wrote:
> On Thu, Jun 7, 2012 at 10:27 AM, Michael Sierchio wrote:
>> net.inet.tcp.finwait2_timeout: 6 <- ms, ten minutes
>
> I can't do arithmetic, but you get the idea. A full minute.
Yes; that's already shorter than possible MAXTTL value of pa
On Thu, Jun 7, 2012 at 10:27 AM, Michael Sierchio wrote:
> net.inet.tcp.finwait2_timeout: 6 <- ms, ten minutes
I can't do arithmetic, but you get the idea. A full minute.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mail
On Thu, Jun 7, 2012 at 10:15 AM, Michael Powell wrote:
> There is also this you can place in /etc/sysctl.conf:
>
> net.inet.tcp.fast_finwait2_recycle=1
>
Good catch. The defaults are perhaps not ideal in all cases:
net.inet.tcp.finwait2_timeout: 6 <- ms, ten minutes
net.inet.tcp.fast_finw
Michael Sierchio wrote:
> On Wed, Jun 6, 2012 at 11:31 AM, Simon wrote:
>
>> This easily causes DoS for when too many FIN_WAIT_2 are created and IPFW
>> stops forwarding using the rule above because of "too many dynamic rules"
>
> Change the defaults for the fw.dyn sysctl MIB nodes
>
> to some
In freebsd-questions Digest, Vol 418, Issue 10, Message: 7
On Wed, 06 Jun 2012 14:31:24 -0400 "Simon" wrote:
> Can someone suggest an alternative/proper way to port forward using ipfw.
> Right
> now I have the following and some bad clients cause too many FIN_WAIT_2 state
>
> fwd IP,PORT2
In the last episode (Jun 06), Michael Sierchio said:
> On Wed, Jun 6, 2012 at 11:31 AM, Simon wrote:
>
> > This easily causes DoS for when too many FIN_WAIT_2 are created and IPFW
> > stops forwarding using the rule above because of "too many dynamic
> > rules"
>
> Change the defaults for the fw
On Wed, Jun 6, 2012 at 11:31 AM, Simon wrote:
> This easily causes DoS for when too many FIN_WAIT_2 are created and IPFW
> stops forwarding using the rule above because of "too many dynamic rules"
Change the defaults for the fw.dyn sysctl MIB nodes
to something like
net.inet.ip.fw.dyn_short_li
Hi,
Can someone suggest an alternative/proper way to port forward using ipfw. Right
now I have the following and some bad clients cause too many FIN_WAIT_2 state
fwd IP,PORT2 tcp from any to me dst-port PORT1 keep-state
This easily causes DoS for when too many FIN_WAIT_2 are created and IPFW
sto
gt;>
>>> hi,
>>> i have a ssh machine behind a freebsd firewall with nat and ipfw.
>>> how do i make port forwarding so internet can access the ssh machine?
>>> thanx
>>>
>>
>> i think you need to configure /etc/ipnat.conf ( read 'man
ment.
i am very confused by the roles of natd and ipfw, and how they should work
together.
rich
On Sat, Dec 27, 2008 at 8:40 AM, wrote:
> Hi Ricard,
>
> On Fri, Dec 26, 2008 at 9:27 PM, Richard Yang wrote:
>
>> hi,
>> i have a ssh machine behind a freebsd firewall with n
Hi Ricard,
On Fri, Dec 26, 2008 at 9:27 PM, Richard Yang wrote:
> hi,
> i have a ssh machine behind a freebsd firewall with nat and ipfw.
> how do i make port forwarding so internet can access the ssh machine?
> thanx
>
i think you need to configure /etc/ipnat.conf ( read 'm
"Richard Yang" writes:
> i have a ssh machine behind a freebsd firewall with nat and ipfw.
> how do i make port forwarding so internet can access the ssh machine?
Use 'redirect_port' with natd(8).
This is extensively documented in the Handbook:
http://www.freebsd
hi,
i have a ssh machine behind a freebsd firewall with nat and ipfw.
how do i make port forwarding so internet can access the ssh machine?
thanx
--
Best Regards
Richard Yang
richardy...@richardyang.net
kusanagiy...@gmail.com
___
freebsd-questions
On Wed, 19 Nov 2008, Jakub T wrote:
2008/11/15 Luke Dean <[EMAIL PROTECTED]>
Port-forwarding through two NATs is something I've never had any success
with. I have a few suggestions that have worked for me and my friends with
this setup.
A) Disable NAT on the ADSL router.
2008/11/15 Luke Dean <[EMAIL PROTECTED]>
>
> Port-forwarding through two NATs is something I've never had any success
> with. I have a few suggestions that have worked for me and my friends with
> this setup.
>
> A) Disable NAT on the ADSL router. I think the term
B) Disable NAT on the wireless router. This allows it to be a simple switch
and wireless access point. The price is that you're probably relying on the
DHCP server in the wireless router for your wireless devices and you'll have
to disable the DHCP when you disable NAT. This creates new probl
e Internet connection on both computers. However, I can't get aMule
and other apps that need port forwarding working on FreeBSD box.
First, I tried to configure ADSL router (192.168.1.1) just to forward 4662
port to 192.168.0.102, doesn't work.
Then, I tried this:
192.168.1.1 router: forward
h computers. However, I can't get aMule
and other apps that need port forwarding working on FreeBSD box.
First, I tried to configure ADSL router (192.168.1.1) just to forward 4662
port to 192.168.0.102, doesn't work.
Then, I tried this:
192.168.1.1 router: forward 4662 to 192.168.
On Mon, Oct 27, 2008 at 12:04:46PM -0500, Kevin Kinsey wrote:
> Hello,
>
> I'm (still) trying to work around a limitation I've encountered
> with a new service provider (cf. "MTA on non-standard port").
>
> As root:
> # ssh -L 24:server:52525 server
>
>fails because root logins aren't permi
On Monday 27 October 2008 17:04:46 Kevin Kinsey wrote:
> Hello,
>
> I'm (still) trying to work around a limitation I've encountered
> with a new service provider (cf. "MTA on non-standard port").
>
> As root:
> # ssh -L 24:server:52525 server
>
>fails because root logins aren't permitted in
>
Hello,
I'm (still) trying to work around a limitation I've encountered
with a new service provider (cf. "MTA on non-standard port").
As root:
# ssh -L 24:server:52525 server
fails because root logins aren't permitted in
/etc/sshd_config on the server.
Also as root:
# ssh -L 24:server:52525
On Fri, Dec 28, 2007 at 12:19:44PM -0800, Brian wrote:
> Chad Perrin wrote:
> >On Tue, Dec 18, 2007 at 05:44:11AM -0500, Gerard Seibert wrote:
> >
> >>>On December 18, 2007 at 12:47AM sham khalil wrote:
> >>>
> >>>once you open port 22 to public ip, you'll get people try to bruteforce
> >>>your
Chad Perrin wrote:
On Tue, Dec 18, 2007 at 05:44:11AM -0500, Gerard Seibert wrote:
On December 18, 2007 at 12:47AM sham khalil wrote:
once you open port 22 to public ip, you'll get people try to bruteforce your
machine.
if you don't want that set sshd to listen to a higher number like 5522
t
On Tue, Dec 18, 2007 at 06:02:18AM +, Pollywog wrote:
>
> Make sure the ISP is not blocking port 22. If they block it, you will need
> to
> change the SSH port in sshd_config and then set the router to forward the
> port to the server's internal IP address. It's a good idea to change the
On Tue, Dec 18, 2007 at 05:44:11AM -0500, Gerard Seibert wrote:
> > On December 18, 2007 at 12:47AM sham khalil wrote:
> >
> > once you open port 22 to public ip, you'll get people try to bruteforce your
> > machine.
> > if you don't want that set sshd to listen to a higher number like 5522
> > th
>
>
> Security through obscurity is a poor substitute for security. Port
> scanners
> will eventually find that port also.
>
> Have you checked to see if a firewall is set up that could be blocking the
> port?
>
Not a thorough check, but my father did turn off the firewall system on that
linksys r
> On December 18, 2007 at 12:47AM sham khalil wrote:
> On Dec 18, 2007 12:08 PM, Bill Campbell <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Dec 17, 2007, Andrew Falanga wrote:
> > >Hi,
> > >
> > >I'm having a difficult time working with my
On Dec 18, 2007 12:08 PM, Bill Campbell <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 17, 2007, Andrew Falanga wrote:
> >Hi,
> >
> >I'm having a difficult time working with my father to get the port
> >forwarding working on his Linksys router to forward SSH requ
Make sure the ISP is not blocking port 22. If they block it, you will need to
change the SSH port in sshd_config and then set the router to forward the
port to the server's internal IP address. It's a good idea to change the
port anyway, in order not to be obvious to script kiddies.
___
On Mon, Dec 17, 2007, Andrew Falanga wrote:
>Hi,
>
>I'm having a difficult time working with my father to get the port
>forwarding working on his Linksys router to forward SSH requests to his
>FreeBSD machine at home. As near as we can figure, it's setup correctly.
>I
Hi,
I'm having a difficult time working with my father to get the port
forwarding working on his Linksys router to forward SSH requests to his
FreeBSD machine at home. As near as we can figure, it's setup correctly.
In case anyone here uses this router it is WRT54G and details (includi
gt; xx.xx.xx.xx netmask 0xff00
Opened by PID 492
Natd configuration (Works fine w/ the exception of port forwarding)
--
natd_enable="YES"
natd_flags="-dynamic -m -redirect_port tcp 1
Has anybody noted any issues with port forwarding using SSH tunnels on
FreeBSD 6.1 AMD64? I just recently upgraded my machine from i386 to
amd64, using nearly all the same configuration files. Now, remotely, I
make an SSH session to my machine and attempt to forward ports, as usual,
and I find
gt; > inet 87.50.69.60 netmask 0xff80 broadcast 87.50.69.127
> > ether 00:b0:02:00:27:f3
> > media: Ethernet autoselect (100baseTX )
> > status: active
> >
> > I have been googling and reading ifconfig papers all day yesterday, in
> >
er 00:b0:02:00:27:f3
> media: Ethernet autoselect (100baseTX )
> status: active
>
> I have been googling and reading ifconfig papers all day yesterday, in
> the search for how to do simple port-forwarding, but nothing have
> worked.
> So, this is my final resort: How
to do simple port-forwarding, but nothing have
worked.
So, this is my final resort: How would I forward the ports 9541 (TCP)
and 9542 (UDP) to 192.168.0.2 on my LAN?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
John Do <[EMAIL PROTECTED]> writes:
> If you have a FreeBSD computer with multiple IP
> addresses and you want an outside client to tunnel how
> can you force the tunnel to use a certain IP?
Isn't the -b option for exactly that?
___
freebsd-questions@fr
If you have a FreeBSD computer with multiple IP
addresses and you want an outside client to tunnel how
can you force the tunnel to use a certain IP?
Thanks!
__
Find your next car at http://autos.yahoo.ca
Deling Ren <[EMAIL PROTECTED]>:
> Hi all, I am trying to setup a NAT box for my home network on freebsd 5.3.
> I am using ipfw and natd. I already got nat running but I am having
> problem with port forwarding. I am trying to forward port 80 on the nat
> box to an internal machin
Deling Ren <[EMAIL PROTECTED]> writes:
> Hi all, I am trying to setup a NAT box for my home network on freebsd 5.3.
> I am using ipfw and natd. I already got nat running but I am having
> problem with port forwarding. I am trying to forward port 80 on the nat
> box to a
Hi all, I am trying to setup a NAT box for my home network on freebsd 5.3.
I am using ipfw and natd. I already got nat running but I am having
problem with port forwarding. I am trying to forward port 80 on the nat
box to an internal machine (192.168.0.7). I have the following as part of
Hi All,
I have an ADSL router with some very basic Firewall
connecting my
internal network to the internet. I now want to give
myself greater
flexibility and protection and so I have been
attempting to set a 3
homed host running a firewall with nat.
This host needs to route packets between 2 fu
.oO( Internet )Oo.
||
||
[DSL--]
[ adsl router ] <- No Nat
[-]
es not seem to work with FreeBSD 5.2.1. It does work out of the box for
other versions (4.7 and 4.8 at least) of FreeBSD though. Is there some rule
somewhere preventing port forwarding in 5.2? Here's my netstat output:
bsd3c# netstat -nat
Active Internet connections (including servers)
Proto
On Sun, Jul 04, 2004 at 06:57:16PM +1000, Jon Kurjakovich wrote:
> My problem: I am trying to use NATD to forward packets to machines on
> the internal network using the redirect_port command.
I don't have a solution to your problem with natd, however net/rinetd
(from ports) might be a good enoug
Yes. It is a Windows 2000 Server machine that I can connect to both on
the local network and via an SSH tunnel. It is simply to do with natd's
port forwarding. I also cannot use port forwarding to access any other
services on the 2000 Server box such as telnet or ftp for example.
Any he
ovich" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 04, 2004 3:57 AM
Subject: NATD Port Forwarding question
> Hi there,
>
> I am currently using FreeBSD 4.8-RELEASE. I do plan on upgrading to
> 5.2-CURRENT shortly but I know people who are using 5.2-
/etc/natd.conf with the following options in my
natd.conf file.
interface tun0
same_ports yes
use_sockets yes
unregistered_only
redirect_port tcp 192.168.1.2:3389 3389
When I create an SSH tunnel using putty, that works fine. It is only
when I try and use natd w/ port-forwarding that it doesn&#
Am Dienstag, 23. März 2004 22:26 schrieb JP:
> Hello,
>
> I am currently using PPPoE on FreeBSD 5.2, I have a
> need to forward internet traffic on certain ports to a
> private IP address behind the box. How can this be
> accompished?
>
> For instance, inbound traffic arriving on public IP
> 205.2
Hello,
I am currently using PPPoE on FreeBSD 5.2, I have a
need to forward internet traffic on certain ports to a
private IP address behind the box. How can this be
accompished?
For instance, inbound traffic arriving on public IP
205.242.192.20 port 21 needs to arrive to private IP
192.168.1.1 p
hello again list!
my firewall is setup in freebsd 4.5 and had not implemented nat.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Wed, Feb 25, 2004 at 05:19:35PM +0800, Edison Cala wrote:
> hello list!
>
> i want to ask some help on port forwarding in a bridge-firewall
> network.
>
> our network setup is:
>
> 1. the router is outside the firewall, direct to the internet.
> 2. the bridge-fi
Really hard to help you when you do not post what firewall you are
using and the nat rules you are using.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Edison Cala
Sent: Wednesday, February 25, 2004 4:20 AM
To: [EMAIL PROTECTED]
Subject: port forwarding
hello list!
i want to ask some help on port forwarding in a bridge-firewall network.
our network setup is:
1. the router is outside the firewall, direct to the internet.
2. the bridge-firewall computer (2 ethernet cards installed, eth0 - outside (router),
eth1 - protected network) is between
is helps.
James
On Thu, 2004-01-22 at 04:54, Rishi Chopra wrote:
> James,
>
> I've configured my Win2k box to contact DNS directly, and both Direct
> Connect and VNC Server are running smoothly (port forwarding is being
> accomplished (per your suggestion) by natd.c
James,
I've configured my Win2k box to contact DNS directly, and both Direct
Connect and VNC Server are running smoothly (port forwarding is being
accomplished (per your suggestion) by natd.conf).
I've set the firewall type to 'OPEN' (the Win2k client has ZoneAlarm
p
If you want your gateway to forward DNS queries from your private
network, you will probably have to run named to answer the DNS queries
and forward them out to your ISP's name servers.
You may also want to run a DHCP server.
I don't believe ipfw has the forwarding capability your looking for in
On Mon, 2004-01-19 at 21:04, Rishi Chopra wrote:
> No, those are the values in the file. I had posted a previous question
> to the list asking what the right values should be (my rl0 interface is
> configured via DHCP) - any ideas what I should put in this section?
>
> James Earl wrote:
>
> >
No, those are the values in the file. I had posted a previous question
to the list asking what the right values should be (my rl0 interface is
configured via DHCP) - any ideas what I should put in this section?
James Earl wrote:
On Mon, 2004-01-19 at 13:58, Rishi Chopra wrote:
Here's the rc.f
On Mon, 2004-01-19 at 13:58, Rishi Chopra wrote:
> Here's the rc.firewall file, with comments trimmed for formatting:
>
> [Ss][Ii][Mm][Pp][Ll][Ee])
>
>
> # set these to your outside interface network and netmask and ip
> oif="rl0"
> omask="255.255.
On Mon, 2004-01-19 at 13:58, Rishi Chopra wrote:
> What I want to do: (1) Change firewall type from 'OPEN' to 'SIMPLE' and
> (2) Forward ports 412 and 5800 to my Win2k box.
>
> What I have: The setup is pictured below.
> IPFIREWALL_DEFAULT_TO_ACCEPT, IPDIVERT and IPFILTER are all enabled in
>
What I want to do: (1) Change firewall type from 'OPEN' to 'SIMPLE' and
(2) Forward ports 412 and 5800 to my Win2k box.
What I have: The setup is pictured below.
IPFIREWALL_DEFAULT_TO_ACCEPT, IPDIVERT and IPFILTER are all enabled in
my kernel config file, are also enabled. Rule-of-thumb adv
Anyone run NWN though a FreeBSD firewall/natd setup?
Been trying to get this running for over a week and starting to get very
frustrated with it. :(
Here is how my network is setup:
{internet} <-> [public ips 6-9] DC1 (Firewall) DC0 -[private ips 25-26] -
NWN server
Here are the techinal
:29.737530 192.168.17.25.5120 > hydra.5121: udp 11
21:06:29.741486 192.168.17.25.5120 > hydra.5121: udp 6
21:06:29.746442 63.231.238.229.ssh > 192.168.17.25.2403: P 5552:5580(28) ack
1 win 58400 (DF) [tos 0x10]
21:06:29.746720 192.168.17.25.2403 > 63.231.238.229.ssh: . ack 5580 win
65243
-Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Budec
> Sent: Monday, January 12, 2004 7:50 PM
> To: 'FreeBSD-questions list'
> Subject: Port forwarding
>
>
>
>
>
> Hello,
>
> I have been trying to g
Hello,
I have been trying to get this working for days and am obviously doing
something wrong and was wondering if any Guru's out there could give a
little guidance. Basically I'm looking to run a game server behind a
FreeBSD firewall. Here is my setup:
{internet} <-> [public address] - Fire
Hi,
> Hi all...I'm at a dead end here. I'm trying to setup my firewall/nat
> box to forward requests on externalIP:portA to
> internalPC:portB. I put
> 'natd_flags="-redirect_port tcp 1internalPC:portB portA" ' in
> my rc.conf
> file, and I have the following three statements in my rc.firewall
Hi all...I'm at a dead end here. I'm trying to setup my firewall/nat
box to forward requests on externalIP:portA to internalPC:portB. I put
'natd_flags="-redirect_port tcp 1internalPC:portB portA" ' in my rc.conf
file, and I have the following three statements in my rc.firewall
script:
ipfw add d
Hey All---
I need some help, I'm trying to forward ports
5800-6000 on a PPPoE broadband connection to allow a
program called VNC to work. I have tried everything
but it seems to fail. I know VNC is working fine as I
can do a telnet localhost 5800 and it works from the
local box. But from outsid
Darryl Hoar wrote:
Greetings,
I have a firewall running 4.7-stable. It has ipftable, and nat. It is
my firewall for my home lan. I am wanting to play a game with
friends on the internet. I also want to host a multiplayer game
on my machine. How do I setup the firewall to forward port
5310 to
[EMAIL PROTECTED] wrote:
> Greetings,
> I have a firewall running 4.7-stable. It has ipftable, and nat. It
^ hmmm..
You want to have a look at "rdr" in man (5) ipnat
> is my firewall for my home lan. I am wanting to play a game with
On Wed, Mar 19, 2003 at 09:53:05AM -0600, Darryl Hoar wrote:
> Greetings,
> I have a firewall running 4.7-stable. It has ipftable, and nat. It is
> my firewall for my home lan. I am wanting to play a game with
> friends on the internet. I also want to host a multiplayer game
> on my machine.
Greetings,
I have a firewall running 4.7-stable. It has ipftable, and nat. It is
my firewall for my home lan. I am wanting to play a game with
friends on the internet. I also want to host a multiplayer game
on my machine. How do I setup the firewall to forward port
5310 to my windows 2000 pc
Matthew Ryan wrote:
On Saturday, March 15, 2003, at 03:06 am, Bill Moran wrote:
Matthew Ryan wrote:
On Saturday, March 15, 2003, at 12:13 am, Lowell Gilbert wrote:
Fact is, natd _only_ redirects from the interface is was told to
bind to.
I'm not exactly sure why the packets don't route out an
On Saturday, March 15, 2003, at 03:06 am, Bill Moran wrote:
Matthew Ryan wrote:
On Saturday, March 15, 2003, at 12:13 am, Lowell Gilbert wrote:
Fact is, natd _only_ redirects from the interface is was told to
bind to.
I'm not exactly sure why the packets don't route out and back in
when you
tr
Matthew Ryan <[EMAIL PROTECTED]> writes:
> On Saturday, March 15, 2003, at 12:13 am, Lowell Gilbert wrote:
>
> >> Fact is, natd _only_ redirects from the interface is was told to
> >> bind to.
> >> I'm not exactly sure why the packets don't route out and back in
> >> when you
> >> try it from in
Matthew Ryan wrote:
On Saturday, March 15, 2003, at 12:13 am, Lowell Gilbert wrote:
Fact is, natd _only_ redirects from the interface is was told to bind
to.
I'm not exactly sure why the packets don't route out and back in when
you
try it from inside, but they don't ;( so you always need to tes
On Saturday, March 15, 2003, at 12:13 am, Lowell Gilbert wrote:
Fact is, natd _only_ redirects from the interface is was told to bind
to.
I'm not exactly sure why the packets don't route out and back in when
you
try it from inside, but they don't ;( so you always need to test it
from
the exter
Bill Moran <[EMAIL PROTECTED]> writes:
> Matthew Ryan wrote:
> > The /etc/rc.conf entry:
> > natd_flags="-redirect_port tcp 192.168.1.241: "
> > was fine since:
> > natd_interface="ep0"
> > specified the interface.
> > All in all I just should have posted the whole of my /etc/rc.conf in
>
Matthew Ryan wrote:
The /etc/rc.conf entry:
natd_flags="-redirect_port tcp 192.168.1.241: "
was fine since:
natd_interface="ep0"
specified the interface.
All in all I just should have posted the whole of my /etc/rc.conf in the
first place.
Sorry about that.
The real irony is that it
Bill and Dan,
Thanks for your help guys it's sort of working now but for the record
here's the story.
All attempts to start port forwarding from the command line were
failing because NATD was already running (enabled at boot time) DOH!
b) natd isn't already running with differe
Daniel Bye wrote:
On Fri, Mar 14, 2003 at 01:07:42PM +, Matthew Ryan wrote:
Thanks Dan
Unfortunately that doesn't seem to work either.
Rats!
I get this when I enter on the command line:
natd -n ep0 -redirect_port tcp 192.168.1.241:
natd: Unable to create divert socket.: Operation
On Fri, Mar 14, 2003 at 01:07:42PM +, Matthew Ryan wrote:
> Thanks Dan
>
> Unfortunately that doesn't seem to work either.
Rats!
> I get this when I enter on the command line:
>
> natd -n ep0 -redirect_port tcp 192.168.1.241:
>
> natd: Unable to create divert socket.: Operation no
Daniel Bye wrote:
On Fri, Mar 14, 2003 at 10:30:28AM +, Matthew Ryan wrote:
natd -redirect_port tcp 192.168.1.241:
but here's what i get:
natd: aliasing address not given
That's because natd can't determine which interface it should use for
aliasing. Try specifying it with the -n
Thanks Dan
Unfortunately that doesn't seem to work either.
I get this when I enter on the command line:
natd -n ep0 -redirect_port tcp 192.168.1.241:
natd: Unable to create divert socket.: Operation not permitted
and no results using the following in /etc/rc.conf:
natd_flags="-n ep0
On Fri, Mar 14, 2003 at 10:30:28AM +, Matthew Ryan wrote:
> Hi there,
>
> I've been trying to route packets received on port via the
> external interface (used by NAT) of my FreeBSD gateway to the same port
> on a local machine.
>
> The manual would seem to make this simple stuff - I h
Hi there,
I've been trying to route packets received on port via the
external interface (used by NAT) of my FreeBSD gateway to the same port
on a local machine.
The manual would seem to make this simple stuff - I have added the
following line to /etc/rc.conf:
natd_flags="-redirect_port t
Thanks for your answer and solutions Matthew :)
This is my 4th day of using freeBSD and I'm still very new to it.
I have used RedHat prior to this and when I could not get it to connect
to my ISP via the cable modem I installed freeBSD. ;)
Actually.. I don't fully understand the rc.firewall scri
On Thu, Jan 16, 2003 at 01:49:08AM -0700, WillyB wrote:
> I finally got natd and ipforwading set up but have a slight problem I
> don't understand.
>
> The IP forwarding works from the internet, through the cable modem and
> through the freeBSD router I set up for my internal network, to a www
Hi
I finally got natd and ipforwading set up but have a slight problem I
don't understand.
The IP forwarding works from the internet, through the cable modem and
through the freeBSD router I set up for my internal network, to a www
server on the private lan.
I can't connect to my server howev
Ralph Freibeuter wrote:
Ho can I exactly define a rule (and where?) that forwards
incoming requests to port 445 (samba?) to an internal machine
with lan ip 192.168.2.50 ?
The routing Macs IP is 192.168.2.1 and the external IP is
given by ISP via pppoe.
As someone else mentioned Darwin (aka MacO
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ralph
> Freibeuter
> Sent: Monday, December 30, 2002 04:27 PM
> To: [EMAIL PROTECTED]
> Subject: mac os x 10.2.3 jaguar and port forwarding?
>
>
> Ho can I exactly d
Thus spake Ralph Freibeuter <[EMAIL PROTECTED]>:
> Ho can I exactly define a rule (and where?) that forwards
> incoming requests to port 445 (samba?) to an internal machine
> with lan ip 192.168.2.50 ?
>
> The routing Macs IP is 192.168.2.1 and the external IP is
> given by ISP via pppoe.
>
> Ple
Ho can I exactly define a rule (and where?) that forwards
incoming requests to port 445 (samba?) to an internal machine
with lan ip 192.168.2.50 ?
The routing Macs IP is 192.168.2.1 and the external IP is
given by ISP via pppoe.
Please help me.
I've already tried:
sudo natd -redirect_port tcp 1
> > What is the easiest way of forwarding a port in FreeBSD. Suppose I want
> > my server to listen on port 8280, but want all connection attempts to
port
> > 80 to be forwarded to this port ... can that be done?
Put this in /etc/ipnat.rules
rdr dc0 0/0 port 80 -> 127.0.0.1 port 8280 tcp
And th
Hiho.
On Thu, 21 Nov 2002 18:48:03 -0800 (PST)
Shvetima Gulati <[EMAIL PROTECTED]> wrote:
> What is the easiest way of forwarding a port in FreeBSD. Suppose I
> want my server to listen on port 8280, but want all connection
> attempts to port 80 to be forwarded to this port ... can that be
> done
On Thu, 21 Nov 2002, Shvetima Gulati wrote:
>
> Hi all,
>
> What is the easiest way of forwarding a port in FreeBSD. Suppose I want
> my server to listen on port 8280, but want all connection attempts to port
> 80 to be forwarded to this port ... can that be done?
>
> Thanks,
> Shv
Yes, with IPF
Hi all,
What is the easiest way of forwarding a port in FreeBSD. Suppose I want
my server to listen on port 8280, but want all connection attempts to port
80 to be forwarded to this port ... can that be done?
Thanks,
Shv
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
Hello,
I got port forwarding to work with one IP, but lets say I have several IP's:
natd -n fxp0 -redirect_port 192.168.1.1:25 50 - this works as it connects me
to my smtp server if I go to port 50.
But as soon as I have several IP's:
1
Hi all,
I have been through all the documentation I can find, and I still haven't
found a definitive answer to my question about port forwarding with a ppp
connection. I have a DSL that uses PPPOE, so the system is connected using
PPP. I need to forward ports from the server to int
1 - 100 of 102 matches
Mail list logo
