Hello, fellow forum users
I hope I am welcomed here, as I just got a used RB3011UiAS for free.
I have been trying to configure it but a few problems I have seen.
Firstly the fact that my devices do not get an internet facing ipv6 address., instead opting for a ::xxxx:xxxx:xxxx:xxxx and an fe80 local address, none of them facing the internet.
I have hopefully correctly set up the dhcp client as I do get a /56 prefix that shows up on the pool page as a prefix length of 64 and is dynamic.
I also setup a DHCP server from the pool to the bridge interface. I have tracerouted from the router and apparently it works but with a ton of packet loss
Additionally I upgraded the software to 7.16rc4 but my RouterBOARD shows that the current firmware is 7.16rc4 but the upgrade firmware is 3.41? It does not allow me to “upgrade”, apparently because its below the factory firmware of 6.46.8. The error it gives me is Couldn’t perform action - ERROR: can not change firmware to this version, please try newer one (1).
Also for some reason even though I have added a default route for my provider’s incoming telephony vlan on the dhcpclient option and the routes in the ip/routes menu do seem to include the ip I am trying to traceroute and it seems to take the right route but it never reaches anything
Post full config .. from terminal window execute /export filename=anynameyouwish, fetch resulting file, open it in your favourite text editor, redact any renaining srbsitivevdara (serial number, passwords, etc.) and post it inside [__code] [/code] tag pair.
Also post output of /system/routerboard/print for us to see what’s up with firmware version.
Is there perhaps a .fwf file lying around in files area? It’s either this or a bug in firmware handling in 7.16rc4 … I don’t have any other explanation for the routerboard anomaly.
In any case, having “current firmware” version same as running ROS version js a good sign and you should not go overboard to "fix"it.
PPPoE is a bit nifty for IPv6. One thing is that you don’t need to request address from DHCPv6 server, only prefix. (Doesn’t hurt requesting one, but it’s useless)
Another thing is that DHCPv6 server on ROS is not very useful, it can’t hand out addresses (only prefixes). Alas, in IPv6 there are Router Advertisements, which announce correct prefix to clienrs on same L2 subnet (and they select their IPv6 address using SLAAC). So you may disable DHCPv6 server until you determine that it’s actually necessary in your setup.
I don’t see assignment of IPv6 address to LAN interface (which is bridge). You do it like this:
If IPv6 doesn’t start behaving afterwards, post output of
/ipv6/address/print
/ipv6/route/print
(obfuscate first 4-letter group of public addresses … but in a meaningful way … e.g. replace it with xxxx or yyyy or zzzz snd use sane repkacement string on all addresses where original value is the same … helps determining is things look right or wrong)
So apparently that fixed it as I observed, I was also able to disable the DHCPv6 server. Now the only non operational thing is the VOIP telephony over the 837 vlan. Traceroutes do work to the end server until a certain point, similar to other equipment but SIP packets do not work and are not seen by the packet sniffer on the vlan837 interface, here are routes and addresses for such interfaces. Setting a classless or default route result to same behavior even if I tried to use it as my main wan interface routing all traffic to it.
[admin@MikroTik] > /ip/route/print
Flags: D - DYNAMIC; A - ACTIVE; c - CONNECT, v - VPN
Columns: DST-ADDRESS, GATEWAY, DISTANCE
DST-ADDRESS GATEWAY DISTANCE
DAv 0.0.0.0/0 wan 1
DAc 10.126.0.0/17 voip837 0
DAc 192.168.1.0/24 bridge 0
DAc 213.16.246.21/32 wan 0
[admin@MikroTik] > /ip/address/print
Flags: D - DYNAMIC
Columns: ADDRESS, NETWORK, INTERFACE
# ADDRESS NETWORK INTERFACE
;;; defconf
0 192.168.1.1/24 192.168.1.0 bridge
1 D 10.126.0.241/17 10.126.0.0 voip837
2 D validpublicipv4/32 213.16.246.21 wan
Server I am trying to reach is at 10.50.131.150 and should be accessed over the voip837 interface by bridge clients
10.50.131.150 does not fit into 10.126.0.0/17 (this one covers range 10.126.0.1 - 10.126.127.254) but you don’t have any specific router which would match better than default via pppoe internet interface.
You can try to add a route towards 10.50.131.150. Ideally you’d use some gateway address (which hapoens to fall into said range). Did your ISP give you any instructions about VoIP settings?
[admin@MikroTik] > /ip/route/print
Flags: D - DYNAMIC; A - ACTIVE; c - CONNECT, d - DHCP, v - VPN; + - ECMP
Columns: DST-ADDRESS, GATEWAY, DISTANCE
DST-ADDRESS GATEWAY DISTANCE
DAv+ 0.0.0.0/0 wan 1
DAd+ 0.0.0.0/0 10.126.0.1 1
DAd 10.23.52.11/32 10.126.0.1 1
DAd 10.24.52.11/32 10.126.0.1 1
DAd 10.50.131.150/32 10.126.0.1 1
DAc 10.126.0.0/17 voip837 0
DAc 192.168.1.0/24 bridge 0
DAc 213.16.246.21/32 wan 0
[admin@MikroTik] >
However when it renews it switches to the voip837 interface so the internet becomes inaccessible?
Additionally sip packets still dont get forwarded to the interface
(ftr here is the official documentation whatever is in greek is usually parameters and define what is sent by them to you https://nova.gr/upload/editor/pdf-documents/diepafes/byod-final-_13-2.pdf )
It seems that DHCP parameters are not meant to be received from both VLANs by the same routing instance.
So now the question: what’s the intended layout of your LAN devices (including VoIP devices)?
I don’t have VoIP, but my ISP delivers IPTV over tagged and multicast. It is possible to terminate that on router and deliver multicast streams to LAN devices … but for me it was much easier to switch the IPTV into LAN infrastructure (retaining VLAN ID) for IPTV boxes to get multicasts and only replace the internet part with one of VLANs provided by my router. Which works great as IPTV set-top boxes expect to access multicasts via tagged ethernet and interbet via untagged ethernet.
And the related config on my router is more or less the same as what ISP-provided router does.
What I know has worked is SIP ALG and a custom route with a dynamic gateway, maybe using the /17 allocation and giving it out over dhcp could work but you would need to dynamically change the lease period since the IPs expire every 530 seconds, as for the layout probably I would want a pbx accessible by lan interface and to setup a few wireguard clients for remote connection into the lan generally to allow not specially configured clients to run softphones and the such. Ideally all clients could get a SIP registration for debugging purposes