Hello,
My AP100x not appear in UTM SG330. Do I need to register the serial number in Sophos central account?
Thanks
This thread was automatically locked due to age.
Guest User!
You are not Sophos Staff.
Hi bigneo7
You should not register AP100x with Sophos Central if you want to use it with UTM9. If you have registered it, you might want to delete it from Sophos Central before connecting it back with UTM9.
If you've not registered it with Sophos Central, that's good. Please check what IP is assigned to this AP100x from DHCP server and make sure that from whichever interface AP contacts or reaches UTM9, it is added in Allowed interfaces under Wireless Protection > Global Settings > Global Settings.
Regards
Jaydeep
Hi Jaydeep
AP100X log show that dnsserver entries are missing.
Here the log:
U-Boot 2012.07 (Nov 21 2017 - 10:06:29)
smem ram ptable found: ver: 0 len: 5
DRAM: 1 GiB
NAND: Detected MICRON MT29F4G08ABBDAH4, total 512 MiB
SF: Detected MX25U3235F with page size 4 KiB, total 4 MiB
PCI0 Link Intialized
PCI1 Link Intialized
In: serial
Out: serial
Err: serial
PHY ID = 0x4dd074, eth0 found AR8033 PHY
MAC2 addr:7c:5a:1c:35:55:7e
PHY ID = 0x4dd074, eth1 found AR8033 PHY
MAC3 addr:7c:5a:1c:35:55:7f
eth0, eth1
Creating 1 MTD partitions on "nand0":
0x000000000000-0x000020000000 : "mtd=0"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: attached mtd2 to ubi0
UBI: MTD device name: "mtd=0"
UBI: MTD device size: 512 MiB
UBI: number of good PEBs: 4096
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 4
UBI: available PEBs: 2068
UBI: total number of reserved PEBs: 2028
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 6/1
SF: Detected MX25U3235F with page size 4 KiB, total 4 MiB
Hit any key to stop autoboot: 0
Read 0 bytes from volume image to 44000000
No size specified -> Using max size (67170304)
## Booting kernel from FIT Image at 44000000 ...
Using 'config@2' configuration
Trying 'kernel@1' kernel subimage
Description: ARM OpenWrt Linux-3.14.43
Type: Kernel Image
Compression: uncompressed
Data Start: 0x440000e4
Data Size: 16266340 Bytes = 15.5 MiB
Architecture: ARM
OS: Linux
Load Address: 0x42208000
Entry Point: 0x42208000
node name: signature@1
Sign algo: sha256,rsa4096
Sign value: 36677d45a4c19d2652341bf20df9546606d11663c1b5b124cd7d2f98e1d7318de3269ee5cc72c2a4c38ffe51ab60972563b1c906637eb8075c4e6e53cfa267eed12f3d4daece603b8bb578f6701db46f178e3a667da9587961dc8782bca17c8eae625d02548ea4d7b51552fcd2fa6e4ff4c5ee43357b979db817183de90703c4af7024cf59966c898cd6118f11ae1c7e017d2ca146ab64011e32896053ab824aed3b38062365e566aa15db34aced4fd3e4c09d5f52e297dc1c7092b0dabf628fdf3dfd2abfbc9ac6aab47ce6b5212569269519a18849e4e1bf9f9a15f4a9684d71536b28a217bf2378d9402fecc08f6a69578bb218571227101f31b95b2034d4937ca87f5abb9994b82c7094a848ff8092979d262e24d2fe0a24c0839839d8b2ab8495792282dc5a3b28e945ed8dbf1cb1e2a785b42ac64fe68cb51ba7809b3f175df86c39e4011bfc9ac1a2ed567aacaee6895875f93fedd0dfa3fbfb5a14165dfbe302fc124d7344f397a63f48ed30b7b7848003e6fd02babfed07ed7e6d6c4580a547c8f39ced724befa221d9cf1b44517f67fc96f225abe1525174dc4fd29169c6d982c0a8a62b81cb7e5c91679e1fd74139ab248d1388af3412e8da50c6a802193e1ca33319d81d15c42bd8c73675227ac89d304fe4856cbfc312d3feeb6293da99bf6f3397d4dc0964ba8e5c4f405e97ad7df26d7db11477dc1b01626a
Verifying Hash Integrity ... sha256+ OK
## Flattened Device Tree from FIT Image at 44000000
Using 'config@2' configuration
Trying 'fdt@2' FDT blob subimage
Description: ARM OpenWrt Sophos-APX device tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x44f8c4ec
Data Size: 24530 Bytes = 24 KiB
Architecture: ARM
node name: signature@1
Sign algo: sha256,rsa4096
Sign value: 8aea249e44fef1269e7583eb15d16ce3b3678eff28dab79b0602215d6ac046ed23715220fb9171bdffac3ef0a4de99e6e5f52010065ad4b26c2bbf585b7fc95130d785214ab8fd21fdb6c29025a78895bc6ca09c29e70a38d48dea16dc7ab2484d1a648385cc9b1d4fca3eed97accbeda91774aaed3fdfcbe31013b1ac3af9b10150d83271aacbf1a84659f94fc9b66ff81403ce594bd1fa7422aa7822ee9b3e1e393f0f3aa933841256f9053671555de8d85519c4a136057de77c9902a6468a7b99fb0e34bc68fe1505d6bda4a756f2e77baddce813aa695ac69ce6fee82d8f3e308d77054cb06263f0713656b419553fc67b8aef32c82d62bb5d5233b1a9936f75b611bce3f36b61a712887d8597b870dc4bdd013fd23f34113d39bd81381c65a377ad7f370b8363e1b671ec92c4dac530b631951edfdd6f4b3742d4588d1f4f2c3466774fce65b74d057b6670f2f10a1e7ac8b03a92ca61488e1eb547e68c3ca1ce6b2d8efbbf33e299ba879c55ebac1392a0066fd0b0991522c7d581c830050afeb23b64b4c5da014718ffe170864f4daf2d04259a18a484f6252979a6ed8a4912f1679eeada36b5d752736451b907f421029d7e863eda7fc87a7ab11a2125e3aefd06f90b770eda1d1814cd824607b6a04161c376fb3c4793544bdfc879bdf546d08d353c08ba3f8621a82aef7189b4556a4093e5f2fb27e14ad0a7e53f
Verifying Hash Integrity ... sha256+ OK
Booting using the fdt blob at 0x44f8c4ec
Loading Kernel Image ... OK
OK
Using Device Tree in place at 44f8c4ec, end 44f954bd
Using machid 0x136c from environment
Starting kernel ...
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
Booting. (Version: v2.1.2-1)
Checking The AP model
/lib/firmware/qca-nss0.bin 37
/lib/firmware/qca-nss1.bin 37
No Direct-Attach chipsets found.
Starting network configuration for ethernet interface over DHCP.
Cloud certificate validation pending.
dnsserver entries are missing
dnsserver entries are missing
dnsserver entries are missing
dnsserver entries are missing
dnsserver entries are missing
dnsserver entries are missing
Ethernet autoconfiguration (bound): IP:172.16.95.3/24, gateway:172.16.95.1, nameservers:172.16.95.1
Ethernet link state changed to: up, Speed: 1000, Duplex: full
Ethernet link state changed to: down
[ 76.634662] reboot: Restarting system
Hi and welcome to the UTM Community!
Jaydeep was asking about the UTM, not the AP. On the ''IPv4 Leases' tab of 'Network Services >> DHCP', do you see that the AP was assigned an IP in 172.16.95.0/24? Is 172.16.95.3 the IP that was assigned? Is the interface to which 172.16.95.1 is bound in the 'Allowed Interfaces' box?
Cheers - Bob
