oscam / newcamd / mgclient problem help please :)

**iphone5** · Mar 23rd 2015

Ok here goes....

Im running oscam to read my card on my ubuntu server with easymouse 2 usb reader! I have set this up without problem. I want to use mgclient 1.38 on my vu solo 2 to connect to oscam/newcamd!

I have setup the newcamd options under oscam and have the following

[newcamd]
port = 34000@0963:000000
key = 0102030405060708091011121314
mgclient = 1

vu solo 2 reciever has the following in /var/keys/newcamd.list

CWS_KEEPALIVE = 300
CWS_INCOMING_PORT = 21000
CWS = xxx.xxx.xxx.xxx 34000 bro1 bro1 01 02 03 04 05 06 07 08 09 10 11 12 13 14 wan newcs

I can get the channels to clear using LOCAL ip address (192.168.0.10) but when i put my EXTERNAL IP where xxx is no channels work. All the examples ive looked at online only show how to get working on local ip??? Is there way to get working using EXTERNAL ip without using CCCAM?

Yes ive got port forwarding setup in my router for the server to connect on external ip.

Any help much appreciated as i cannot understand why its not working unless its not meant to or im being a douche lol.

Cheers

**master G** · Mar 23rd 2015

Check canyouseeme website to see if port 34000 is open..

You also need an mg_cfg configured for the latest images, it`s attached.. Place it in /usr/keys folder..

Remove the wan newcs from the end of the CWS line, it`s not required, the example below is enough:

Code

CWS = xxx.xxx.xxx.xxx 34000 bro1 bro1 01 02 03 04 05 06 07 08 09 10 11 12 13 14

djgee76 · Mar 23rd 2015

You need to put oscam server file in var/keys and tuxbox or usr/keys and tuxbox and restart emu oscam

**iphone5** · Mar 23rd 2015

Quote from djgee76

You need to put oscam server file in var/keys and tuxbox or usr/keys and tuxbox and restart emu oscam

Please explain what you mean? i dont follow

**codar** · Mar 23rd 2015

Have you got cccam to work using your external ip from within your network?
If not, your problem might be your router not supporting nat loopback.
Not all routers can support this and some which do, have the facility turned off.

Quote

NAT loopback

NAT loopback, also known as NAT hairpinning or NAT reflection,[6] is a feature in many consumer routers[7] which allows a user to connect to his/her own public IP address from inside the LAN. This is especially useful when, for example, a website is hosted at that IP address. The following describes an example network:

Public address: 203.0.113.1 (this is the address of the WAN interface on the router)
Internal address of router: 192.168.1.1
Address of the server: 192.168.1.2
Address of a computer: 192.168.1.100

If a packet is sent to the public address (203.0.113.1) by a computer at 192.168.1.100, the packet would normally be routed to the default gateway (the router), unless an explicit route is set in the computer's routing tables. A router with the NAT loopback feature detects that 203.0.113.1 is the address of its WAN interface, and treats the packet as if coming from that interface. It decides based on DNAT (port forwarding) rules on the destination for the packet. For example, if the data were sent to port 80 and there is a DNAT rule for port 80 directed to 192.168.1.2, then the host at that address will receive the packet.

If no applicable DNAT rules are available, the router's firewall drops the packet. An ICMP Destination Unreachable reply may be sent. If any DNAT rules were present, address translation is still in effect; the router still rewrites the source IP address in the packet. The computer (192.168.1.100) sends the packet as coming from 192.168.1.100, but the server (192.168.1.2) receives it as coming from 203.0.113.1. When the server replies the process is identical as for an external sender. Thus, two-way communication is possible between hosts inside the LAN network via their public IP address.

NAT loopback is especially useful when the server hosts a domain name that resolves to a public address. When the router does not perform NAT loopback, any connection attempts to that IP address fail.

Display More

Wikipedia.

If you can see your ports are open (canyouseeme.org) then more than likely it should work using your dns/ip from outside your network but giving a temp share to a friend/ using a different network (connect solo2 to mobile hotspot on phone if your solo2 has a wifi adaptor) will be the acid test.

**iphone5** · Mar 23rd 2015

problem fixed :) Thanks to mastaG i cant believe that cfg and a restart of the softcam worked :) Thanks to all who replied for the help too but i knew i had the router setup right seems it was the files on the solo that needed adjusting. I removed the wan and newcs from the end too. Happy chappy no freezing and lower response times. Seems CCcam has seen its day for performance.

**codar** · Mar 23rd 2015

Glad your sorted, i'll close this so.

oscam / newcamd / mgclient problem help please :)

MGCamd Support Forum

Participate now!

Share

Tags