To allow Default LAN (VLAN 1) initiated traffic to reach devices on any other VLAN defined on the UDMP device and block traffic between VLAN's.
Device: UDM Pro
OS: 4.0.21 (Official release up to date as of 2024-11-27)
Networks: Two VLAN's, default (1) and Guest (30)
Profile Name: All private IPs RFC1918
| Ambientweather's servers had problems some problems which led to a data delivery failure | |
| Their server problems were resolved, however, they use Amazon Web Services (AWS) | |
| They changed to a new AWS server, left the old one running, but the old one doesn't process data, or the authentication credentials of our WS-2902 were not present. | |
| The old server does, however, give an OK response when sent data - we were sending data, the server said it was OK, it wasn't | |
| The WS-2902 console caches the IP address of the remote server and does not renew it ever (as far as I can tell) | |
| Removing power and battery backup from the weather station and then plugging it back in clears the IP address / Hostname cache. | |
| The Ambientweather station is now talking to a new server that does process data. | |
| Ambientweather.net and all downstream weather services should be getting updates as of 2022-09-26 1240 |
| The following error message is logged to /var/log/syslog by hpcups and indicates that the CUPS subsystem | |
| is attempting to query the SNMP 'public' community name to retrieve printer device information. | |
| io/hpmud/jd.c 94: unable to read device-id | |
| Unfortunately this stops the hp cups subsystem from printing with the following error in /var/log/syslog | |
| prnt/backend/hp.c 825: INFO: open device failed stat=12: hp:/net/HP_LaserJet_P2035n?ip=10.10.0.25; will retry in 30 seconds... | |
| A look at the code base for jd.c shows that an SNMP query failure generates the "unable to read device-id" error message |