DhcpServer w/ PCC on Single Interface, without VLANS, Help?

RouterOS Forwarding Protocols
1

Ok Ive got Dual WAN, Ive got a dhcp server, all running on a single interface and I want to get load balancing going.

Ive got Two Static IP Adresses configured and operational on Eth2
ROS Ver 3.0 RB532a

Ive got internet through both static ips, and Ive got a route for each I can change between them simply by changing the distance number in winbox.

Im a total noob at this but I did google first, All the tuts ive read explain how to do this with multiple physical interfaces, but since no one likes too many cables laying around im going to give it a whack with one interface, or the other issue I have with tuts is that the syntax is wrong in the tutorials due to outdated routerOS.

PS I dont wanna do policy based load balaning, I mean I dont simply wanna route one group of machines to one gateway and another group of pcs to a diffferent one, I wanna load this bby up with real load balancing, hehe


any ideas how 2 pull this off?

2

This is not a good idea. You shouldn’t run multiple logical networks on the same physical/logical broadcast domain. At least use VLANs - and they appear as interfaces in RouterOS, abeitly logical ones. Means you can use a single physical cable as a router on a stick, though.

It might be possible - it’d just require some rewriting of the PCC template, for example. But don’t do things that are just plain bad ideas when there’s better options.

3

Ok well what if I ran the dhcp server on its own interface, could it still be done reasonably?

Or should I just drop this notion and shift to putting each static address and the dhcpserver all on Vlans?

4

I would use one VLAN per network. Your goal is to minimize physical interfaces - using VLANs takes your requirements down to just one physical interface. You can stack as many VLANs on that interface as you want - might as well make it clean and use three total.

5

Um, yeah, two problems

  1. It wont allow more than one Vlan on the interface

  2. when I switch the dhcpserver to this single Vlan, assign the address to it, and dhcpserver to it, it ceases to route the internet.

6

Sure it allows more than one VLAN on an interface. Post the configuration you tried.

7

oh I figured out why it wouldnt let me have more than one, I needed to change the Vlan ID number. ok so I have 3 vlans now

I assigned each static ip to its own vlan2 and vlan3, removed and readded the routes, I assigned the dhcpserver to vlan1 no internet from either gateway :frowning: , does this need some additional nat rules? Masquerade? or dp I need to reboot my gateways?

also, if I wanted to dump my config here how could I do that?

8

Do you have a VLAN capable switch? What is your physical layout? I was assuming you had existing knowledge about how VLANs work.

9

I just googled the switch and no vlan support,. FS-108 “VLAN Support - No” and no I am not used to using Vlans, :frowning: But this works, I have no visible problems networkiing and I can manually switch traffic between gateways by simply manipulating the routes. Just would be nice to have load balancing, So Im assuming that in order to achived PCC I will need to write some custom stuff into it, I see with their example they use interfaces, I would need to use IP ranges instead, bawww im lost.

heres my layout






IP adresses on my network are as follows:

ip routes on my system are as follows:

/ ip firewall nat (this is my only NAT rule)
add chain=srcnat out-interface=ether2 action=masquerade

PCC Example that needs to be modified before I can implement it:

/ ip firewall mangle
add chain=input in-interface=wlan1 action=mark-connection new-connection-mark=wlan1_conn <----can I set this to ether2?
add chain=input in-interface=wlan2 action=mark-connection new-connection-mark=wlan2_conn <----can I set this to ether2?
add chain=output connection-mark=wlan1_conn action=mark-routing new-routing-mark=to_wlan1 <----can I set this to ether2?
add chain=output connection-mark=wlan2_conn action=mark-routing new-routing-mark=to_wlan2 <----can I set this to ether2?
add chain=prerouting dst-address=10.111.0.0/24 action=accept in-interface=Local ← Local is not an acceptable interface so says routerOS
add chain=prerouting dst-address=10.112.0.0/24 action=accept in-interface=Local ← Local is not an acceptable interface so says routerOS
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses:2/0 \ <— No idea what this should be
action=mark-connection new-connection-mark=wlan1_conn passthrough=yes
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses:2/1 \ <— No idea what this should be
action=mark-connection new-connection-mark=wlan2_conn passthrough=yes
add chain=prerouting connection-mark=wlan1_conn in-interface=Local action=mark-routing new-routing-mark=to_wlan1 <----can I set this to ether2?
add chain=prerouting connection-mark=wlan2_conn in-interface=Local action=mark-routing new-routing-mark=to_wlan2 <----can I set this to ether2?