Internet connectivity issues:- MgCamd

[intrigue]

Hello,

I have had a weird issue with the box ever since I've had it. I've raised it before, to be told by certain people that 'it's not possible'. Well, unfortunately it is as it's continuing!

A couple of issues:

My box can sometimes do something which kills my internet connection. My internet will not then work at all. Wired via the box or any of my other devices via WiFi will not connect to the internet. This has happened with both Sky broadband over ADSL and VM cable broadband. The only way I can get it to work is to disconnect the ethernet cable and bang, the wifi works again! So, this is pretty much pointing towards the box now. I have tried different ISP's, different broadband types, different routers, different cables etc. Any ideas?

Another issue is sometimes the above can happen and then when the internet is working again, I plug the ethernet cable back in. Searching for stuff on TSmedia, on a known working section, gives back no results. Restarting network shows the network restarted, and supposedly working. A couple of restarts later and still not working. Obviously as a result non-FTA channels do not clear but my link to my box downstairs is up and running as it should be. I can go through this process of restarting box and cam a number of times and get nothing. Then I may go in to TSmedia and try a YouTube video, it works, then coming out all of a sudden the channels clear. It doesn't make sense as to why this happens. Is there some kind of network setting in the box which causes this re-occurring problem? A friend has the same box and doesn't have any of this grief!

Thanks in advance!

[Larry-G]

If I remember correctly your initial posts about this were claiming that something in ViX was connecting to the internet and killing your network, thats is the part that is not possible as ViX does not connect to the internet for any other reason than to check for updates which uses almost no data at all and that can be edited out if thats what you want to do. your issue is either going to be hardware related or a result of a plugin or plugins you have installed into the image and without full details, crash logs, debug log etc we cant really help as we would just be guessing as the the issue you are having.

[abu baniaz]

Are you using Mgcamd? If so, upload your mg_cfg?

[intrigue]

Thanks - I don't get crash logs as such, where would I get any other logs that may be useful?

Mg_cfg is as follows?

# EMM messages
# 00 don't show any EMMs (default)
# 01 show only valid EMMs
# 02 show valid and bad EMMs with complete data display
M: { 01 }

# ECM messages
# 00 don't show anything about ecm
# 01 normal mode, show pids processed, decoded ecm and cw
# 02 verbose mode, show valid and bad ECMs with data
C: { 01 }

# AU
# 00 disable, no emm pids processed
# 01 enable, emm pids always processed for soft-au and shared cards
# 02 auto, emm started only if channel cant be decoded
# 03 process emm pids for network cards update only
A: { 02 }

# key update (sum 01 or 02 with 04)
# 01 update only new keys, default setting
# 02 update all keys (used for valid PMK checking)
# 04 enable TPS au
# + tps SID, which pmt pid contains au pid
U: { 01 } 0x12c0

# config files folder (softcam, autoroll, ignore/priority)
# 00 files in /var/keys
# 01 files in /tmp
T: { 00 }

# network mode, use summ for several clients
# 00 no network (default)
# 01 newcamd netclient
# 02 radegast netclient
# 04 camd3 netclient
# 08 gbox netclient
# 32 cccamd netclient, card list saved as /tmp/cccamd.info
# (ECM only, supported server version up to 2.1.1, later not work)
G: { 01 }

# network retry, use summ for several options
# 00 disable
# 01 retry every new ecm
# 02 try to connect to offline shares every Q: seconds
# 04 try to detect and fast reconnect to lost (and not used atm) server
# + XX messages number and YY seconds to reconnect
# mg will reconnect to server, if no answer to last XX ecm/keepalive or
# if no answer for last ecm or keepalive sent for YY seconds
# set to 0 to disable
N: { 07 } 5 30

# network ecm timeout in seconds
K: { 05 }

# newcamd dead routes connect retry, sec
Q: { 600 }

# network shares priority
# 00 gbox, newcamd, cccamd, radegast, camd3 (default)
# 01 camd3, radegast, cccamd, gbox, newcamd
# 02 cccamd, newcamd, camd3, gbox, radegast
P: { 00 }

# on screen display type
# 00 No OSD (default)
# 01 neutrino
# 02 enigma
# 03 relook
# + user password for http auth
O: { 00 } username password

# on screen display Options, summ of:
# 01 show emu ecm
# 02 show network shares messages
# 04 show decoding failed / fta
# 08 show emm keys update
# + web port to use for osd
S: { 03 } 80

# Log option, summ of:
# 00 off
# 01 network udp log
# 02 log to console
# 04 file, appended ! delete it by yourself, before it eat all your hdd
# + IP udp-port log-file-name
L: { 03 } 172.16.1.1 28007 /tmp/mgcamd.log

# keep ecm cache, seconds
# every cache entry takes 28 bytes, so 24h cache will take *only* 240-400kb of memory,
# for openbox/elanvision users with remote shares make sense to set it higher than default value,
# to not hammer cards while timeshifting or playing crypted recordings.
E: { 15 }

# cache option, summ of:
# 00 Off (default)
# 01 Ecm pids cache, store pids used to decode in /tmp/ca_cache.list at exit, load at startup, same syntax as restore.list
# 02 Ecm data cache, remember CW for (E time
# 04 Emm cache for network cards, do not resend the same emm twice, cache not cleared until restart
H: { 07 }

# reread files, summ of:
# 00 No (default)
# 01 reread config file on channel change (including priority and ignore, but not replace/cache)
# 02 reread SoftCam.Key on channel change
# 04 reread SoftCam.Key if file changed
R: { 00 }

# debug, summ of
# 00 off (default)
# 01 debug ecm
# 02 debug emm
# 04 debug network ecm
# 08 debug network emm
# 16 debug network login
# 32 show mem/cpu stats every 1 min
# 64 add timestamp to log messages
D: { 00 }

# box type
# 00 autodetect, change only if you think wrong type detected.
# 01 dbox2
# 02 dreambox
# 03 triple-dragon
# 04 relook
# 05 openbox
# 06 dreambox/mips
# 08 stapi/kathrein
# 09 stapi/ipbox
# 11 stapi/openbox
B: { 00 }

# map all 180x nagra caids to 1801
# default is 01
F: { 01 }

[abu baniaz]

Change this

L: { 03 } 172.16.1.1 28007 /tmp/mgcamd.log

to

L: { 00 }

You are currently trying to send mgcamd logs to IP address 172.16.1.1. You are DDOS yourself.

You might as well as change

B: { 00 }

to

B: { 06 }

[intrigue]

Would my Mg file cause network issues though? Only plugins I have over and above what come with VIX are MediaPortal (problem existed before install), Ondemand player, MyMetrix and OpenStore (to do with the metrix skin I have) and TSmedia

[intrigue]

changed - I'm guessing I just remove the 172.16.1.1 28007 /tmp/mgcamd.log up to the #?

[Larry-G]

Would my Mg file cause network issues though?

yes as ABU says it's trying to connect to a inactive IP address and essentially DDOS'ing your home network. thats the problem with using config files found on the internet without knowing what they contain.

[intrigue]

Thanks Phoenix, will give it a go and see how it pans out!

[abu baniaz]

You guessed wrong. Re-read what was posted for you.

[intrigue]

Hi Abu, sorry, maybe I didn't explain myself correctly:

When I view my cfg in notepad it shows it as one lump, i.e # + IP udp-port log-file-nameL: { 03 } 172.16.1.1 28007 /tmp/mgcamd.log# keep ecm cache, seconds# etc etc etc not set out nicely as it copy and pasted above!

So I have changed it to # + IP udp-port log-file-nameL: { 00 } # keep ecm cache, seconds

If that makes sense? Is that right? I didn't know if I needed to keep the space between the { 00 } and the #

[abu baniaz]

Use Notepad++. This is different from Windows Notepad

[intrigue]

Ok have checked it in notepad++ and thankfully formatting looks correct. Thanks

[abu baniaz]

I am editing thread title. Hope you dont mind.

[birdman]

My box can sometimes do something which kills my internet connection. My internet will not then work at all. Wired via the box or any of my other devices via WiFi will not connect to the internet. This has happened with both Sky broadband over ADSL and VM cable broadband. The only way I can get it to work is to disconnect the ethernet cable and bang, the wifi works again!

Some network issues can be truly weird.
I have an (old) Asus router which is configured to run as a stand-alone system. If I switch it on and connect it via Ethernet all is well for a few minutes. Then my ADSL connexion (run via an ADSL modem 2 hosp away) goes down. All of my internal home network remains OK. Unplug the Asus and ADSL comes back up. I have no explanation for this, so have left it switched off for several years now....
There probably is an explanation for this that would make sense of it all, but...