I am trying to figure out how to create a WiFi network on a 130 rooms hotel. I tried some Access Points on the hallways but the signal is not getting in the rooms as I desired...
Now I am thinking to put 1 access point per room with POE. Is this something that can be done? Will the network work? There will be a lot of ip's (130 only from the AP's?) + the guests.
If anyone can give me some ideas I would much appreciate it!
Marius
You can put a high power AP in the hallway and one AP working in repeater mode in each room to enlarge the signal.
Anyway, the best solution is put an AP in each room and connect them with network interface by line which is more stable.
Hope it helps. :)
Related
I'm looking for a way to extract information from a router, be it from the router directly, through command, or through the routers webpage. I need to extract the amount of connected devices in real time. This has to be sent somewhere, where it gets processed and can be fed into an arduino.
The project is a kind of installation where light reacts to the amount of connected devices to the network. So more devices connected make the light do something and less make it do something else.
Is this even possible?
Thanks in advance!
Usually this information could be obtained from router's administration web interface.
For example, I found screenshot of Cisco router web interface:
Look at the bottom of the image: where are a "Current clients" field with number of clients.
So, this page could be loaded programmatically and parsed for the needed value.
As you didn't specified your router model, or your programming language or any other details, I can't give your more specific solution.
My python isn't that good though. Is there anyway you can point me in the right direction as where to look for this. And the information is in another submenu so is this still possible?this is what my router interface looks like.
I'm playing around With Node-Red (I'm still in the newbie stages)
I have around 20 ESP8266 modules taking temperature and humidity in various locations in and around my home.
The way I am doing it right now, is to put a webserver on each of my ESPs and have node-red poll them every 5 Seconds. This is ugly in all respects, as repeating this 20 times hurts the eyes. I've set up two of them already, and it looks bad:
My question is:
Is there a way I can give node-red a list of the Devices (well, their IP addresses) and have node-red create my desired Dashboard for all of them? Looks like I would need a "for-each" module, as well as something to automatically create a group in the Dashboard for grouping the various gauges/Charts to each sensor.
Not a lot of code to share so far, but I did create a gist for you to see, if you're interested in the webserver part for ESP8266:
Gist of how to Connect ESP8266 With Node-Red using Arduino/C
In advance, thanks for your tips and suggestions
No, at the moment you need to define each widget on the dashboard explicitly.
The closest you could do is use the template node and pass in an array of values that can be rendered in a loop, but that will not work for the Chart node or Text nodes.
I've got an old connection log to a website which contains the IP addresses, the user agent string and the timestamp.
I want to know how many of them used 3G to access a website as I suspect there is a latency issue.
Now I know that I can use some code to have this info directly from the user.
But I still want to process this old log using only IP addresses even if it is only for one ISP.
I thought I could do that by finding a list of the subnets used for 3g.
Do you think it can be done?
Otherwise, what do you suggest?
Hope you can help.
Cheers,
One approach could be to lookup every IP using "whois" services, if the ISP listed is a phone carrier only, you can be certain the connection was made by a mobile connection.
This is not a total solution, but it might give you enough information.
Now, to find a service which will allow you to make all the requests required, might be another matter.
I'm trying to connect to a given number of peers in a P2P network and I'd like to have them span the globe as good as possible (have them as far away from each other as possible). Since I gradually connect to them one after another I will discover better peers one after another and discard (or disconnect) from peers that drop out of my top list. Problem is that I'm stuck defining a metric that tells me how "good" a peer is. I will be using a geo ip database to map ips to geo coordinates but I just can't find a good metric to apply.
In my opinion you should not think of geography but in network topology. For every new peer you should do traceroute and ping so you know how the good the connectivity is. Store this and do cost-calculation. Most simply in just adding up the latency. Bandwidth and latency are more important. If you are concerned with the local laws where the specific peer is located you could start think in geography.
I wonder, are you able to get your users to set a location in their UI? That might be a better measure of geographical spread than ping times. That said, for a variety of complicated reasons - as I'm sure you know - two nodes 500 miles apart may have better speed and latency measurements than two nodes 250 miles apart. So it depends whether you care about location or performance :)
Context:
I have a system that will need to support 20,000 connected chat users spread over 100 chat rooms. During performance testing I've found that I can get up to 6,000 connected users on a single box before I get a crash dump, so in production I'll probably go with four servers in a cluster.
My Question:
I understand that a chatroom is bound to a server node, so that if the node dies the chatroom disappears with it and the users no longer belong to the room. Is there a way to "replicate" a chatroom over to another node so that users who are left behind are moved to the replicated room? If not, what do you do to keep continuity for the users?
What hardware are you using ? 6000 connected users seem a bit low. Also, ejabberd is not supposed to crash under load. It might slow down, but not crash.
There is something wrong in your setup.
About replicating a chatroom node, it's not easy. It's better to handle smooth reconnection on the client side.
But then again, ejabberd should not crash under this kind of load, unless something's wrong.