By default Vera automatically configure it's network, in your case if you connect it to your router it will automatically configure in switch mode. From the logs I've noticed that your router assigned 198.168.1.100 ip to your Vera unit, which is wrong because it's an internet IP ( it should be 192.168.1.100 ). TAIPEI, TAIWAN, Sept. 13, 2019 –LITE-ON Technology Corporation (TWSE:2301), a global leader in optoelectronic components today announced that it signed a strategic partnership agreement with, II‐VI Incorporated (Nasdaq:IIVI), a leader in semiconductor lasers, to partner in the volume manufacturing and commercialization of packaged semiconductor lasers for mass-market light.
By default Vera automatically configure it's network, in your case if you connect it to your router it will automatically configure in switch mode.
From the logs I've noticed that your router assigned 198.168.1.100 ip to your Vera unit, which is wrong because it's an internet IP ( it should be 192.168.1.100 ),
and because of this Vera will auto configure in gateway mode with firewall active and you won't be able to reach it and on findvera.com
and you'll see 'Vera not found on your home network' message.
Please follow this steps to fix it:
- unplug Vera from the power cord
- unplug all the cables from Vera
- plug a cable from your computer into Vera's LAN 1 port
- plug Vera into the power cord
- wait it to start and for your computer to get an ip address:
+ on windows you can type this in Start->Run to view it: cmd /K ipconfig
+ on linux and windows you have to start an command line and type there ifconfig | grep -B1 'inet addr'
+ by default you should receive an ip from Vera that should be in this range 192.168.81.100 - 192.168.81.254
- if you've changed the default LAN IP in Vera you'll receive an IP from that range
- if you've disable Vera's dhcp server you won't receive any ip and you'll have to setup one manually on you pc
that should be in Vera's subnet ( ie: if you've left default ip lan settings but disable dhcp you'll have to put on your pc an ip like 192.168.81.2 )
+ after you have an ip on your PC and you can ping Vera's ip successfully open an web browser and type this:
http://192.168.81.1 or http://<and_the_ip_that_you've_set_on_your_Vera_LAN_side_in_Net&Wi-Fi_page>
- Vera's web interface should open and then go to Setup->Advanced->Net&Wi-Fi
+ check the Internet settings:
- if you let it to DHCP, your primary router should assign an IP address to Vera
- if you don't have a dhcp server you can set it to Static and manually set an IP to your Vera
+ Firewall
- if you connect your Vera to another router you have to set it to No Firewall (bridge)
- if Vera is directly connected to the cable modem set the Firewall to Active
* more informations can be found on this manual page: http://wiki.micasaverde.com/index.php/Networking_Setup
+ LAN
-DHCP Server: off - if you connect vera to another router
on - if you connect Vera directly to the internet
- IP address: - this is Vera's lan ip address, this SHOULDN'T be the same or in the same subnet as it's Internet IP or as other router that's on your network
- you can reach Vera on this IP only if the firewall is in 'No Firewall (bridge)' mode and you're connecting to one of the LAN ports of Vera
- Press Save and Apply only if you've done any changes. Pressing this will disable the auto-network configure function!!! So if you connect right now your Vera to another router
and the firewall is set in bridge mode and then you connect your Vera to your cable mode, you'll have to manually set Vera's firewall to Active or No Firewall in order to have
internet access on your PC also.
- connect the WAN port of your Vera to your other router or cable mode.
+ if you connect it to a cable modem: the first time you'll have to power cycle the cable mode, wait for it to synchronize and then plug Vera's cable in it
+ if you connect it to another router, it will switch in bridge mode, you'll get another ip from your main router and you won't be able to access its UI
- you'll have to reconnect to it's Internet ip which you've setup manually or it was released by your main router dhcp server
- or if you have your pc connected to the internet and Vera is also connected to the internet ( the power led is solid ) you can go to
http://findvera.com and click on 'Configure Vera on my home network'
In order to activate the findvera.com service you'll have first to connect directly to your Vera and the go to Setup->FindVera.Com page and set it up.
I manage a small network that uses a router running Tomato firmware to host a guest wireless network on separate VLAN (setup guide). The modest 3000/512 DSL connection is easy to overload but after a recent speed complaint, I started noticing some odd traffic.
On Tomato’s QoS > View Details page, I could see that there was UDP traffic going to and from TLDs all over the world (.au, .ar, .ua, .is, .ru, ..su, .za). Much of the inbound was to port 62416, but it looked like it stopped at the router—that port is not open—so I once I determined it wasn’t a UDP flood, I wasn’t too concerned.
However, a few days later, I noticed something odd: Tomato’s Bandwidth graph for the Last 24 Hours showed a near-constant outbound of over 300 kbits/second (in blue below), effectively using most of the available upload bandwidth:
I also confirmed on the Bandwidth > Daily page that the router was seeing a sudden 3-6 times increase in total traffic compared to its average of about 1.3GB per day. (That average may actually be high since I rebooted the router not long ago.)
Finding the Rogue Device
So which device is causing this sudden increase in traffic? Tomato’s IP Traffic > Last 24 Hours graph can help find it, but the graph seems to stop working after a while, maybe because there is a limit to the number of devices it can display. Here’s what worked this time:
Liteon Network & Wireless Cards Driver Download Windows 10
1. Reboot the router. Under Status > Device List, check which device connects first. In this case, the first unknown device was named 5CD2431DLM and has a MAC address starting with 20:68:9D. That’s made by Lite-On Technology Corp., which unfortunately tells me nothing about what kind of device it is in. It is listed with an IP address on the public WiFi network, so we’re looking for a wireless device.
2. Install Nmap on a computer that is on the WiFi network. The Intense Scan tells me the device is probably running Windows 7/2008:
Port 3389 (RDP) was not open. I tried browsing the network share but failed the authentication challenge.
Liteon Network & Wireless Cards Driver Download Windows 7
3. The wireless access points are all fed off a Cisco SG200-08P switch behind the Tomato router. I turned on port mirroring on the switch and used Wireshark to capture some packets to and from the rogue device. There was a lot of UDP traffic and some TCP. I thought this might tell me what the device was trying to do but it was not obvious at first glance. I did confirm IP addresses in foreign countries (Sweden and Australia to name two).
4. Figure out which wireless access point the device is using. I pulled up Tomato’s IP Traffic > Real-Time graph and highlighted the rogue device. I could see active outbound packets. Then I unplugged all the access points from the switch. Sure enough, the bandwidth dropped to zero. Then I plugged the access points back in to the switch until I figured out which one the rogue device was using.
5. Look around for rogue devices in range of the access point. Unplugging a couple of printers didn’t help. Staff devices (phones and tablets) were identified and did not match the rogue device’s IP. Wishing for a gizmo that could physically locate the offending machine by giving a “hot/cold” reading on the source of traffic to/from a particular IP address. Most tools seem designed to find rogue access points, not individual devices.
6. Log in to the Cisco 1130AG access point and drill down to the connected device. The only thing interesting here was that its signal strength was –85 dB, a fairly weak signal.
Lite-on Network & Wireless Cards Driver Download
My hunch is that this means one of the residential neighbors has learned the loosely-kept WiFi password. Unfortunately it seems their computer has some kind of virus that is phoning home to servers all over the world, and chewing up the client’s limited bandwidth in the process. (In later analysis, I found some BitTorrent packets in the Wireshark capture, so this may have been “normal” BitTorrent traffic, but it was still not welcome on this network.)
7. Oddly, Tomato does not seem to have a way to block a device from receiving a DHCP lease. Adding a block under Basic > Wireless Filter doesn’t help, because we’re not using the wireless in the router; we’re using access points. The best I could do is go to Access Restriction and add a full-time block on the the rogue MAC address:
This blocks Internet access, which solves the main issue (bandwidth use). However the rogue device is still attached to the WiFi network, which I’m not too keen on. We may wind up changing the WiFi password.