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 is 192.168.1.254/32(255.255.255.255)

Abel Alejandro wrote:

Hello, I have two interfaces. The rl0 is for monitoring purposes and fxp0 is
for normal internet access.
rl0 is attached to a catalyst port using SPAN, meaning all the traffic going
to the internet gets mirrored to
this port. fxp0 is on the same catalyst.

If I shutdown rl0 then I can access fxp0 from the outside, but if I ifconfig
rl0 up then
I am just allowed to access fxp0 within machines in the 196.12.X.0 network.

rl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
       inet 10.0.0.1 netmask 0xa0000fc broadcast 255.255.255.3
       inet6 fe80::2e0:7dff:fed0:fdf4%rl0 prefixlen 64 scopeid 0x1
       ether 00:e0:7d:d0:fd:f4
       media: Ethernet autoselect (100baseTX <full-duplex>)
       status: active
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       inet 196.12.X.251 netmask 0xffffff00 broadcast 196.12.160.255
       inet6 fe80::250:8bff:febb:1689%fxp0 prefixlen 64 scopeid 0x2
       inet 196.12.X.10 netmask 0xffffffff broadcast 196.12.160.10
       ether 00:50:8b:bb:16:89
       media: Ethernet autoselect (100baseTX <full-duplex>)
       status: active

Abel Alejandro.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message





To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message

Reply via email to