maxpower

Might be a better choice

2 hours ago, CrossBones said:

Thanks, why do I need to change subnet on old router. Why not just disconnect wifi on one router and plug it to new router?

 

 

You could plug in another router and use as an access point only.

What is the distribution arrangement from Sinet and model number of existing TP-Link box. Are you connected directly to a fiber terminator via Ethernet or behind some other Sinet distribution.

I can confirm that many TOT users report port 80 as closed. Hundreds of security DVR's are connected to TOT and a colleague is currently using port 21 on a TOT account so other ports are open.

Why don't you do the basics and ask TOT which ports are open on your account before someone adds relocate to the list of suggestions.

My old TOT service closed Jan 2018 had port 80 open but I know for sure they were considering moves to close 80 service wide. AIS only has limited ports to get over 2x NAT no 80. Not sure about 3BB or True.

Why the IP drama when basic shared hosting is so cheap and most offer free ssl cert ready to go.
 

17 minutes ago, Basil B said:

About the only thing Hardline brexiteers can quote, who keep shouting we won so shutup... we speak for everybody...

 

Lets have have another referendum, because public opinion has shifted and I am sure this time the result will be a clear majority...  come on what are you brexiteers scared of???

That's on the B Side called "THE NEVER ENDING VOTE" also two nice songs on the album "BAD LOSERS UNITE" and "LETS ALL GET ALONG DREAMS"

Lets play it again eh.

16 minutes ago, Pib said:

The DHCP on the "new" model Playbox will stay turned off if just going from standby to on, on to standby, etc.  But if there is a power outage (even very brief) or if physically turning the Playbox's power switch off and on, the DHCP setting will turn on by default and a person needs to go into the settings and turn it off if he don't want to have a DHCP IP for some reason .  This is how it works on the new model boxes with the neutered firmware (i.e., only runs AIS Play, doesn't allow running of other apps like Youtube, Kodi etc)...or at least it works that way on my two new model boxes and I think SooKee confirmed the same for his box.

If your box switches DHCP back on during power cycle then its game over and you are in the hands of the AIS nanny who has destroyed a basic network setting most likely to keep DHCP away from the support desk. Why dont they do it properly and remove it from the menu?

12 minutes ago, SooKee said:

So, problem came back today.

 

At the router, DHCP range set from 100 - 200.  Playbox has a reserved IP address ending 10.  Lease time at the original 86400.

 

Went into the router again, reset the DHCP range to 2 - 254 so the reserved IP will be within the DHCP range.  Will see how that goes.  If it crops up again will revert to a two day lease time.

Read my last post #60

Old work colleague in Bangkok tells me his AIS Box holds DHCP off settings without problems but you guys tell me yours will not. Strange.

Just a reminder how two different TVBoxes would operate and why TVBox2 with DHCP off will not show in a router lease table.

TVBox1 - DHCP On

TVBox1 owner plugs him into ethernet and he starts broadcasting DHCPDISCOVER on the network waiting for a server to make an offer. Router sends an offer and TVBox1 quickly sends back a request. Router then sends back a packet complete with network info and lease time. TVBox1 now has enough details to play on the network.

The ip address given to TVBox1 would normally come from routers pool but if router has a special reservation for TVBox1 it will send the reserved ip instead. Smart stuff, its kind of like a static ip but has a nasty lease agreement attached that we need to request and keep up to date.

TVBox2 DHCP - Off - network settings local set

TVBox2 owner plugs him into Ethernet and he starts using the network immediately because settings are stored locally no need to ask router.

1 hour ago, Pib said:

@maxpower

  Will you post a snapshot from you router of the "lease time" of one of you devices set to a static IP.   Would like to see how it displays lease time.  

I am at work now but can give snap from a local device displaying exact same info as my home router would. It has one mobile connected from DHCP and three static ip devices on LAN which we cant see because the static devices do not require a lease from DHCP. 

Snap from router DHCP lease table showing device that have been given leases from the DHCP server. Static devices with DHCP off are not shown. If we had a device with reserved ip in DHCP it would be shown also.

47 minutes ago, Pib said:

Below from RMerlin himself...the guy who programs the renowned Merlin firmware for some Asus router models  His post is basically talking some of the confusion caused by how different network IT equipment makers and so called experts refer to the various types of IPs (i.e., static, reserved, manual, dynamic, etc).  I clearly noticed this in my googling/youtubing over the last week or so where "static" IP seemed to be a loosely used term...possibly incorrectly referenced in many cases.  

 

https://www.snbforums.com/threads/dhcp-server-stops-handing-out-ips-for-wireless.40751/

 

My understanding of a "static" IP is one you set on the "client's end," repeat the client's end, like you can do in Android phone or on a Windows computer where you can select either a DCHP IP or Static IP.  

 

If you are setting an IP on the "router's end," repeat, the router's end you are really just manually reserving an IP.  And on Asus routers you can manually reserve an IP either inside or outside the DHCP scope. 

 

RMerlin recommends reserving IPs "within" the DHCP's scope....he did't explain why but I'm sure he has good reasons.  With that being said, my Playboxes are now set on the router's end to IPs "outside" the DHCP scope....so is SooKee's as of today.  This goes against RMerlin's recommendation, however, both my Playboxes are working fine so far for the last few days I've had them set this way.

 

Early testing with IPs manually set "within" the DHCP didn't help the problem for me or SooKee, but that was before we changed the lease time which appears to have fixed/cleared the problem. 

 

As mentioned in an earlier post and my testing this week my gut now tells me the Playbox will work fine with an IP within the router's DHCP scope whether manually set or dynamics set since the lease time change seemed to have cleared the problem.  At some point in the near future I'll probably put both Playbox IPs back within the DHCP scope and let them be assigned dynamically just to see if the problem comes back.

 

Maybe now some of what I have been saying makes sense.

Its always best to follow a strict set of rules with networking because it makes future troubleshooting and communication with others much easier. This also applies to basic home networking.

Think of a small network setup by Joe. Bob arrives to take over and Joe tells Bob that he has set DHCP range to xxx xxx and reserved a couple of ip addresses in  DHCP for some stuff.

Because they follow rules, Bob knows that he can safely use ip's outside of the DHCP range without worrying about the router grabbing one for some DHCP variant  built into its firmware.

As explained previously, only my mobile stuff uses DHCP on my network, the rest is Ethernet static.

I am using a Cisco enterprise router which has the usual router functions including reservation in the DHCP range which I dont use.

My DHCP has a reserved range and the rest is free for static use outside of the router.

From the interface I can view devices which have been given leases via DHCP and connected devices that have not been issued a lease.

If the router is turned off I can access the server, printer and all devices with static ip's.

Again, if an Android device cant run static with DHCP off then its in the trash or get it sorted by the vendor.
 

17 minutes ago, SooKee said:

Yes. Everything is set at the router. I set nothing on devices.

So when one of your devices makes a DHCP request for network info it gets given a fixed IP out of DHCP range along with a lease. Interesting arrangement.

25 minutes ago, Pib said:

Could be.   Just saying what I set up....basically same-same as what Sookee just setup except he chose a different scope range of .100 to .200 for his DHCP scope where I used .21 to 254.  And both of us manually entered the a Playbox IP for use outside (below) the DHCP scope.  

 

As mentioned earlier the IPs set outside the DHCP scope are still getting the same lease time as devices within the DHCP lease.  The IPs outside the DHCP scope do not get indefinite lease times....they are getting 24 hour lease times since the DHCP lease time is set to 24 hours.

 

Personally I think it basically the same as leaving the DHCP scope set to .2 thru .254 and manually selecting in IP for a device....or what is also called a Reservation.   My gut tells me if I set the scope back to .2 thru .254 and whether I manually selected IP for my Playboxes or not the internet connection problem would not return.   

 

But since I can't test various IP settings "willy-nilly" because of other household members using the home internet most of the time and my tests possibly impacting them I need to wait to those times when I won't impact them....give me time to right things if I break something with my testing.

 

Actually I found a silver lining in this issue as this week I spend a good amount of time googling/youtubing the IP assignment and Lease Time.  Been interesting....learned a lot....now more dangerous.

This is where networks become confused because a lease is given to a DHCP request which should only give out ip's within its range.

Like I have said before, my home devices have a static ip's and the router has no business using them because it has been told the range it can use.

If I login to my router and try to set a reserved IP out of DHCP limit it will show error because it does not want a collision with something outside of its range.

34 minutes ago, SooKee said:

1) Set the DHCP range from 100 - 200

2) Assigned all devices with static IP with IP addresses to below 100

3) Reset lease time to 86400

Your description might clear up some confusion here.

You have set a DHCP range from 100 - 200 in the router.

You are setting static ips below 100 at the router using MAC address correct?

If not, how and where are you setting static ip's below 100.
 

4 hours ago, Pib said:

So, now I have one PB operating within the DHCP server scope like it has for the longest time and also having the intermittent but annoying no internet connection frequently.  The other PB set to an IP address outside of the DHCP scope.  And now both operating with a 1 day lease time again because the lease time applies to all types of IP addresses the router issues out....whether you want to call the IP address in use a  Dynamic, Static, Reserved, etc.  Plus you can actually see the lease time remaining on all IPs issued out by the routers.  Ran this test for 2 days and still not getting any PB no internet connection message....all is still good.

1 hour ago, Pib said:

yeap, the two PBs are not operating outside the DHCP scope.  I changed the DHCP scope from .2 to .254 to .21 to .254.  Then I assigned the PBs IPs within the left over .2 to .20 range....assigned from the router end.   All done on the router end....nothing done on the PB end. 

Unless you only have more than one set of scope rules DHCP can only issue from the .21 - .254 range. If a DHCP request is being dished up an ip below .21 then you have more than one set of scope rules in operation. 

And again. Static IP's outside of router scope are free from any lease. 

1 hour ago, Pib said:

So, now I have one PB operating within the DHCP server scope like it has for the longest time and also having the intermittent but annoying no internet connection frequently.  The other PB set to an IP address outside of the DHCP scope.  And now both operating with a 1 day lease time again because the lease time applies to all types of IP addresses the router issues out....whether you want to call the IP address in use a  Dynamic, Static, Reserved, etc.  Plus you can actually see the lease time remaining on all IPs issued out by the routers.  Ran this test for 2 days and still not getting any PB no internet connection message....all is still good.

How can the Playbox with an IP outside of the DHCP scope be operating with a 1 day lease? If its not within DHCP scope DHCP did not issue the IP and give it lease time.

Unless of course you have the facility to issue an IP outside of the DHCP scope and include it in the least time setting. 

1 hour ago, Jingthing said:

Yes just noticed the same thing.

Also trying to do searches on things I know should exist and getting no results. 

It's obviously a large part of the database is just not there now. No, I'm not talking about very old stuff.

Should we expect this data to be restored or is it gone forever?

If you are using the thaivisa search system you must appreciate that most forums have limited resources available for searching.

Using Googles complex algorithms and resources to search thaivisa will most likely dish up more accurate and relevant results.

Try entering the following in a Google search box and it should return a Thaivisa post from 2002 in the top results along with some Lonely Planet relevance.

site:thaivisa.com Reading the visa section in my Lonely Planet

1 hour ago, Crossy said:

All the bits were "in stock" in the assorted stuff box (never throw anything away). The bolt next to the MOVs is blocking up a hole which I thought was a bit big to maintain integrity should the MOVs fail.

You can use the same method to build a whole house protection box using higher rated MOVS. Maybe include gas arrestors and spark gaps to make a level one box.

1 hour ago, Pib said:

The AiS Playbox has firmware developed/"modified" by AIS.   it's no longer a typical Android box. 

Locking down a Android device is quite understandable as it takes a load off support desks and helps with security. AIS  have most likely screwed up the network routines while attempting to idiot proof the device but I cant believe a developer would be foolish enough to force DHCP on at every boot up. 

If its a pay TV system I would keep on at AIS until the annoying network problem was resolved.

20 hours ago, Pib said:

Regarding the static/reserved IP subject, last night when I spent a couple hours googling and reviewing youtubes on IP addresses with focus on "DHCP, Static, and Lease Time" it seemed a lot of variation existed in how the a "static" IP was setup....and it varied depending on the type of "DHCP or router" you were using....to include the age of the device.  Seems the new devices had simplified the setting up of an static IP.

Static is static now lets turn off DHCP and its so called static reservation. No, lets go the full hog and turn off the router. 

DHCP servers are just a convenient way to dish out network info and addresses on demand nothing more. DHCP ip reservation is a convenient add on feature.

Our workshops gateway router DHCP is turned off, wirless devices are dished up address from a pool somewhere else.

I can turn off my home router and continue to use the network with all devices talking to each other including the media server. This is because they are all static addressed and simply play along through a common switch. There is no internet of course because routers gateway is turned off. None of my static devices gives a rats ass about the routers DHCP or it leases.

The Android box which I rarely use has DHCP turned off and just powers up using its static settings without fail. If I factory reset the Android box then I would of course need to give it the static network settings again. 

Standard test procedure when a device fails to handle DHCP properly is to turn off DHCP and go static. The results of the test will then move the procedure in simple logical steps.

The Crunch

If after turning DHCP off your device turns it back on during power cycle then it has a serious firmware error that needs sorting by the vendor. The only time DHCP should be switch to default is at settings or hard reset.

Why would you waste time fighting with a device that cant keep basic settings during power cycle or even worse requires a hard rest to continue operating?

PS

I see member Fruit Trader has indicated a similar 'playbox' device has DHCP turned off and possibly holds it static network settings without problem. Maybe a clue to some having faulty devices or a device variant with bad firmware. 

Old photo from BKK workshops showing switched Thai sockets mounted on sealed metal box containing a bunch of L-N L-E N-E connected MOVS and mains filter. No thermal protection required in this metal enclosure.

36 minutes ago, Crossy said:

I'm persuaded ????

 

Since we probably don't want to do this, do you have a recommendation for a suitable thermal fuse that can be sandwiched between two 20mm MOVs? 

 

Ideally readily available here, if not then AliExpress or the like.

 

EDIT Something like this? https://www.aliexpress.com/item/TF-Thermal-Fuse-10A-250V-Temperature-65C-85C-100C-105C-100C-113C-120C-130C-152C-165C/32893092186.html

 

 

The 65C units would likely do the trick if the enclosure isn't getting too warm in operation. At 14 cents a pop we probably should be doing this.

 

Is it worth glueing the fuse to the MOV? 

 

 

I have custom MOV/GAS arrestor boards on my home electronics which have 80 deg C 10 Amp one shot thermal fuses near to the MOV's

These axial lead thermal fuses are assailable from Eleement14, RS, Ebay, Ali and good electronic component stores.

Best to crimp tails on thermal fuses as soldering requires heat sink on the leads. 

19 hours ago, Crossy said:

That said, these things are all over the place including in "surge arresting" power boards and plug-in arrestors. None of these that I've seen have any form of protection against the MOV going short, so one assumes they just catch fire ???? (I've never seen one go like that).

Self extinguishing materials and thermal fuse protection with indication are common in devices that employ MOV's. Din rail style surge modules usually include a spring loaded thermal safety link that disconnects the device.
UL1449 sets a safety and performance standard that many manufacturers follow.

19 hours ago, Crossy said:

Of course, if you do add a fuse, you don't know if the protection has failed unless the fuse also cuts the power to the outlet.

Fuse or no fuse how would you know if a MOV hidden inside an enclosure has failed. If the thermal fuse has activated there is usually signs of burning around the MOV. But of course you could just leave it to the smoke and flames to provide fail indication.

1 hour ago, Pib said:

Yes, but even with a static IP a lease time is still assigned (the best I can figure out from googling and youtubing "lease time" use for a static or dynamically assigned IP)  in the communications between the client and router (DHCP Server).  It's just when the lease is renewed for a static IP, the IP address will "absolutely always" stay the same whereas with a DHCP IP Address "might" change.  

 

For a static IP it's like the lease time setting means nothing, but a lease time is still issued.....maybe because in the client-router communications it's expected otherwise an error might occur.  

 

"Maybe" the lease time setting is the key to this Playbox issue; maybe not.  Too early for me to say, but I have had my router lease time changed from 1 day to 2 days since lunch time Saturday and neither Playbox has presented me with the no internet connection message yet.   But since it's only been about 30 hours since I made the change it's too early to tell if this has helped yet as sometimes I go for 3 or so days or a few times maybe a week without the no internet message on the Playbox.  But over the last few weeks it seems on one of my two boxes I can't get beyond 3 days without it occurring.   One of my two boxes just displays the problem more often...and they are identical Playbox models.

 

Time will tell on the lease time setting...seems it worked for SooKee.  I need more time before I can say it definitely helped me. If I can get thru 3 days with no error message I'll start feeling more confident....and if getting to a week I be feeling pretty durn sure it helped.  Time will tell.

 

STATIC DYNAMIC RESERVED

A device with static network settings does not need to get involved with DHCP or lease times. Reserving an ip in the routers DHCP pool does not make a device static it just reserves an address for the device with matching MAC. To avoid confusion it is best to think of static devices as those with ip's locked in the device and outside of the DHCP pool. Now we have static ip and reserved ip without confusion.

If your device can only obtain network setting via DHCP please ignore the rest of this post.

My experience tells me that your Android devices are having problems with DHCP lease while sleeping.

The way to prove this is to take DHCP involvement and leases away from the device completely and if this cures the fault then we know the device has problems with DHCP leases only.

Lets stop here and say devices do not need to get involved with a DHCP server if they are capable of storing basic network settings.

IP address - Mask - Gateway - DNS Primary - DNS Secondary

By selecting an ip outside of the routers DHCP pool, example settings might be :-

IP 192.168.1.4 - GATEWAY 192.168.1.1 - MASK 255.255.255.0 - DNS1 8.8.8.8 - DNS2 8.8.4.4

With static settings the device can wake up and go about network business armed with its local settings. It will not need to deal with the router DHCP server and its lease times ever again.