1.8b Development

I have been using IOG to monitor the WAN interface bandwidth on my GB-1000.

Today I upgraded to the new 1.8.0b518 from 1.8.0b517.

With 1.8.0b518, the reported output and input bandwidth values are now reversed. That is, what is really incoming bandwidth is shown as outgoing by IOG.

I haven't made any changes to anything other than upgrading m0n0wall.

There are at least two possibilities.

One is that the interface numbering internal to the SNMP Agent has changed and I am really monitoring the LAN bandwidth, not the WAN.

The other is that the meanings of ifInOctets and ifOutOctets have been reversed in the Agent or the MIB.

I can probably cobble together a workaround in the meantime, but I would appreciate the developers who "touched" 1.8.0b518 to review their notes to see what has changed in the area.

Thanks.

I have sorted this out and attribute the problem to a change in the m0n0wall MIB.

Here are the values in question.


For 1.8.0b517, the last version that worked properly:

OID=.1.3.6.1.2.1.2.2.1.2.1, Type=OctetString, Value=fxp0  (LAN interface)
OID=.1.3.6.1.2.1.2.2.1.2.2, Type=OctetString, Value=fxp1  (WAN Interface)
OID=.1.3.6.1.2.1.2.2.1.2.3, Type=OctetString, Value=fxp2
OID=.1.3.6.1.2.1.2.2.1.2.4, Type=OctetString, Value=fxp3


For 1.8.1b522 which is problematic with the problem first appearing in 1.8.1b518:

OID=.1.3.6.1.2.1.2.2.1.2.1, Type=OctetString, Value=usbus0
OID=.1.3.6.1.2.1.2.2.1.2.2, Type=OctetString, Value=fxp0  (LAN interface)
OID=.1.3.6.1.2.1.2.2.1.2.3, Type=OctetString, Value=fxp1  (WAN interface)
OID=.1.3.6.1.2.1.2.2.1.2.4, Type=OctetString, Value=fxp2
OID=.1.3.6.1.2.1.2.2.1.2.5, Type=OctetString, Value=fxp3

As can be seen, the last OID digit of the fxp interfaces has been incremented by one in the b522 version.

The result of this was that IOG was now tracking the wrong adapter, my LAN adapter instead of my WAN adapter. This explains the direction reversal of the measured bandwidth.

The usbus interface has been introduced in FreeBSD 8.3, but as it's not needed in m0n0wall, I have just commited a change to the loader.rc script that disables it. Please try again with b523. Thanks for the report!

Thanks for the quick fix, it is now back the way it was with 517.