Hi kbr, big bad world is the name of the external network. This does not appear in any of the reports prior to 8.163. Prior to 8.163 that line in the report was reported as the ASG hostname.
This seems to be a bug. When using pppoe, the external interface address and the external broadcast address are the same. Therefore in daily reports, the external traffic is showing up as external network (Broadcast).
Hi Ian,
can you see from the packetfilter log what traffic it is that get's dropped?
Hi kai,
this is some sort of a bug. If you notice the screenshot that Ian posted, its not the top 10 dropped addresses, its the top 10 clients. So its not going to show up in packet filter logs. It seems to be the external network traffic.
I have the same problem by the way and the only thing Ian and I have in common is the pppoe connection.
Regards
Bill.
Edit: Just noticed in the daily executive report that the external ip also shows up as external broadcast in the application control section of the executive report. Screenshot added.
I agree, the external IP shouldn't appear on the Top-Clients list at all.
One more question: Does the order of magnitude of that traffic fit into what you expect the total traffic to be?
Hi, I don't mind the external IP appearing in top clients. Infact this behavior is consistent with previous versions (http proxy traffic I believe). However any broadcast would never generate that much traffic for our home setups[;)]
When you look at the external network definition for our setups (pppoe), there is no difference in the address and broadcast (again consistent with previous versions). So at first glance, this appears to be a case of mislabeling, but I might be wrong on that.
this will be fixed in the next beta. Current beta resolves IP addresses to interface name if match. PPPoE has a /32 netmask, in fact there is no broadcast address set. So next beta will not set broadcast addresses for /32 and /31 netmask...
