NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Many FVS318v3 Log Entries: UDP packet "Access Policy not found"
My simple office setup is as follows:
ISP <=> Office Building Cable Modem/Router (Shared) <=> Office Tenants (I'm one of many)...
...my FVS318v3 <=> my single Win7 laptop and HP printer connected directly to FVS318v3
Don't recall getting these log entries before, but I hadn't logged in for a while until recently. Now these are commonplace (always the same IANA-Reserved RFC 3927/5735 "link local" block):
Mon, 2012-01-16 10:15:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:16:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:16:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:17:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:17:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:18:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:18:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:19:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:19:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:20:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:20:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:21:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:21:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
...and so on and so forth. Any throughts as to why?
ISP <=> Office Building Cable Modem/Router (Shared) <=> Office Tenants (I'm one of many)...
...my FVS318v3 <=> my single Win7 laptop and HP printer connected directly to FVS318v3
Don't recall getting these log entries before, but I hadn't logged in for a while until recently. Now these are commonplace (always the same IANA-Reserved RFC 3927/5735 "link local" block):
Mon, 2012-01-16 10:15:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:16:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:16:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:17:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:17:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:18:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:18:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:19:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:19:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:20:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:20:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:21:07 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
Mon, 2012-01-16 10:21:37 - UDP packet - Source: 169.254.25.233 - Destination: 169.254.255.255 - [Access Policy not found, dropping packet Src 138 Dst 138 from WAN]
...and so on and so forth. Any throughts as to why?
9 Replies
- What IP addresses are you using on the network? Public IP on the WAN?
Thanks for stopping by. These are as follows--adit wrote: What IP addresses are you using on the network?
My internal LAN:
192.168.0.1 - FVS318v3
192.168.0.2 - Windows 7 laptop
192.168.0.3 - HP Printer
Building's LAN:
192.168.10.1 - Building's cable modem/router
192.168.10.231 - My LAN via FVS318v3's ethernet WAN port
192.168.10.XXX's - Other LANs/Computers, other offices, other businesses
I assume this means the building's cable modem/router looking at the rest of the world; therefore, yes, I believe so. A "what is my IP address" browser test from my laptop yields an IP address that is not even close to any of the numbers above.Public IP on the WAN? - since you are sharing with entire suite so looks like WAN is all private IP, seems to make sense .
there must be a device behind the WAN side (cable modem> tent router) which are broadcasting the traffic - You'll see goofy traffic come through to the logs when you have private IP's on the WAN. I would get a public IP if possible.
Thanks for your help. I searched a bit today for the term, "tent router," so as not to waste your time, but there's not much out there (at least that I can understand). A few words, or link, on this will be appeciated.jmizoguchi wrote: since you are sharing with entire suite so looks like WAN is all private IP, seems to make sense .
there must be a device behind the WAN side (cable modem> tent router) which are broadcasting the traffic
That's actually an option assuming I understand you correctly, having been already told the building is set up for the cable company to jack directly into individual offices (for what can't be much more than I'm paying now). Then it would be ISP <-> FVS318v3 <-> my stuff.adit wrote: You'll see goofy traffic come through to the logs when you have private IP's on the WAN.
I would get a public IP if possible.- then you WAN of FVS should have public IP and it's not
Makes sense now, thanks. Will get on that ASAP.jmizoguchi wrote: then you WAN of FVS should have public IP and it's not - good luck.. you probably have to pull your won line instead of behind tenants network. :)
- Thanks, mods. I appreciate you helping the much less knowledgeable get a clue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
