Choose your cart
Choose your cart
Receive up to $504 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $504 w/5G Do More, 5G Play More, 5G Get More or One Unlimited for iPhone plan (Welcome Unlimited and One Unlimited for iPhone plans can't be mixed w/other Unlimited plans; all lines on the account req'd on respective plans)) when you add a new smartphone line with your own 4G/5G smartphone on an eligible postpaid plan between 2/10/23 and 4/5/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
$699.99 (128 GB only) device payment purchase or full retail purchase w/ new smartphone line on One Unlimited for iPhone (all lines on account req'd on plan), 5G Start, 5G Do More, 5G Play More or 5G Get More plan req'd. Less $699.99 promo credit applied over 36 mos.; promo credit ends if eligibility req’s are no longer met; 0% APR.
Hi,
Lately Eset internet security has been going crazy with notifications that its blocking ARP Cache poisoning attacks and that there is a duplicate ip address at 192.168.1.1. That is strange because that is the source of the G3100 router and not sure whats going on or if the device has been compromised or is this a false positive due to how the router works.
Thanks
Solved! Go to Correct Answer
Turns out I had another router that I had configured to use as a switch and somehow the settings reset and it was running as another dhcp server. Once I realized the source I was able to fix the problem.
Thanks
Points to https://www.comparitech.com/blog/information-security/arp-poisoning-spoofing-detect-prevent/
to where it says How to detect ARP poisoning and as well as the first three listed options on How to prevent ARP poisoning.
Maybe also the fourth option on How to prevent ARP poisoning.
Do you have other networking devices on your network? This could potentially be an IP conflict after all. Do you have other routers and modems that are not powered down completely?
Turns out I had another router that I had configured to use as a switch and somehow the settings reset and it was running as another dhcp server. Once I realized the source I was able to fix the problem.
Thanks
I thought that too.
oops