I am trying to setup LTE kernel with VoLTE capabilities (test zone with mnc 001 and mcc 01).
But something goes wrong...
My Alcatel 5033d does not recognised that LTE node has VoLTE capabilities and never ask about P-CSCP address
There are too much ways to check and investigate.
May be somebody pass this way and could advice me?
Now I have in my configuration two machines with NextEPC and OpenIMS with FHoSS HSS.
I am successfully attach to LTE node with modem or smartphone and could access to the internet, but cannot make voice call.
My test SIM card has an ISIM profile but never use it.
I have checked my Alcatel - it could attach and VoLTE with SIM card from my local operator.
Related
I have a Raspberry PI with two NFC readers attached. Problem is that the readers get different device numbers each time the system reboots or a reader is detached and attached again.
I therefore created udev rules that create a fixed device name depending on the physical port a device is attached to. E.g. plug in NFC reader in the upper left port leads always to /dev/nfc_a and plugged into the upper right port leads always to /dev/nfc_b.
How can I now configure libnfc to use these devices and report the device names such as /dev/nfc_a as a part of the reading? I am using Node-RED with node-red-contrib-nfc (https://github.com/hardillb/node-red-contrib-nfc) on top of libnfc. My ultimate goal is to safely distinguish the two readers within my Node-RED flow to act differently upon the readings.
I already found the "connstring" configuration but I don't know how to correctly set it for using /dev/nfc_a.
It's been a LONG time since I wrote this node, but looking back at the nodejs library it's based on (nfc) the output message should contain a field called deviceID which should indicate which NFC reader triggered the input.
When I run on my machine I get:
deviceID: 'pn53x_usb:001:005'
Where 001 is the USB bus id and 005 is the device ID, which matches up with the output from lsusb. These should stay static as long as the readers are always plugged into the same USB sockets.
i've been struggling lately with integrating Rasperry Pi and IBM Presence Insight
for wifi proximity detection
the official documentation describes raspberry pi as possible Wifi Proximity sensor, but there is no available documentation
someone tried it before ?
In order to use Raspberry Pi as a proximity sensor, you will need to:
Build a raspberry pi device with two different wifi adapters
Configure one wifi adapter to be an publicly visible endpoint
Write code to capture every time a mobile device tries to connect to the endpoint
Report that information back to Presence Insights.
Unfortunately, the chunk of code you need to write has not been open sourced, so you will need to do this on your own.
You could probably hack together a solution. It looks like there are a lot of resources out there online about "seeing who connects to my network [1], [2]" You could probably use one of these solutions and just feed the data into Presence Insights in the correct format (see the documentation about "proximity connectors.")
[1] http://www.howtogeek.com/204057/how-to-see-who%E2%80%99s-connected-to-your-wi-fi-network/
[2] https://github.com/tlhunter/node-wireless
I have a raspberry pi with 2 wireless adapters connected to it - one has an antenna.
http://www.modmypi.com/raspberry-pi/accessories/wifi-dongles/wifi-dongle-ultra-long-range-high-gain-w-5dbi-antenna
I am trying to write a script that queries my linux box for wireless interfaces, finds out which one is the one which has the antenna connected and put it into hotspot mode. Tomorrow, it can be any other adapter with an antenna attached.
Are there any tools or commands that can help?
Any entries in /proc or /sys that tell me this is the required device?
Thanks in advance.
EDIT:
Is there a CLI that gives the interface name and the Manufacturer and model?
To know what wifi cards you have plugged in your system, run "iwconfig".
For the antenna, there is no way to know if your dongle has the antenna plugged on, or the antenna has been removed.
I guess, the best workaround could be, query the device for a network scan - then you count how many APs were found: if the antenna has been unplugged, you will not get any APs (or maybe only 1-2...)
I ended up using hwinfo on my pi and doing the text/regex parsing in python to get all the data I was interested in.
I've been having quite a time trying to use IPMI tools (such as OpenIPMI, FreeIPMI, and ipmitool) to discover and monitor a PCI device in my server. Using an IBM server going through IMM over the network using the IPMI tools, I can't seem to be able to get any information on the PCI devices in the server. The IPMI tools only return basic information on the system such as the BMC, chassis, power supplies, fans, etc. No information on the devices plugged into the PCI slots.
I've tried basic commands like "fru list", "sdr elist", etc. and haven't been able to get any information from the PCI slots.
Just hoping someone has had experience using these tools and is able to get information from the devices in the PCI slots.
Specifically, I would like to get the FRU information as well as device ID, I2C slave address, etc. for accessing the device.
Thanks for any information that you can provide...
There is no requirement in the IPMI spec that the PCI connector A side pins 40 and 41 that contain the SMBus are routed to the BMC. A vendor may do it but most do not.
Look at it this way, the BMC can turn off power to the PCI bus and main CPUs. You would not be able to read anything from them anyway.
This is why the AdvancedTCA specification requires management power and two IPMB buses to each blade slot. The AdvancedTCA spec requires the IPMB bus from each slot is connected to the BMC. The blade can power up and use a max 15 watts to supply IPM Controller and you can read the data you are looking for without powering on the main CPUs.
Hank Bruning
JBlade
As my iPhone automatically joins my home network once I get home and press the main button, I thought this could be used as a trigger for some home automation ideas I have,
especially disarming the alarm system for example.
I could detect the iPhone by pinging the broadcast address with a script and then look for it's MAC address in the arp cache, but this would have to be done every 15 seconds or so
to be of any use. This really doesn't seem like the most elegant solution though.
Can anyone think of a better way to implement a check like this? I suppose one could assign an IP address dependent on my MAC address, then I would know what to ping, and could thereafter check the MAC address to keep things secure.
Just suppose I cannot assign a DHCP IP based on MAC address, as the problem
of being able to find the MAC address on the network is the part that really interests me.
Secondly I noticed with tcpdump that the iPhone seems to talk to itself all night, but only some sort of Ethernet frames:
23:59:59.740097 00:26:08:ae:ed:eb > 00:26:08:ae:ed:eb, 802.3, length 70: LLC, dsap Null (0x00) Individual, ssap Unknown (0x20) Command, ctrl 0x33: Unnumbered, 23, Flags [Poll], length 56
This happens every 2 minutes.
How could I monitor this traffic so that my "home" knows I am still there using a program? Could be good to automatically alarm the house when I am no longer there...
I think your router here should be the point of control... If you can log the devices that are logged on to the router you can disable your security based on that info.
If you have an openWrt compatible router http://wiki.openwrt.org/toh/start you can certainly extend to get the functionality you want.
Here is a link plugin for the indigo home automation server that does what you want to do bij logging the info from his router. http://www.perceptiveautomation.com/userforum/viewtopic.php?f=19&t=6876&sid=07a351fa04c2eadcd2d3813afc72ae5a
Note: it's really easy to spoof a mac address so might be interesting to have some other verification too :-)