Jump to content

brwainer

Member
  • Content count

    2,421
  • Joined

  • Last visited

Awards


1 Follower

About brwainer

  • Title
    Veteran

Recent Profile Visitors

1,865 profile views
  1. Router to Switch vs Router to Router

    This seems like silly advice. Traditionally, straight cables are for use between an infrastructure device (switch, router) and an endpoint device (computer, printer, etc) while you need to use a crossover cable if you want to connect two infrastructure devices together, or two endpoint devices. Some old infrastructure devices (mainly hubs and switches) would have an “uplink” port that basically had the crossover builtin internally so that you could use straight wiring instead. But this is all a thing of the past due to Auto-MDIX which is a process where the port can swap its TX and RX pairs as needed automagically (this is negotiated/detected during the same communication that determines the speed and duplex). Auto-MDIX has been around since at least 1998 and is present in every ethernet device I own except some Cisco 2950 switches. Also Gigabit Ethernet doesn’t care about this at all because all four pairs are both TX and RX at the same time. For more see https://en.m.wikipedia.org/wiki/Medium-dependent_interface
  2. Forwarding Ports for Xbox?? MikroTik

    You already have what @beersykins was suggesting that you do, because you have the default rules that Mikrotik made. It is important to understand that these default firewall rules only apply to devices that Mikrotik intends for SOHO use (generally anything that has wireless or less than 8 ports) and also that even if you have one of these SOHO devices it is possible to not have any firewall rules if you reset to defaults and then don't use one of the Quick Set profiles as a starting point. The general rule of thumb is to use Quick Set the first time you log into a device, and then never touch it afterwards again. Anyway, let's discuss the suggestion in specifics. "input rules" are anything that is on the "Chain" of "Input". Input is anything whose destination is the router's own IP. The other possible chains are Forward (anything whose destination is some other IP), and Output (anything that the router itself is sending , this does not include traffic leaving the router due to forwarding). If you look at your Input rules you'll see that you are accepting ICMP (pings), anything from the LAN, anything to do with l2tp, a couple other rules that I can't see the details of in the screenshot, and then dropping everything else. This is a pretty standard and good input filter list. The mention of "established/related" is a bit odd since that is a Forward chain thing, not an Input Chain. But you do have that rule, as well as the other normal things like FastTrack, dropping invalid, and dropping anything from WAN that is going through dstnat (this protects you from someone being on the WAN side of the router but trying to directly access your internal devices via IP - with your internet connection being over PPPoE this is basically impossible, this default rule exists because there are other circumstances where your "WAN" might really be a shared network and other people's equipment might be on the same network and able to reach your router directly) Overall your firewall rules look normal and I have no concerns.
  3. Forwarding Ports for Xbox?? MikroTik

    I wouldn't be terribly surprised if the system assumes a blank value for "To. Ports" means to use the same as the Dst. Port, but that is relying on an assumption that might change in future updates.
  4. Forwarding Ports for Xbox?? MikroTik

    On the General tab, take the ports you have in "Src. Port" and move it to "Dst. Port". Then on Action put in the same port number. Your Plex Server rule appears to be correct, although I can't see the "To Ports"column in your screenshot (it isn't added by default, you can do so by clicking the down arrow to the right of Packets)
  5. @leadeater is the only person I know of on the forum with Aruba WAP experience. There may be others who just haven’t been vocal yet. My only Aruba experience is using the 7005 controller as a gateway device. Just for general information, do you have an active directory domain set up or is everything using its own local credentials?
  6. Forwarding Ports for Xbox?? MikroTik

    He is using RouterOS, the same OS run by all Mikrotik devices. He’s in the right section for port forwarding just needs help with the rules. The fundamentals are the same as setting it up on PFSense because they both do it via the NAT section of the firewall config, and both have more or less the same configuration options. Anyway there is a fairly indepth wiki for RouterOS, the page for NAT is https://wiki.mikrotik.com/wiki/Manual:IP/Firewall/NAT
  7. Forwarding Ports for Xbox?? MikroTik

    In you dst-nat rules to have to set the “to port” on every rule, it is right under the “to address”. Can you show us the rules from webfig (the http interface) or winbox? I’ve not used the android tikapp before (I think that’s what you’re using?) so things look a bit different to me. Edit: also with dst-nat you should only be putting port numbers into the dst-port not the src-port.
  8. Ubiquiti is not an enterprise wireless solution nor do they claim to be. All of the actually enterprise wireless brands cost more or less the same as Ruckus (except Meraki but then you’re paying for something a bit different)
  9. I don't know about other industries, but in the hospitality world we install an AP into every guestroom or every other if the rooms are small. Ruckus, Extreme, Cisco, doesn't matter what brand. Noone in an enterprise environment installs a different number and type of AP just because of one brand or another. All the other enterprise brands have their own beamforming under various names - Extreme, Meraki, etc. Saying "you install 2 to 3 times less APs when using Ruckus" should really be "you install 2 to 3 times less APs when using enterprise grade ones". This gets back to my point from my first post - the two devices you are asking for a comparison about serve two different markets and use cases. Linus already did a Ruckus (enterprise) versus non-enterprise review, and there is nothing to gain just because there is some new shiny models on both sides of the divide.
  10. Those two devices serve entirely different markets / use cases so while you could do a comparison between them on the pure wireless experience, it wouldn't make sense to. The R720 is meant to serve hundreds of clients in a close space, it isn't tuned for covering large areas or a place with lots of walls like a house or apartment (lots of walls means lots of reflections) with small numbers of devices. While the R720 will do excellently, I would expect that of an $800 unit (current street prices if you aren't buying in volume)
  11. WHat is this connected to my internet?

    This is a MAC address, the fact that searching the MAC address brings up results for virus detections is completely unrelated and a coincidence. You can't find anything useful from a MAC address just by putting it into a normal search engine. There are sites that can take a MAC address and tell you the manufacturer, because the first six digits of a MAC (called the OUI) are assigned to specific manufacturers to use. My preferred site for looking this up is DeepMac: http://search.deepmac.org/search.php?date=&macadd=50%3A6A%3A03%3AC4%3A94%3A99&comp=&dev=&numresults=50 From this result we can see that the MAC you are seeing is a Netgear device.
  12. Virtual machine router

    I've never reviewed that guide but I'm sure it is serviceable. You'll need two different virtual switches one for the WAN/DMZ and the other for the LAN port. Things that the PFSense will port forward to will need to be connected to the LAN switch somehow. The "somehow" again comes back to either separate physical ethernet ports (and an external switch or whatnot) or VLANs. Or if your other things that need ports forwarded to them are all VMs then they should just connect to the LAN virtual switch.
  13. Virtual machine router

    at work we run routers/firewalls (specifically PFSense) on ESXi all the time. The setup can be a little tricky because you need to separate the WAN and LAN of the VM somehow, either by separate physical ethernet ports or by using VLANs.
  14. IIRC either Elon or Gwynne was asked if this could be used for cellphones and they said not really. I can’t find the exact source but I remember from somewhere that the transceiver is going to be large-ish, like 12”x12” - like a large enterprise AP e.g. Ruckus R710. They aren’t going to have a traditional satellite dish, but you do need something on the larger side to send and receive from satellites at high speeds.
  15. Agreed, I never said it would be a problem - its the same as cell tower roaming but in reverse. But there is going to be a certain amount of jitter (variance in latency) even if they can manage it very well. And yeah airplanes are going to be an interesting aspect.
×