home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
MP1 Advantage: parts of MP1 "call home" (or somewhere else)
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="resa" data-source="post: 1142719" data-attributes="member: 68500"><p>i can't get all the detailed circumstances and setup descriptions out of this thread that are needed for the bulls-eye solution, but maybe i can give some hints:</p><p></p><p>the fact that mp keeps tethering up is maybe simply founded on keeping the network interface awake enough due to tv-service or mp-client running and waiting for client/server activities... thinking about green ethernet functionalities, which are activated by default...if there is no activity for the network interface, the port speeds down and finally entering a state comparable with shutting down the machine and having the network interface waiting for MagicPackt or Patterns to perform WoL ... meaning... the interface is waiting for serious activity to leave the energy-savings i.e. user requests an connection or router is forwarding an incoming connection etc. to put it simple here: all the managment packets and broadcasts like ICMP, ARP etc. on the network are ignored or only basicily handled... in another manner this applies also on wlan interfaces...</p><p></p><p>try playing around with a) the energy management in windows, also the deeper advanced settings there and b) the advanced network-adapter settings on driver level, reachable from within the network-center and in the the device manager as well... try to prevent your network interface appearing inactive to the tethering-device...</p><p></p><p>next thing... ping is not suitable to keep anything alive for more than miliseconds... even more... ping is only ICMP traffic, meaning network management traffic that is frequently and constantly exhcnaged between all the network devices on lan/wan for several reasons... ping is not considered to be important like traffic that carries real application-data... no serious connection will be established... to compare the difference... stop your internet-activity for some minutes and open cmd, then ping an not so common websites... i.e. asus.com .... and enter "netstat - a" shortly after the ping... you will see a list with open connections and most of them are internal connections on the machine itself... now open an browser, enter the same url here and again type "netstat -a" into cmd.... now you will see a much longer list with opened connections to external targets, at least one of them are server(s) from asus, others are servers from google, facebook, twitter, advertising companys etc. ... you can repeat the netstat -a for some time and you will notice, these connections/ports are traced as active for a quite long time ... now you have seen real network activity, considered as valuable traffic that cant be ignored by any tethering-device or its firm/software...</p><p></p><p>keep in mind, that mobile networks have only very limited network-ressources to connect the clients and therefore they disconnecting inactive clients EXTRA-ASAP in order to set the network free for other clients... you can call it sort of client-balancing.... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> )</p><p></p><p>BTW... pinging the google dns servers constantly/frequently is not really a great idea (but do so on other servers is even an much worser idea <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> ) ... you are simulating an classic DDos -Attack with such an behaviour <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" /></p><p></p><p>i recommend to do some real traffic for keeping things like mobile network-connections and your tethering up... i.e. you can open an ftp-connection to a tiny webspace etc. and refresh directory listing or overwrite a small txt frequently... an basic commandline ftp-client comes with windows and can be used in bats also... or use telnet... or simply start some minimized social-network or chat-thingies... etc. etc. ... but after all, don't rely on having the same IP for long or having an active or funtioning/usuable connection always and for ever on mobile networks with this at all...</p><p></p><p>to be honest... personally i never would give up the physical internet-connection, no matter how slow it is... wireless thingies have the habit for malfunctioning especially in that moments they urgently needed <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p>best regards and good luck <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p></blockquote><p></p>
[QUOTE="resa, post: 1142719, member: 68500"] i can't get all the detailed circumstances and setup descriptions out of this thread that are needed for the bulls-eye solution, but maybe i can give some hints: the fact that mp keeps tethering up is maybe simply founded on keeping the network interface awake enough due to tv-service or mp-client running and waiting for client/server activities... thinking about green ethernet functionalities, which are activated by default...if there is no activity for the network interface, the port speeds down and finally entering a state comparable with shutting down the machine and having the network interface waiting for MagicPackt or Patterns to perform WoL ... meaning... the interface is waiting for serious activity to leave the energy-savings i.e. user requests an connection or router is forwarding an incoming connection etc. to put it simple here: all the managment packets and broadcasts like ICMP, ARP etc. on the network are ignored or only basicily handled... in another manner this applies also on wlan interfaces... try playing around with a) the energy management in windows, also the deeper advanced settings there and b) the advanced network-adapter settings on driver level, reachable from within the network-center and in the the device manager as well... try to prevent your network interface appearing inactive to the tethering-device... next thing... ping is not suitable to keep anything alive for more than miliseconds... even more... ping is only ICMP traffic, meaning network management traffic that is frequently and constantly exhcnaged between all the network devices on lan/wan for several reasons... ping is not considered to be important like traffic that carries real application-data... no serious connection will be established... to compare the difference... stop your internet-activity for some minutes and open cmd, then ping an not so common websites... i.e. asus.com .... and enter "netstat - a" shortly after the ping... you will see a list with open connections and most of them are internal connections on the machine itself... now open an browser, enter the same url here and again type "netstat -a" into cmd.... now you will see a much longer list with opened connections to external targets, at least one of them are server(s) from asus, others are servers from google, facebook, twitter, advertising companys etc. ... you can repeat the netstat -a for some time and you will notice, these connections/ports are traced as active for a quite long time ... now you have seen real network activity, considered as valuable traffic that cant be ignored by any tethering-device or its firm/software... keep in mind, that mobile networks have only very limited network-ressources to connect the clients and therefore they disconnecting inactive clients EXTRA-ASAP in order to set the network free for other clients... you can call it sort of client-balancing.... ;) ) BTW... pinging the google dns servers constantly/frequently is not really a great idea (but do so on other servers is even an much worser idea ;) ) ... you are simulating an classic DDos -Attack with such an behaviour :p i recommend to do some real traffic for keeping things like mobile network-connections and your tethering up... i.e. you can open an ftp-connection to a tiny webspace etc. and refresh directory listing or overwrite a small txt frequently... an basic commandline ftp-client comes with windows and can be used in bats also... or use telnet... or simply start some minimized social-network or chat-thingies... etc. etc. ... but after all, don't rely on having the same IP for long or having an active or funtioning/usuable connection always and for ever on mobile networks with this at all... to be honest... personally i never would give up the physical internet-connection, no matter how slow it is... wireless thingies have the habit for malfunctioning especially in that moments they urgently needed ;) best regards and good luck ;) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
MP1 Advantage: parts of MP1 "call home" (or somewhere else)
Contact us
RSS
Top
Bottom
