On 2005.01.26 02:33:54 +, Bruce M Simpson wrote:
> On Tue, Jan 25, 2005 at 06:38:42PM +0100, Jeremie Le Hen wrote:
> > Are you thinking about the enc(4) interface [1] [2] provided with OpenBSD ?
>
> Somewhat, although whilst enc(4) provides some of this functionality, its
> role as far as I ca
Please do the following:
ping -r -S 192.168.1.1 192.168.4.13 >/dev/null 2>&1 &
netstat -I gif0 -w 1
and see if any packets are counted. If you are using IPSec, maybe your packets
are encrypted before they go to gif. See this article:
http://groups-beta.google.com/group/sol.lists.freebsd.net/brows
Hi Jeremie.
Please tell me more about your problem: is it that tcpdump cannot attach to
device, or it shows no packets when you are sure there is traffic on the gif(4)
interface, or something else? If there is some error report - send it here.
Please check that you have free bpf device :-) . Wh
See documentation for squid. It has such option. I cannot look into config file
right now, but I remember that I have used it successfully.
-Original Message-
From: Mike Wesson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 18, 2005 12:44 AM
To: freebsd-net@freebsd.org
Subject: Using al
I am using trafd and I am quite happy with it, if I dump internal tables to
disk often enough.
Nick
-Original Message-
From: Andrew Seguin [mailto:[EMAIL PROTECTED]
Sent: Monday, January 17, 2005 11:11 PM
To: freebsd-net@freebsd.org
Subject: Network accounting
I’ve searched Google, I’v
On 1/20/2005 2:33 AM, Robert Watson wrote:
On Wed, 19 Jan 2005, Charlie Schluting wrote:
Now, in 5.3, the only thing I can get working is to configure the em0
int with the IP, and set the trunk to have the native vlan corresponding
to that IP. Weird.
Also, is there a way to stop em(4) from stripp
Hi all,
Here is what i have done so far.
i worked only on the nat.ex.com
internet
|
|
rl0(193.23143.33)
||
| nat.example.com
Hi there,
Basically because NAT is altering all packets leaving on rl0 on your 'nat'
machine, to the outside world the packets leaving your network, from 'app'
machine will appear to be from your 'nat' machines external interface.
The way to get around this is to tell natd not to perform NAT on
1. Dont add any alias to rl1, just keep 192.168.0.254/24
2. Delete all ip/masks of app.example.com.
3. Add 193.231.43.26/32 as ip/mask to app.example.com
4. Do a "route add 192.168.0.254/32 -interface ($nic) -cloning
on app.example.com
5. and "route add default 192.168.0.254" on app.example.com
Referencing:
http://lists.freebsd.org/pipermail/freebsd-net/2004-November/005738.html
I appear to have hit a similar or the same problem (with the exception
that I'm not bridging with the vlan), has anyone (Robert Watson
appears to be the lead) come up with anything?
My config is 5.3-STABLE with
> Referencing:
> http://lists.freebsd.org/pipermail/freebsd-net/2004-November/005738.html
>
> I appear to have hit a similar or the same problem (with the exception
> that I'm not bridging with the vlan), has anyone (Robert Watson
> appears to be the lead) come up with anything?
I think it has ju
11 matches
Mail list logo
