When monitoring a network, your monitoring interface should have no IP
set or an IP address that matches you network with a netmask of
255.255.255.255 if your monitoring software will not work with out an IP.
Example:
LAN is 192.168.1.0/24(255.255.255.0)
fxp0 is 192.168.1.2/24(255.255.255.0)
rl0
(Promoted to -net due to lack of responces on -questions)
I'm trying to deploy a transparent proxy server for a friend's office but have
run into a couple of snags that I can't seam to find the correct answer for.
Please see http://home2.dbitech.bc.ca:8080/netconfig.txt for graphical
topology
draw a diagrasm
this can be tricky.
On Tue, 25 Feb 2003, Darcy Buskermolen wrote:
>
> (Promoted to -net due to lack of responces on -questions)
>
>
> I'm trying to deploy a transparent proxy server for a friend's office but have
> run into a couple of snags that I can't seam to find the cor
Are packets from the proxy going through 192.168.0.254?
you may have to have a rule to let them out without being fwd'd again.
On Tue, 25 Feb 2003, Darcy Buskermolen wrote:
>
> (Promoted to -net due to lack of responces on -questions)
>
>
> I'm trying to deploy a transparent proxy server for a
Hello,
> Yes, it's me. I'm still alive.
It's great to hear that one of the most talented FreeBSD hackers is back
in business :)
Does this means that you can afford some time to investigate the problems
regarding your old software?
I mean ng_fec primarily, because I couldn't get help in the past
> Hello,
>
> > Yes, it's me. I'm still alive.
> It's great to hear that one of the most talented FreeBSD hackers is back
> in business :)
>
> Does this means that you can afford some time to investigate the problems
> regarding your old software?
Not unless it's something I can fix using easily
