Hi,
I’ve just bought a RB2011UiAS-2HnD-IN.
For my home wired configuration, I need to put the WAN ethernet cable (come from an Ubiquiti PoE Antenna provides me internet) in ethernet port 10, to power by PoE the antenna.
In my router default wan port is ether1. So how can I change this configuration using RouterOS graphic interface?
Thanks in advance.
Kind regards
Giuseppe
In RouterOS there is no such thing as “WAN” port per se. It is just a port that has DHCP-client enabled and firewall rules protect it. So if you would go to the DHCP client menu and change the interface there, then go to “firewall filter” and change interface there also, I think that would be all.
Yes, I know there isn’t a WAN port, I wrote WAN for semplicity.
However, in Interface tab in routerOS, ether1 is described as “Ether1-gateway” so I thougth it’s default port to connect internet, isn’t it?
Maybe changing configuration as you described, will change it?
Anyway, thanks for your replay, I will try this configuration.
Bye
You probably also would need to remove the new port from any bride/master-port configuration
But in Quick config TAB … I simply CANT setup Wan port to ether10
only ether1 and sfp1 port is active to setup
router os v 6.34
That is something that just about everybody faces, yet I can not find logical “How to…”
Anybody?
sebus
What exactly are you looking for? Read what normis and Rudios have written above- that’s about all you need to do.
Please note that this clearly goes beyond the “basic setup” thing, so there’s no chance you can do this via the QuickSet window.
All I need to do is make “WAN” port being Eth9.
There is NO need to waste Gig port for WAN connection (that is at most 72Mb) - hence this should be easily user changeable!
So I can change DHCP client/NAT/FW rules/neighbour discovery/master on Eth 9, but in QuickSet window there is still ONLY Eth1/SFP1 as only options.
Default config (from /export) does NOT have anything related to Eth1 as WAN port
sebus
So what?
Use Winbox.
As I said above, you will have to forget about QuickSet forever (and configure you router using the regular means from now on) if you need to use another port as your WAN connection.
In the default configuration of your device ether9 is a slave interface with master-port set set ether6, so the first thing you have to do is to set master-port to none for ether9 (while there you can also consider renaming ether9 to ether9-gateway or whatever for clarity). Having done that, you can proceed with editing you /ip firewall filter, /ip firewall nat, /ip dhcp-client, etc.
I am sorry, but if that is the case then it is a bug (at least in interface!)
I do know what to change, but none of the changes do get reflected in QuickSet (which obviously is wrong)
Again, WAN port swap should be really basic step, as most users would need it (or change the defaults in firmware)
EDIT:
Is following correct (as per this):
ether1it isn’t wired to the switch chip. Therefore it can’t be switched with ether2-ether5, unless a bridge port is manually configured
That would explain why Gig port is wasted for WAN…
No, it is not a bug, it is a limitation in the feature set. Quickset is designed to do a very limited set of simple alterations to a standard configuration for the benefit of people who understand little if anything about routing. What you want to do is not in the"Simple" class of alterations that the tool was conceived to accommodate.
To do what you want, you can use either Winbox for Webfig, both of which give you full control over the internals of the router.
Sent from my iPhone using Tapatalk
Swapping wan port can definitely be a bit more complicated than you believe. Also imagine that the whole group of ports 6-10 share one single 100mbit line to cpu. Maybe it is not wasting to use one of gigabits as wan even it is 70 mbits.
Your lack of knowledge is not a bug of a system you refused to understand.
In fairness, he did want to use the POE out feature on port 10. still, this is basically a design quibble over what features he thinks should have been included in Quickset versus what features the designers thought should be included.
Sent from my iPhone using Tapatalk
@jarda, how can you asses my knowledge? From a single question that there is no clear answer to? Just use search & see how many people asked same question over the years…
To me it is a bug/bad design, no matter what you think.
Could you also consider that is the user that decides what is or not “waste” in their environment?
Swapping ports is not really difficult. I get paid for doing it…
a limitation in the feature set = bad software design
Not always, as a glance at Microsoft word will bear out. Sometimes, limits to a features set are good design when the purpose of the interface is to enable an untrained user (such as a person who buys a router for his home use) to make simple changes without shooting himself in the foot.
You have two professional grade tools which allow you to do exactly what it is you want to do. It’s not necessarily advantageous to add that function to the watered-down interface designed for novices.
Sent from my iPhone using Tapatalk
They are not supposed to. QuickSet is a one-way thing. You cannot expect anything not directly supported by QuickSet to be reflected in QuickSet (when you change that elsewhere). In general, QuickSet is a simple way for an inexperienced user to quickly apply some typical configuration to his/her device. Once deviated from what QuickSet provides, you cannot expect to be able to easily go back.
For RB2011 it’s not. It is correct, however, for some other (mostly outdated/discontinued) devices. More info here.
Good design would be to just show what the user chose to be the WAN IF user did make the change.
Really simple. It would be good for either condition then. Or disable QuickSet IF user made changes elsewhere.
As it is now, it simply looks confusing
Let me repeat this again (if you have not understood that yet): there is no such thing as a WAN port in general. I used to use a good-old-tiny RB750GL (which is also considered a SOHO-class device) for inter-office routing between 5 semi-isolated networks. All 5 ports were independent (i.e. no switching) and none of them was WAN-facing port.
Calling some port “WAN port” is just a matter of convenience. Changing what port QuickSet considers WAN is not withing the scope of “basic setup”. A more experienced users do not usually call any port “WAN port”.
There should not be any quickset at all… Even it is well meaned, it provocates such users to overestimate their expectations and then to be disappointed.