Dynamic VLANs Assignment using MAB, LDAP and ACS Server - ldap

I'm new to this forum. This is my first post. Now I'm working on how to dynamically assign switch ports to their respective VLAN by using MAB with ACS server. I've LDAP database that contains greater numbers of end device 's MAC addresses. I want to use Mac address bypass feature in ACS server which will send query to LDAP database to authenticate the mac address. If the mac address is valid then i want to read a specific information which is VLAN ID that stored in LDAP and send back to the switch that end devices connected. From the reply from ACS server, the switch now can read the VLAN ID and match with its own VLAN database and set that particular ports to that vlan.
My question: Is it possible to do this in ACS server by using MAB?
Is it possible to do this in ACS server by using MAB?
If no, is there any other technology that can help to actualize my idea above?
In nutshell, can I automatically change VLAN in the switch based on the information stored in LDAP database such end device's mac address and vlan ID for that particular mac address by using ACS server?
Thanks in advance. :)

Related

Remote control OPC ip address

I am new with OPC UA world and I need to getting start with this. I have a company in witch there is a new machinery that is an opc server. This machinery is actually linked in internet with dhcp. In particular, I need to understand:
For remote control on the same network I only need to take the ip address (eventually static) and I can monitor and write values of the server, is this right?
OPC UA server provide different endpoints, typically in the form of opc.tcp://myOPCUAServer:12345/path those endpoints can be discovered using the local IP address or DNS name. Your OPC UA stack typically provide functionality to list all the endpoints, like DiscoveryClient.GetEndpoints() and than select one for you CoreClientUtils.SelectEndpoint().
Often endpoint support different connection settings like Security Policy (e.g. Basic256Sha256), Message Security Mode (e.g. SignAndEncrypt) and User Authentication (Anonymous, Username/Password, Certificate). Your client connection would need to support the same, in order to connect.

Reprogramming Pet GPS tracker to send data to my own server

sorry if this is the wrong "stack". I could not find a better suited.
I bought a GPS tracker for my dog, which came with a subscription, a SIM card and a poorly developed app.
I have cancelled my subscription and want to use the device to send location info to my own server.
The device has a micro USB input and a SIM card slot. There is not much more I know, but if you have questions which may help find the answer, I can try to take it apart a little more.
So basically, is there some way I can reprogram this device to use my own SIM-card and app?
Plugging the device into my computer does nothing(as expected) however it does register in devmgmt.
Do not worry about the actual reprogramming, I can handle that myself.
Thanks in advance
Edit:
Thank you for feedback.
Image provided.
It does not, as I first thaught, register in the device manager.
I do have an IMEI number for it, but I cannot see a manufacturer anywhere on it. It might be on the underside, but the battery is glued on there.
Based on the Model Number LK120 After some Googling I found a documentation with the following SMS commands. Link to documentation LK209
Note send the commands without Square Brackets
// I guess you've already done 1 and 2.
1 - Set Admin Number - admin123456 [YOUR_PHONE_NUMBER]
2 - Set APN - apn123456 [APN_DETAILS]
//123456 seems to be the password - If the company you got the tracker from provided a different password - try that.
3 - SET the IP and Port Number - adminip123456 [IP_ADDRESS] [PORT_NUMBER]
As this Tracker is either TCP or UDP based - Can't really tell without the actual protocols and User Manual - you will have to setup a TCP and UDP Server and see which Protocol the Tracking Device connects via.
There are a few free software that can setup a TCP/UDP Server on your local machine for testing. [https://packetsender.com/]
Note that the IP address you set on the Tracker must be your Public IP Address, not Local LAN IP Address. You can get the Public IP from here - https://www.whatismyip.com/
Also you will need to open the port of your choosing on your Router and forward the Port to your PC make sure the port is not in use by another application e.g. 9999. This is possible for most Routers. You should be able to access your router admin panel using a browser, details should be on your router.
Also open the port on your PC firewall.
You can always check if it is possible to connect to your Server by going to CMD and running the following command (or use the Packet Sender software to test)
telnet [PUBLIC_IP_ADDRESS] [PORT]
If you can connect via the above command then the tracker should also be able connect.
Note Let us know if the SMS commands work, you should get a response if they work.

API Connect On Premise OVA Properties

I noticed while deploying API Connect that the OVA had a variety of useful properties that I could set to get my on premise deployment up and running much more rapidly and securely. I couldn't find any documentation on them though. Can someone explain what all of these properties do?
I've bolded the ones I really care about, but bonus points if you explain them all and show how to craft an ovftool command to set those properties.
hostname
domain
Ip Address
Netmask
Gateway
Primary DNS
Secondary DNS
NTP
Domain Search
Cloud IP address
Username
Password
Email
These properties are referenced in https://www.ibm.com/support/knowledgecenter/en/SSMNED_5.0.0/com.ibm.apic.install.doc/overview_installing_mgmtvm_apimgmt.html
When configuring multiple (a cluster of) management nodes into a management service, use the Cloud IP address to tell the 2nd..nth nodes where to find the 1st (leave blank for the 1st node).
Email is the email address of the Cloud Manager "admin" user.

How can a server know which client is connecting it while the client is using getInputStream:outputStream:?

I am using hotspot to communicate with iPhone, I publish netservice and connect each other. While every client can find many devices, when one of them connect my device by using getInputStream:outputStream:, how can I know which one is connecting me? PS:I have tried to resolve IP, but IP address can change any time.
Make your hotspot send some defined credentials (such as a host name) on the first attempt to connect. When accepting an input stream, check, if these data are provided and you're all set.

Broadcasting hostname and IP address

In order to notify all computers within the same LAN about my existence, I want to broadcast my hostname and IP address.
How do I go about doing so without sending them as a string?
Avik, this is what DNS is meant to be used for. While "regular" DNS is meant to hold names and IP addresses for each machine (statically configured), there is a dynamic DNS protocol which allows machines to update their DNS entries in real time.
This sort of capability is used in some of the office environments for my clients where printers on a machine are shared but the machines they're attached to use DHCP (meaning their IP address can change).
See here and here for details and the Windows implementation with DHCP.
Lets call your machine that wants to advertise itself the SERVER and all the machines that can use it, the CLIENTS.
Of course, dynamic DNS only notifies DNS itself of the name/IP mapping and is useful if the CLIENTS are already aware of your SERVER so they can get the IP address from DNS. If you have no way for CLIENTS to discover that your SERVER has just been added, you'll still need to broadcast a packet occasionally indicating that your SERVER exists (this will only need the SERVER name since CLIENTS will use DNS to get the IP address).
This broadcast packet should be picked up by all CLIENTS and kept in a local table. If the communications from a CLIENT to your SERVER fails, the local table entry for your SERVER should be removed (it'll be re-added when your SERVER broadcasts again).
Basically re-inventing NetBIOS or ZeroConf, as popular with small embedded devices for discovery by a Windows or OS X based installer or setup utility.
You can try to use UPnP Discovery.