![]() ![]() What i know from the past is that the iap135 in cluster was once a plain real ap135 which was aruba-lab-converted somehow to iap by reflashing, it was from an old SE who gave that to us few years ago. Show tech wont help here as the config lines were already removed after i experienced the existence.įeeling little bit unconciousness how those were added. i just expect this was cause by some software bug during upgrading the OS - which is done regularly.ĭo you have guys in engineering where you can ask about the strange IP adress? I cant imagine someone would have hacked my internal network by passing the external firewall, then executing a virus/trojan on one of my clients and just brute-forcing the webui/ssh instant-cluster and adds AWMS config lines just to observe. I would expect, if this is aruba-central/activate that a hostname would be used instead of a plain IP adress.ĭo you know if there's some CLI command showing OS upgrade history, then i try to reproduce by downgrading to the OS where the config lines werent added, restoring october 2016 config and then upgrading the same way again to see if the AWMS config lines add themselves again. Unfortunately cant open case cause no maintenance on the instant-cluster serial numbers.Ĭjoseph : is/was there any instant OS with automatic call-home feature like Aruba_Central/Activate which could explain this behaviour? perhaps cause of some instantOS interim upgrade "bug" (or whatever) this just added magically without any intervention? i just wonder why and "how" those config lines added to my config. Someone can clearify this, as i dont see hints in release-notes, perhaps it's the usual cloud management, but i would expect that german customers are freaking out if magically AMS IP adds itself thru upgrading the instant OS -) So, what's up with this magic config additions, BB is watchin' on verizon ? -) : (pointing to iap105 and iap135 file, the usual way many ppl use). normally upgrading happens with local file upgrades e.g. It was never managed by airwave/ams, so i wonder why config lines like this suddenly are added after plain upgrading.Īs i kept config file histories, it seems this already happenend after upgrading to 4.2.4.3 in october, today i upgraded directly from webui to 4.2.4.4 as it was finally once offered again. ![]() "Dynamic" means it doesn't belong to a particular machine - it's temporarily assigned to that machine for some period of time, but that machine might get a different address assigned to it at another time.Did i miss something ? i browsed today thru my config of iap-cluster (105/135) and saw that webui management say "airwave" management instead of "local" as it was for more than 2-3 years. How do i find out who is responcible for the traffic coming from it.Īsk Verizon who had that IP address during the times when you saw traffic to and from that host. If it's a server - which I suspect it's not - it's probably not stored on one of Verizon's servers it's probably stored on some Verizon customer's machine. What sort of FTP control traffic (commands and responses, as opposed to data traffic) is coming from that host, and what sort of traffic is going to that host? If commands are coming from the host and responses are going to the host, it's an FTP client if commands are going to the host and responses are coming from the host, it's an FTP server. "pool-100-36-132-90" probably means that it's a dynamically assigned IP address from Verizon's pool of addresses the address is 100.36.132.90.Īlso considering this is FTP traffic, is this device an ftp server ![]() In fact, it's probably in Northern Virginia, as per the "washdc", as in "Washington, DC". It says that this particular IP is for a device in Virginia ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |