On 8/27/2010 9:09 PM, Doug Hardie wrote:
On 27 August 2010, at 05:07, Patrick Lamaiziere wrote:
Le Thu, 26 Aug 2010 18:17:19 -0700, Doug Hardie a
écrit :
PF's route_to will return the packets to the proper router, but I
have not been able to figure out which ones those would be. The
source
On 27 August 2010, at 05:07, Patrick Lamaiziere wrote:
> Le Thu, 26 Aug 2010 18:17:19 -0700,
> Doug Hardie a écrit :
>
>> PF's route_to will return the packets to the proper router, but I have not
>> been able to figure out which ones those would be. The source IP
>> address can be any on eith
Le Thu, 26 Aug 2010 18:17:19 -0700,
Doug Hardie a écrit :
> PF's route_to will return the packets to the proper router, but I have not
> been able to figure out which ones those would be. The source IP
> address can be any on either network and its highly likely that we
> will see packets from
Laszlo Nagy írta:
- ping from pc on 0.0 network to 192.168.2.138
Well, I cannot do this from here. Those computers are X terminals,
they do not run inetd nor sshd. I cannot login from here and I cannot
leave now, but I can do it later if necessary.
- sysctl -a net.inet.ip.forwarding (on
- ping from pc on 0.0 network to 192.168.2.138
Well, I cannot do this from here. Those computers are X terminals,
they do not run inetd nor sshd. I cannot login from here and I cannot
leave now, but I can do it later if necessary.
- sysctl -a net.inet.ip.forwarding (on the GatewayComp)
Steve Bertrand wrote:
Internet -> [Hw Router] (LAN1: 192.168.2.0/24) -> [
192.168.2.138 GatewayComp 192.168.0.1 ] -- (LAN2: 192.168.0.0/24)
I would like to access a computer from LAN1 to LAN2.
Perform the following and post the results of:
- ping from GatewayComp to
> Internet -> [Hw Router] (LAN1: 192.168.2.0/24) -> [
> 192.168.2.138 GatewayComp 192.168.0.1 ] -- (LAN2: 192.168.0.0/24)
>
> I would like to access a computer from LAN1 to LAN2.
Perform the following and post the results of:
- ping from GatewayComp to pc on 0.0 network and
In response to "Bret J Esquivel" <[EMAIL PROTECTED]>:
>
> I have a cable modem at my office with a /28 allocated. I have a FreeBSD 6.1
> firewall/router in between the cable modem and the switch to other nodes. My
> question is how could I add static routes to say my web server having an
> externa
Bret J Esquivel wrote:
Hi,
I have a cable modem at my office with a /28 allocated. I have a FreeBSD 6.1
firewall/router in between the cable modem and the switch to other nodes. My
question is how could I add static routes to say my web server having an
external IP address but still going th
On Tuesday 12 December 2006 09:49, Bret J. Esquivel wrote:
> Hi,
>
>
>
> I have a cable modem at my office with a /28 allocated. I have a FreeBSD 6.1
> firewall/router in between the cable modem and the switch to other nodes. My
> question is how could I add static routes to say my web server h
In the last episode (Apr 14), Kurt Buff said:
> Dan Nelson wrote:
> >In the last episode (Apr 13), Kurt Buff said:
> >>I have a FreeBSD 5.3 box running
> >>postfix/amavisd-new/spamassassin/clamav. Currently, we have two
> >>entrances to our network, one is the Watchguard FBIII for our T1,
> >>the o
In the last episode (Apr 14), Kurt Buff said:
> Dan Nelson wrote:
> >In the last episode (Apr 13), Kurt Buff said:
> >>I have a FreeBSD 5.3 box running
> >>postfix/amavisd-new/spamassassin/clamav. Currently, we have two
> >>entrances to our network, one is the Watchguard FBIII for our T1,
> >>the o
Dan Nelson wrote:
In the last episode (Apr 13), Kurt Buff said:
I have a FreeBSD 5.3 box running
postfix/amavisd-new/spamassassin/clamav. Currently, we have two
entrances to our network, one is the Watchguard FBIII for our T1, the
other is a PC running Win2k and Winproxy, serving our DSL line. The
Dan Nelson wrote:
In the last episode (Apr 13), Kurt Buff said:
I have a FreeBSD 5.3 box running
postfix/amavisd-new/spamassassin/clamav. Currently, we have two
entrances to our network, one is the Watchguard FBIII for our T1, the
other is a PC running Win2k and Winproxy, serving our DSL line. The
In the last episode (Apr 13), Kurt Buff said:
> I have a FreeBSD 5.3 box running
> postfix/amavisd-new/spamassassin/clamav. Currently, we have two
> entrances to our network, one is the Watchguard FBIII for our T1, the
> other is a PC running Win2k and Winproxy, serving our DSL line. The
> PC is st
]
Sent: 11 June 2004 18:12
To: [EMAIL PROTECTED]
Subject: RE: Routing question
Leon,
This is possible, but will require you to run static routes so that you can
manually manage the connections. You should be able to set the routing
metrics so that all your traffic from client D goes to B and if they
]
Sent: 11 June 2004 18:16
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Routing question
Perhaps if you post more info, we can come up with creative solutions for
you. My big question is why?
AFAIK, you cannot have more than one default gateway, unless you are using
netgraph to balance
Perhaps if you post more info, we can come up with creative solutions
for you. My big question is why?
AFAIK, you cannot have more than one default gateway, unless you are
using netgraph to balance between network interfaces. However, you could
NAT C & D to their respective "public" interfaces.
thank you
On Sat, 5 Jun 2004, Eric Crist wrote:
> You need to kill all the running dhclient processes, then try again.
> Usually, this can be done with:
>
> #killall -9 dhclient
>
> HTH
>
> Eric F Crist
> President
> AdTech Integrated Systems, Inc
> (612) 998-3588
>
>
>
> > -Original Message-
You need to kill all the running dhclient processes, then try again.
Usually, this can be done with:
#killall -9 dhclient
HTH
Eric F Crist
President
AdTech Integrated Systems, Inc
(612) 998-3588
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
>
On Mon, Feb 09, 2004 at 03:40:04PM -0500, Marius Kirschner wrote:
> I have a 4.9 box that's on a public IP and I want to configure Samba so it
> only accepts connections from the private network (192.168.1). My question
> is, can I do that with only 1 NIC card or do I have to add a second NIC for
Look in the Samba config for the following setting, it is IP based so
you should be OK with what you want.
# This option is important for security. It allows you to restrict
hosts allow = 192.168.1. 127.
HTH,
Jay
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Be
You can do that within the smb.conf
Use SWAT, advanced options, I think just for the share...
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Marius Kirschner
> Sent: Monday, 9 February 2004 12:40
> To: [EMAIL PROTECTED]
> Subject: Routing ques
: Nathan Nieblas [mailto:[EMAIL PROTECTED]
Sent: 10 June 2003 09:08
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Routing question
You can probably get what you want by compiling IPDIVERT and IPFIREWALL into
your kernel.
Then running some rules, this may or may not be accurate:
ipfw add
24 matches
Mail list logo