Mikrotik RB750 setup help required

[Messugga]

Okay, so I'm a complete Mikrotik noon. I felt the need to revamp my home network a bit and purchased a RB750 to manage a few things for me.

Problem is, this thing is tricky to set up if you're not familiar with MikrotikOS, so I could really use some assistance.

I want to do a few things - I want it to handle DHCP which seems to be working. I need it to open a PPPoE connection via a adsl modem (which I can get it to do) and then I also need to let devices on the network actually use that PPPoE connection to get Internet access. That's the bit I'm particularly struggling with.
I think it's something to do with routing traffic to the gateway port (eth0) that I'm just not doing right.

Alternatively, I'm using a Netgear router as modem currently. It creates a connection to my ISP which would bypass the need for PPPoE but with that being said, I have a ADSL modem on order that might require me using the Mikrotik for creating the connection.

I also need it to do what other routers would call half-bridge mode where it also allows for PPPoE connections from other devices to be passed through to the modem. I read somewhere that that has a trick to it.

Assistance would be greatly appreciated!

 

[paul5186]

Use ether1 to your adsl routet. Under ip/interfaces setup a pppoe-client with your adsl username and password on interface ether1, add default route and use peer dns must be enabled. Then setup a bridge, add ports ether2 to ether5 of the bridge, this will be used for your internal network, much like a switch. Make sure you adsl modem is setup on the same subnet as the mikrotik. E.g 192.168.1.1/24 on your adsl modem. Then under ip/addresses setup 192.168.1.2/24 on the bridge interface. Your next step is to make sure dhcp is turned off on the adsl modem. Under ip/pool setup a dhcp scope e.g 192.168.1.100-192.168.1.200. Then under ip/dhcp setup a dhcp server on the bridge interface using the pool you created. Under the dhcp network tab make sure the network address is 192.168.1.0/24 and the gateway is 192.168.1.2/24. Now dhcp should be setup. Last thing would be to masquarde your traffic i.e basically nats your internal ips via the pppoe connection ip. In ip/firewall/nat add a src-nat rule, src-address of 192.168.1.0/24, out-interface is your pppoe connection, under the action tab select masquarade. Under ip/dns tick the box allowing remote requests. Last think is to secure your mikrotik with a good password. Hope that helps!

 

[Messugga]

Got it working, thanks!

I've also managed to set up a scheduled script to update my UnoTelly IP once a minute.

Next up is getting queues set up for packet prioritization. With Seacom being crappy this weekend, I think I'll leave that for another day so that I get more immediate real-world results.

 

[Messugga]

Okay, the queues isn't working well... I get it to sort of work, but not how I'd like it to.

I want torrent (and other downloads) to run at full speed until anything else in the network requires bandwidth, then they should take a back seat. If I can get that working, I'm sure I can figure out prioritization for my other bits and bobs.

 

[Tinuva]

Okay, the queues isn't working well... I get it to sort of work, but not how I'd like it to.

I want torrent (and other downloads) to run at full speed until anything else in the network requires bandwidth, then they should take a back seat. If I can get that working, I'm sure I can figure out prioritization for my other bits and bobs.

I assume you are using queue tree for this? If not, you should work towards that instead of simple queues.

In that case, the priorities doesn't really work at all for me. So the way I do it, the queue that torrents go in, gets a very low "Limit at" value, which is like 10% of line speed, and max value is at 98% line speed. Then the queue with interactive traffic in like browsing and streaming, you put the "Limit at" at 80% of line speed, and max value again at 98% line speed. This is a simplistic way of how I do mine, but it works much more effectively than hoping for priorities to work. I do a bit more advance stuff, but thats what you should start with to get what you need done. Once you also want to play games...that is where it becomes fun and you need to fine tune queue types ect.

 

[Nuke]

Some things to remember. You can't shape(prioritize) inbound traffic, only police(limit) it. Also inbound policing works for TCP traffic, not very well for UDP. As the traffic arrives at your router it will be dropped if it exceeds eg. 256kbps, but without TCP's congestion avoidance it will just drop perfectly good UDP traffic on the WAN side of your router. It will already have congested your ADSL line.
You can shape it outbound though. But I guess you do far more down than up.

Mikrotik does not support interleaving. On a slow line you may need it for low latency traffic like VoIP. The closest you can do on Mikrotik is to drop the MTU to 512, but that can have other strange effects....

For proper QoS you need control over both sides of your link, something you will never have on ADSL unfortunately.

 

[Messugga]

I assume you are using queue tree for this? If not, you should work towards that instead of simple queues.

In that case, the priorities doesn't really work at all for me. So the way I do it, the queue that torrents go in, gets a very low "Limit at" value, which is like 10% of line speed, and max value is at 98% line speed. Then the queue with interactive traffic in like browsing and streaming, you put the "Limit at" at 80% of line speed, and max value again at 98% line speed. This is a simplistic way of how I do mine, but it works much more effectively than hoping for priorities to work. I do a bit more advance stuff, but thats what you should start with to get what you need done. Once you also want to play games...that is where it becomes fun and you need to fine tune queue types ect.

Would you mind going into a bit of detail regarding how you flag your torrent traffic as such?