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 2
Submit: Bug Reports
MP2 2.1.3 client network broadcast crippling other systems on network
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="Mr Whippy" data-source="post: 1260456" data-attributes="member: 164120"><p>I've just been doing more looking at what MP2 is doing on the network.</p><p></p><p>I had virtual box installed, and it created a virtual adaptor. 192.168.56.1 iirc, which is a default address.</p><p></p><p>Even that address was sending UDP traffic via the server service from what I can see.</p><p></p><p>As you're running a lot of VMs I assume they're all sending lots of traffic via virtual network adapters?</p><p></p><p>Do any of those adapters drop out occasionally?</p><p></p><p></p><p></p><p></p><p></p><p>Also the service monitor is using ipv6 (loopback alongside ipv4 loopback), despite the client being set to not use ipv6.</p><p></p><p>Once I start up the server, that also uses ipv6 addresses (loopback again), alongside ipv4 loopbacks.</p><p></p><p>Only the client appears to use ipv4 or ipv6 when asked to do so.</p><p></p><p></p><p>When I open up my outbound firewall (not blocking with rules), all these ipv6 addresses get connected on 55555 (UPnP)</p><p></p><p>So the monitor seems to think the server and client are connected, but the client won't connect (as it's set to ipv4)</p><p></p><p>Setting the client back to ipv6 (if it wants to) means MP2 is connecting locally using ipv6 loopback on 55555 for UDP, and then using ipv4 for external connections (for 80/443 for web-graphics and all that stuff)</p><p></p><p></p><p>It seems MP2 is hard-set on using ipv6 for UPnP at my end.</p><p></p><p></p><p>I'm a bit baffled about how MP2 is dealing with UPnP in this context.</p><p></p><p></p><p>As Lehmden said earlier, if your client is struggling to connect to the server over UPnP, then it may be struggling because it can't use ipv6, and is set to ipv4?!</p><p></p><p>To get my client/server happy to connect via UPnP, I also had to provide a rule (UDP on local subnet to port 1900, blanket rule). There was no way to attach this rule to any program or service (ie, the mp exes or mp service) and it work.</p><p></p><p></p><p>I'm a bit baffled here.</p><p></p><p>The documentation about exactly what connections are needed is lacking.</p><p></p><p>I think the behavior is confusing in itself which makes trying to bug-fix your issue a bit harder too.</p><p></p><p></p><p>What kind of firewalling/router/switching do you use at your end?</p><p></p><p>I know UPnP is blocked sensibly at most WAN interfaces, but is allowed across LAN. Is all your kit connecting on LAN and not some across a WAN?</p><p></p><p></p><p>Cheers</p><p></p><p>Dave</p></blockquote><p></p>
[QUOTE="Mr Whippy, post: 1260456, member: 164120"] I've just been doing more looking at what MP2 is doing on the network. I had virtual box installed, and it created a virtual adaptor. 192.168.56.1 iirc, which is a default address. Even that address was sending UDP traffic via the server service from what I can see. As you're running a lot of VMs I assume they're all sending lots of traffic via virtual network adapters? Do any of those adapters drop out occasionally? Also the service monitor is using ipv6 (loopback alongside ipv4 loopback), despite the client being set to not use ipv6. Once I start up the server, that also uses ipv6 addresses (loopback again), alongside ipv4 loopbacks. Only the client appears to use ipv4 or ipv6 when asked to do so. When I open up my outbound firewall (not blocking with rules), all these ipv6 addresses get connected on 55555 (UPnP) So the monitor seems to think the server and client are connected, but the client won't connect (as it's set to ipv4) Setting the client back to ipv6 (if it wants to) means MP2 is connecting locally using ipv6 loopback on 55555 for UDP, and then using ipv4 for external connections (for 80/443 for web-graphics and all that stuff) It seems MP2 is hard-set on using ipv6 for UPnP at my end. I'm a bit baffled about how MP2 is dealing with UPnP in this context. As Lehmden said earlier, if your client is struggling to connect to the server over UPnP, then it may be struggling because it can't use ipv6, and is set to ipv4?! To get my client/server happy to connect via UPnP, I also had to provide a rule (UDP on local subnet to port 1900, blanket rule). There was no way to attach this rule to any program or service (ie, the mp exes or mp service) and it work. I'm a bit baffled here. The documentation about exactly what connections are needed is lacking. I think the behavior is confusing in itself which makes trying to bug-fix your issue a bit harder too. What kind of firewalling/router/switching do you use at your end? I know UPnP is blocked sensibly at most WAN interfaces, but is allowed across LAN. Is all your kit connecting on LAN and not some across a WAN? Cheers Dave [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Submit: Bug Reports
MP2 2.1.3 client network broadcast crippling other systems on network
Contact us
RSS
Top
Bottom
