First of all, I’m a completely newbie to networks so please do not shoot me
The reason for asking is that the system is delivered to me from a provider that claim they do not support hotspot.
I have a WLAN using RB600A and two wlan zones up running and everything is good. But now I want to add HOTSPOT.
I have followed the Hotspot server setup on the Wiki, but when I get to the last step I get the following error message: setup failed to configure ip address: failed to add IP address: already have such address (6)
The DNS that I put in is the DNS that I can see doing a “ipconfig /all” on a computer connected to the wlan.
The hotspot interface has two ip subnets assigned. Is this a bridge interface? Which physical interfaces are assigned to it? Which interface is your wan interface? What is ‘530’?
194.69.219.144/28 530 reachable
We would have to see your config to give you much information, but based off of the error, I’m guessing the IP you are trying to add to the hotspot already exists on an interface. Check your IP addresses and move the IP you are trying to add to the hotspot to the hotspot interface if it isn’t there already.
It helps! I presume that the hotspot is assigned to the bridge bridgelienter. Which interfaces are assigned to that interface? How is the ip/subnet assigned?
Yes the plan was to start by setting up a hotspot on sone1 and get that to work before starting with sone2 but for the moment no hotspot is defined due to the error I get running the hotspot wizard.
The “Bridgeklienter” (or Bridge clients in English) is the bridge
What physical interfaces are assigned to the bridge? If there aren’t any physical interfaces assigned to a bridge it will not work.
I see that there is already an IP assigned to sone1, so if you are trying to add the same IP address again, that’s where the error is coming from. Try deleting it and going through the setup again.
After playing around with the system I saw that the ether1 was having the same network addresses as I was trying to assign to the hotspot. I’m not sure what ether1 is or if it is just a default interface that can be deleted.
Well anyhow I tried one more time now setting the network pool to 192.168.89.1/24 instead and now the wizard went the whole way and no error messages.
So now I have a hotspot server showing up but it’s red and marked as Invalid.
The same with DHCP servers it’s there but marked as Invalid.
You can view what physical interfaces are assigned to the bridge by going to /interface bridge port export.
Since you have apparently used the the wizard before or you are trying to reuse what has already been set up, that is where the errors are coming in. The wizard is trying to remake stuff that already exists with the same information/names and that is where your errors happen.
At this point:
1.) You can wipe the config and start over and see what you can do. If it’s live and people are using it and relying on it, I would not recommend this.
2.) Run export from the top level of the CLI and read over your current config and get a feel for it and see what you can change and move around to get a feel for the MikroTik and how it works. Once again if it’s live and people are using it and relying on it, I would not recommend making too many changes.
3.) Get a test box set up in your office run through the wizards and take a look at the config after they have been run, and compare it to your working config and see what changes you need to make.
All the wizards do is run built in scripts that write the relevant configuration parts for you based off of the information you feed them. You don’t need to use them to get these things set up if you know what it writes and where it writes it, you can do it manually.
This is what I discovered after some time too. The wizards puts in information in a lot of places. I have to admit that I managed to destroy the settings so totally that I had to contact the company that sold us this solution and get them to reset everything back to the start again. No, I had not taken a local backup before I started I have now
This is exactly why I was so stressed earlier in the week. The system is going live today…
I have totally abounded the thought of using hotspot for the time being. I’ll have to relay on the wpa2 code for giving people access to the network and then just change this quite often.
The hotspot functionality has to wait until the end of the camping season ie a couple of months. Then I’ll try again.
…in the mean time I’ll start to read the documentation regarding queuing and see if I can get one specific IP-address to have pri1 while the rest have pri8, but that is another thread…
I would recommend picking up a 450 for a 750 to use as a test box, the 450 is nice since it has a console port so you can always get into it if you screw up the config royally. Either of these boxes will have more than enough horsepower to deal with anything you throw at them in the office, and are cheap enough for it to be a good investment. This way you can do whatever you want to it in a lab environment and figure most everything out without breaking anything critical, and save you a lot of stress and lost hair .
Another thing you may want to consider is sending yourself a backup on a schedule with the router. These come in very handy to get something back up and running when it breaks. You’ll need to set up the e-mail tool to bounce the e-mails off of a relay server, but that’s not very hard.
add comment="" disabled=no interval=1w name=sched_backup on-event=backup policy=ftp,reboot,read,write,policy,test,winbox,password,sniff,sensitive start-date=jan/01/1970 \
start-time=07:30:00
add name=backup policy=ftp,reboot,read,write,policy,test,winbox,password,sniff,sensitive source="/export file=([/system identity get name] . \"-\" . \\\
\n[:pick [/system clock get date] 7 11] . [:pick [/system clock get date] 0 3] . [:pick [/system clock get date] 4 6]); \\\
\n/tool e-mail send to=\"backups@domain.com\" subject=([/system identity get name] . \" Backup \" . \\\
\n[/system clock get date]) file=([/system identity get name] . \"-\" . [:pick [/system clock get date] 7 11] . \\\
\n[:pick [/system clock get date] 0 3] . [:pick [/system clock get date] 4 6] . \".rsc\"); :delay 10; \\\
\n/file rem [/file find name=([/system identity get name] . \"-\" . [:pick [/system clock get date] 7 11] . \\\
\n[:pick [/system clock get date] 0 3] . [:pick [/system clock get date] 4 6] . \".rsc\")]; \\\
\n:log info (\"System Backup emailed at \" . [/sys cl get time] . \" \" . [/sys cl get date])"
If I was in to networking I would definitely look into this, but the truth is I’m just a user that was given the responsibility to get the WLAN to work a week ago since the company that has delivered the system claims that they do not give any support on hotspot/wlan. But it’s always fun to try to learn something new
Hey, hey, hey take it easy remember I’m a total newbie
I have made sure that I have several copies of the existing setup and I’m not going to play around with anything more (- I think -) until most customers disappear in a two months time.
…but it would be interesting to know how I set up the email…
It’s very easy to set up. Go to Tools and E-mail in Winbox or the CLI and set up your server, port number is almost always port 25, the From field can be from anything you want it to be, and if your relay server requires a user name and pass to send e-mails enter in those. After that you can send out e-mails.
You can also specify these options from the CLI when you are sending out the e-mail instead of having it pre-setup.
I have now 
