I am not sure that it is wise to recommend Microtik. Microtik is favourite of massive botnet builders due to their very closed nature and lack of updates.
March 2018: https://blog.radware.com/security/2018/03/mikrotik-routeros-based-botnet/ August 2018: https://www.trendmicro.com/vinfo/us/security/news/cybercrime-and-digital-threats/over-200-000-mikrotik-routers-compromised-in-cryptojacking-campaign Tomas On Wed, Dec 12, 2018, 7:52 AM Chuck Hast <[email protected] wrote: > David, > That is why I use routers that I can load after market software onto. > OpenWRT, DDwrt, Tomato, > anything but the factory stuff. Netgear has put out some real pieces of > work on their hardware. > > I found this one on DD-WRT, if you want to escape the factory stuff this is > an option: > > https://wiki.dd-wrt.com/wiki/index.php/Netgear_R6300v2 > > I am using OpenWRT right now, it is stable and never does goofy stuff. But > I have used all 3 > and they are all much better than the residential router software in my > experience. (YMMV) > > If you want more stable factory software on a router you need to go up > scale. I have a MikroTIK > that just seems to take a beating and never misses, some of the setting up > is arcane (until you > look at it then it makes sense, especially from the cmd line view) > > I also prefer a router with NO wifi. I use access points for that then when > the WiFi stuff moves > forward I am not stuck with a WiFi that I cannot upgrade without having to > upgrade the router. > > I am using a Netgear WNDR3700v2 as I am going to put the MikroTIC in a 1U > rack holder. > It has WiFi on it, and it is turned on but the real WiFi are AP's around > the house. The 3700 > is running OpenWRT. Works great. > > On Tue, Dec 11, 2018 at 8:06 PM David Fleck <[email protected]> wrote: > > > Rebooting the router fixed the problem. > > > > It's a Netgear genie 6200v2, with the original firmware, and getting a > bit > > long in the tooth. This is the first time that I remember it behaving > > oddly. > > > > Thanks for the troubleshooting reminder. > > > > -- > > - David Fleck > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Tuesday, December 11, 2018 7:45 PM, Russell Senior < > > [email protected]> wrote: > > > > > Oh, also check to see that the IPaddr that your problematic laptop has > > is distinct from all other hosts on your network. I recall a problem once > > upon a time with the Paradyne/Zhone DSL modems that Integra Telecom used > > would happily hand out leases of ipaddrs that were already taken on the > > network, leading to periodic clashes with devices with static IPs. > > > > > > On Tue, Dec 11, 2018 at 5:42 PM Russell Senior < > > [email protected]> wrote: > > > > > >> More info needed: > > >> > > >> * What is the router? What is it running (i.e. stock vs 3rd party > > firmware); > > >> * Have you tried power cycling the router? > > >> * Have you looked at dmesg -T on your problematic laptop? > > >> * Have you looked at iptables on your problematic laptop? > > >> > > >> On Tue, Dec 11, 2018 at 5:32 PM David Fleck <[email protected]> > > wrote: > > >> > > >>> My wife and I have 2 practically identical ThinkPad laptops, both > > running OpenSUSE 42.3. They connect to a wireless router via DHCP. We > > also have several desktop machines (Linux & FreeBSD) with static IP > > addresses. All the machines are connected by a router. Both laptops can > > see the router, the outside world, and each other. But one laptop can > see > > all the desktops, and the other one can't see any of them. The desktops > > can't see the one laptop, either. > > >>> > > >>> As far as I can see, the routing tables are the same on both laptops: > > >>> m2:~ # route ### This is the non-connecting laptop > > >>> Kernel IP routing table > > >>> Destination Gateway Genmask Flags Metric Ref > > Use Iface > > >>> default 192.168.1.1 0.0.0.0 UG 600 0 > > 0 wlan0 > > >>> 192.168.1.0 * 255.255.255.0 U 600 0 > > 0 wlan0 > > >>> > > >>> dcf:~> route ### This is the connecting laptop > > >>> Kernel IP routing table > > >>> Destination Gateway Genmask Flags Metric Ref > > Use Iface > > >>> default 192.168.1.1 0.0.0.0 UG 600 0 > > 0 wlan0 > > >>> 192.168.1.0 * 255.255.255.0 U 600 0 > > 0 wlan0 > > >>> > > >>> But when I try to ping from the non-connecting laptop: > > >>> m2:~ # ping 192.168.1.9 > > >>> PING 192.168.1.9 (192.168.1.9) 56(84) bytes of data. > > >>> ^C > > >>> --- 192.168.1.9 ping statistics --- > > >>> 5 packets transmitted, 0 received, 100% packet loss, time 3999ms > > >>> > > >>> whereas: > > >>> dcf:~> ping 192.168.1.9 > > >>> PING 192.168.1.9 (192.168.1.9) 56(84) bytes of data. > > >>> 64 bytes from 192.168.1.9: icmp_seq=1 ttl=64 time=9.59 ms > > >>> 64 bytes from 192.168.1.9: icmp_seq=2 ttl=64 time=0.960 ms > > >>> 64 bytes from 192.168.1.9: icmp_seq=3 ttl=64 time=0.960 ms > > >>> > > >>> I'm flummoxed. Everything I can think to look at on the > non-connecting > > laptop looks right, but the machines simply don't 'see' each other, even > > though they can see other machines on the network and there is no > > difference in network topology distinguishing connecting and > non-connecting > > machines. Reboots (of desktops and the laptop) haven't helped. > > >>> > > >>> Last data point: this was all working correctly 24 hours ago. > > >>> > > >>> -- > > >>> - David Fleck > > >>> _______________________________________________ > > >>> PLUG mailing list > > >>> [email protected] > > >>> http://lists.pdxlinux.org/mailman/listinfo/plug > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > > > -- > > Chuck Hast -- KP4DJT -- > I can do all things through Christ which strengtheneth me. > Ph 4:13 KJV > Todo lo puedo en Cristo que me fortalece. > Fil 4:13 RVR1960 > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
