CCcam works through LAN but not remotely

**Comet** · 09-01-11, 01:24 PM

Hi,
I've got a 500S and have been able to have it act as a client through a local LAN connecting to another 500S. I then took the box to another house and now get the below.

Code:

root@dm500 /var/etc # CCcam -d -v
12:44:42.245 CCcam: ======================================================================
12:44:42.247 CCcam: starting CCcam 2.2.1 compiled on Nov 21 2010@02:20:06
12:44:42.247 CCcam: ======================================================================
12:44:42.249 CCcam: online using nodeId 214c2134bd40753d
12:44:42.261 CCcam: dvb api1 detected
12:44:42.263 CCcam: DM56xx/500/600 detected
12:44:42.264 CCcam: create 2 cam device(s)
12:44:42.465 CCcam: added 0 keys from /var/keys/SoftCam.Key
12:44:42.466 CCcam: readKeyfile: cannot open /var/keys/AutoRoll.Key or not found
12:44:42.467 CCcam: static cw not found or bad
12:44:42.468 CCcam: parsed 0 entries from /var/etc/CCcam.prio
12:44:42.470 CCcam: readProviderfile: cannot open /var/etc/CCcam.providers or not found
12:44:42.471 CCcam: readChannelList: cannot open /var/etc/CCcam.channelinfo or not found
12:44:42.473 CCcam: server started on port 12000
12:44:45.481 CCcam: found irdeto caid: 0x604 ecmpid: 0x1778 id: 0x0
12:44:45.482 CCcam: found nds caid: 0x90b ecmpid: 0x1390 id: 0x0
12:44:45.482 CCcam: found nds caid: 0x96c ecmpid: 0x1584 id: 0x0
12:44:45.483 CCcam: cam[0] set PMT for sid=1390
12:44:45.485 CCcam: start EMM
12:44:45.608 CCcam: EMM demux 1 set
12:44:45.609 CCcam: EMM: start filter on irdeto emmpid: 0x3ea caid: 0x604 id: 0x0
12:44:45.610 CCcam: EMM: start filter on irdeto emmpid: 0x3ea caid: 0x624 id: 0x0
12:44:45.610 CCcam: EMM: not interested in 090B:000000
12:44:45.610 CCcam: EMM: not interested in 096C:000000
12:44:45.780 CCcam: chid 0196
12:44:45.780 CCcam: chid 0228
12:44:45.781 CCcam: cam[0] ecm even nok caid:0x604 id:0x0 pid:0x1778 Unknown

On the server side it gets my request as it shows this.

Code:

00:02:44.745 CCcam: new tcp client from xxx.xxx.xxx.xxx
00:02:45.684 CCcam: deleting client xxx.xxx.xxx.xxx, signature failed

I can also telnet onto the server so the port is routed correctly to the server from the client box.

Any suggestions on determining what might be going wrong? It doesn't seem to get to the point where it does any authentication so I am baffled as to why it would work on a LAN and not through a remote connection. Whilst I was on the LAN I also had the static IP address rather than the LAN ip and it worked so I assumed it wouldn't have any issues when accessing it from a different location. Any help is appreciated.

**florra** · 09-01-11, 03:43 PM

You say that your port is routed correctly, but if it works in your local lan, then the only reason why it wont work remotely is either, the IP address is incorrect or your port forwarding isn't configured correctly.

**Comet** · 09-01-11, 03:52 PM

From the dreambox I can telnet successfully to the server dreambox. Am I misunderstanding something?

Code:

root@dm500 ~ # telnet xxx.xxx.xxx.xxx 12000
?%?9??c2q)??E?

**Comet** · 09-01-11, 04:30 PM

And I've also tried it by tethering my iPhone to my laptop and used it as a bridge and same situation so my assumption is that it's not a network issue on my end.

**freakee1** · 09-01-11, 06:10 PM

Hey Comet,

just to clarify

you have a Dream500s, it is at your place & is your server, the second one is at your friends place and it won't talk to the server.

You can talk to the Server DM from the client DM

OK - try this
Make your DM's ip static
port forward 12000 of your router to the Dream Server IP
if your Internet Provider doesn't run with Static IP's then you may need a dyndns server.
if you get a dyndns server then change the ip address in the c line in the DM500 at your friends place to reflect the dyndns server (otherwise make sure it is your ip address of your internet router - not the ip address of your DM)

give that a go

goodluck

cheers

f

**Comet** · 09-01-11, 11:03 PM

Thanks for the tip. Unfortunately tried with the static IP and port forwarding. No dice...

**Smacca** · 09-01-11, 11:15 PM

First thing I would do is revert CCcam back to an older version at the client end. Perhaps 2.1.1? Test and report back!

**ferni** · 10-01-11, 07:25 AM

If you can telnet from the dreambox to the server on the port you're trying to connect from then your network settings are all fine (as i'm sure you realised). So i'd stop looking at network and start looking at software. I haven't used cccam as a server before so can't help to much. Do you use an encryption key with the server? (the 01 02 03 etc.. stuff).. maybe that's not matched?

**Comet** · 10-01-11, 08:07 AM

Tried it with 2.0.0 on both ends but still the same result. Are there any logs that might give more indication of what might be the problem?

Not using any encryption key with the server...

Thanks for the suggestions so far.

**raygbmw1** · 10-01-11, 11:07 AM

I use the PFPortCheck to check the port (lan/wan) setup if I configured the router properly maybe try that. After I get the ok from PFPortCheck I ask my brother form his home to check and ping my ip/dns address. If I get an ok from my brother then I know the port is configured ok.

I find that when pinging my ip address from within the LAN it can give you false positive.

**Comet** · 10-01-11, 10:44 PM

Tried with pfportchecker and said port 12000 was ok. Very baffled as the server continues to show kick xxx.xxx.xxx.xxx, signature failed.

**freakee1** · 10-01-11, 10:54 PM

Originally Posted by Comet

Tried it with 2.0.0 on both ends but still the same result. Are there any logs that might give more indication of what might be the problem?

Not using any encryption key with the server...

Thanks for the suggestions so far.

hey Comet

I wouldn't vary from the CCcam encryption due to the fact that the 14 bytes that you have emitted may be the issue with the signature being incorrect

stick with the 01 02 03 04 ........ untill things are working - then change them to something else later

f

**Comet** · 11-01-11, 12:45 AM

Not sure if it's useful but the server side gets this.

23:36:48.624 CCcam: newcamd_send: buffer of 15 bytes
23:36:48.625 CCcam: 0000: 00 00 00 00 00 01 00 00 - 00 00 00 00 FD 00 00 ........ - .......
23:36:48.700 CCcam: 0000: FD 00 00 - ... -
23:36:55.744 CCcam: new tcp client from xxx.xxx.xxx.xxx
23:36:56.744 CCcam: deleting client xxx.xxx.xxx.xxx, signature failed

This is running CCcam -dvn

Anyone have any ideas? Summary so far:

- When server and client are on the same network it works. (i.e. C: contains something like 192.168.0.1 12000 user password)
- When I change the ip address on the C: line to the public IP it produces the signature failed message the first time, but then starts working.
- When I move the client dreambox to a different network it constantly gets the signature failed message and doesn't work.
- PFPortChecker tool tells me that 12000 is open. OS X doing a port scan through the network utilities also produces

Port Scanning host: xxx.xxx.xxx.xxx

Open TCP Port: 12000 entextxid
Port Scan has completed…

- When on the local network where the server and client are on the same network, signature failed constantly occurs when I kill the initial CCcam process and I start another one through CCcam -dvn

Any suggestions etc is appreciated!

**ferni** · 11-01-11, 08:22 AM

Interesting, i didn't realise you'd tried both the server box and client box on same network, then you're just moving the client box...

What about if you try moving the client box to another network (just to test)...?

Is there any reverse DNS configuration/auth you have setup?

**Comet** · 11-01-11, 12:52 PM

Originally Posted by ferni

Interesting, i didn't realise you'd tried both the server box and client box on same network, then you're just moving the client box...

What about if you try moving the client box to another network (just to test)...?

Is there any reverse DNS configuration/auth you have setup?

I've got a 3G modem/router so I used that to connect the client to the internet to see if it can access the server. That's how I end up with signature failed. It doesn't get to the point where it authenticates so I assume it's network related.

The network setup is pretty simple with a static IP from the ISP. NAT doing its thing to route port 12000 to the server box. Might have to try a different ADSL2 modem to see if that changes the behaviour.

BTW, does anyone know what the signature failed message means?

**nfnovice** · 11-01-11, 03:23 PM

Originally Posted by freakee1

hey Comet

I wouldn't vary from the CCcam encryption due to the fact that the 14 bytes that you have emitted may be the issue with the signature being incorrect

stick with the 01 02 03 04 ........ untill things are working - then change them to something else later

f

As I understand it we are talking CCcam server and CCcam client

so the 01 02 .. 14 does not come into it .. thats is only for NewCs or similar server with mgcam or CCcam N: line client.

Comet can you confirm CCcam C: line client to CCcam Server ?

**Comet** · 11-01-11, 03:30 PM

Originally Posted by nfnovice

Comet can you confirm CCcam C: line client to CCcam Server ?

Yes, on the client I have a C: line in hte CCcam.cfg pointing to the server that has F: line in the CCcam.cfg

**Comet** · 13-01-11, 11:51 AM

Just an update.
As my last resort I've created an SSH tunnel to the server dreambox and I have finally got it working. Very bizarre but I still need the port forwarding on the router for the dreambox server (port 12000) in place or else the tunnel doesn't work...

So it was in the end a network issue...

**zooma** · 13-01-11, 04:31 PM

Hello Comet,

I intend to do something similar and would like to be prepared if (when!!) trouble starts :-).

Can you give a few more details about the ssh tunnel please?
eg. Did you forward port 12000 on the client to 12000 on the server, then connect cccam to localhost:12000?

Thanks.

Zooma.

**Comet** · 13-01-11, 09:15 PM

Originally Posted by zooma

Hello Comet,

I intend to do something similar and would like to be prepared if (when!!) trouble starts :-).

Can you give a few more details about the ssh tunnel please?
eg. Did you forward port 12000 on the client to 12000 on the server, then connect cccam to localhost:12000?

Thanks.

Zooma.

Hi there,
On the server side
- Installed dropbear
- Did a port forward for 22 and 12000 on the modem/router
- Created another user id so that the ssh goes through without using root

On the client side
- Installed dropbear
- scripted a command (ssh <userid>@<server's global ip> -L 12000:<server's internal ip>:12000)

Another update to this issue is that i finally got hold of a different modem/router and that seems to have made the whole setup work without a ssh tunnel. Just port forwarding of 12000 on the router!

Thread: CCcam works through LAN but not remotely

Thread Tools

Search Thread

Display

CCcam works through LAN but not remotely

The Following User Says Thank You to florra For This Useful Post:

The Following User Says Thank You to freakee1 For This Useful Post:

The Following User Says Thank You to Smacca For This Useful Post:

The Following 2 Users Say Thank You to ferni For This Useful Post:

The Following User Says Thank You to raygbmw1 For This Useful Post:

The Following User Says Thank You to freakee1 For This Useful Post:

The Following User Says Thank You to ferni For This Useful Post:

The Following 2 Users Say Thank You to nfnovice For This Useful Post:

The Following User Says Thank You to Comet For This Useful Post:

The Following User Says Thank You to Comet For This Useful Post:

Bookmarks

Bookmarks

Posting Permissions