Problem with guest wifi on Technicolor/Thomson TG582n

I replaced my becoming-flakey Netgear with the current PlusNet default TG582n for my fibre b/b, and I'm generally pleased with it.However, the Netgear had an isolated guest wifi option which I liked, so I tried to replicate this on the TG582n. This was done largely with something like (deduced from the ever-helpful telnet commands site often linked from here):

Now, I thought this was working, but after a day or so it became apparent that it had made the normal wifi connection exceedingly flakey: our wireless devices were working briefly, then dropping out momentarily, before reconnecting and working again. As soon as I disabled the new guest I/F, it all became reliable again.Can anyone explain why? Is it something to do with the following output?

Re: Problem with guest wifi on Technicolor/Thomson TG582n

The first number is the radio, there's only one radio so it's always "0".The second number is the SSID number, the main station is "0" any additional virtual stations are 1, 2 or 3.The numbers are correct but the lack of security is worrying.Have you seen this:http://npr.me.uk/mssid.htmlOr if you wish the guest wireless network to be isolated from the main network:http://npr.me.uk/advdmz.html

Re: Problem with guest wifi on Technicolor/Thomson TG582n

Does this also apply to the TG582n as identified in the OP? This page says "Multiple SSID's on a Thomson TG587n", it references this not being applicable to 585v7 but makes no claims for the 582n. If it is applicable, is that valid for all 582n? (W/wo USB interface).

Re: Problem with guest wifi on Technicolor/Thomson TG582n

@npr - yes, thanks, that's the site to which I referred (but didn't have a link to hand).I read a few of the pages, and used the multiple SSID page to achieve what I did (including the extra “bugfix” bridge setup which I found I needed). The DMZ config. is way OTT for my needs (although I suppose I've effectively got that with my internal Linux firewall configs anyway).While a great resource, the main issue I have with that site is that it's more about recipes than documentation, so while there are a few comments it doesn't really explain in enough detail what's being achieved (& I like to think I know a bit about networking and firewalls).So yes, that's what I did, it just made my connection really flakey. I may try it again with simple WEP on the guest connection (like @RPMozley, it's also to allow NDSs to connect while I keep WPA2 on the main connection), in case the wireless devices are being too eager to jump between available SSIDs and see the open guest as a good bet.

Re: Problem with guest wifi on Technicolor/Thomson TG582n

This page says "Multiple SSID's on a Thomson TG587n", it references this not being applicable to 585v7 but makes no claims for the 582n.

The 582n was not out when I wrote that web page. Thing's move on I haven't tested multiple SSID on the tg582n, but the commands are supported so I see no reason for it to not work.@ fnxweb,I assume the NDS doesn't support wireless "n". Some old wireless g devices can cause problem with the routers wireless, try disabling wireless n in the router. You'll find the command in the telnet page of that site.

Re: Problem with guest wifi on Technicolor/Thomson TG582n

I assume the NDS doesn't support wireless "n". Some old wireless g devices can cause problem with the routers wireless, try disabling wireless n in the router. You'll find the command in the telnet page of that site.

Heh, I haven't even tried the NDSs yet; the connection problems were with a number of (n-capable) Android devices, and also possibly a couple of standalone wireless security cameras (which were playing up and now aren't, the subject of a future post).

Re: Problem with guest wifi on Technicolor/Thomson TG582n

I added the guest back in, using WEP this time. It seemed OK initially, but soon degraded to unusable (my phone kept dropping connection to the main SSID, and I lost access to both wireless webcams).I removed it again and all was fixed. Guess I'm just out of luck :-(

Re: Problem with guest wifi on Technicolor/Thomson TG582n

Hi thereI've followed this guide for my 582n, and it's worked great. My only problem is that the guest wifi network can still see files on my shared WD Live drive.I usedapisolation = enabledbut that doesn't seem to have done the trick. Am I missing something?

Re: Problem with guest wifi on Technicolor/Thomson TG582n

You need to use this method to isolate your main LAN.http://npr.me.uk/advdmz.htmlAlternatively you should be able to block access to the shared drive using the routers firewall.Try a firewall rule allowing access to the share from whichever IP addresses you wish to allow.Followed by a rule blocking access to the share from LAN.You may need to experiment a bit but something along those lines should work.

Re: Problem with guest wifi on Technicolor/Thomson TG582n

Hi nprThanks for the reply and your excellent guide.Just so I understand what I'm doing - the DMZ should sit separate from everything else in terms of access, so if my existing Wifi is 'SSID1', and my guest wifi is 'GuestWifi', then when I run 'eth bridge vlan iflist' I should see the ethport with my WD Live NAS in default, and the 'GuestWifi' in the DMZ?

Re: Problem with guest wifi on Technicolor/Thomson TG582n

It all depends on the options you chose from that guide.If you just chose the wifi option (d) then nothing connected to a ethernet port or on the original wireless ssid can be accessed from the new (dmz) wifi.ie "eth bridge vlan iflist" will then only show:-2 dmz OBC, Wdmz*Good luck, please let us know how you get on.

you need:Vid Name Bridge interfaces (* = untagged)--- ---- --------------------------------1 default OBC*, ethport1*, ethport2*, ethport3*, ethport4*, WLAN*2 dmz OBC, Wdmz*Note:Wdmz was the eth interface name first used in the instructions to create the dnz ssid. You can use a different name but it need to be consistent through out.You may be best doing a factory reset and starting again.

Re: Problem with guest wifi on Technicolor/Thomson TG582n

OK - I think I managed to figure out what I've done wrong - now I see the correct items in the list.One thing that's gone wrong now is that I can only get 'Limited access' on my virtual SSID - nearly there!