Newbie needs help with Sharing on VLAN

D

dolbyr

Member
My Satellite Setup
2x DM500S with Nabilosat
My Location
Bulgaria
Hello.
I'm new here in the forum, and new to Dreamboxes.

I have my boxes from about a months, they are DM500S clones.
I have flashed both of them with Nabilo v08 maxvar and I'm searching the forums and google from 2 weeks on a way to share my card.

As the MAC address on the clones is identical, I've set up a Vlan to connect both boxes to the net. The IPs are 192.168.1.1xx and 192.168.2.1xx.

I have tried different configs on CCcam but I just cant get the sharing to work. Could someone please help me. Its not mandatory even to be with CCcam.
Currently I'm opening my card using Scam, but seems as CCcam 2.0.9 is able to open it also.
 
The IPs are 192.168.1.1xx and 192.168.2.1xx.
Click to expand...

There's no need to use xx as it's a LAN IP address.

It's easier to have them on the same range: 192.168.1.1 and 192.168.1.2
 
Yes well spotted mhku I had missed that small detail, they are local addresses and need to be in the same range on the lan as already mentioned
 
mhku & Topper,
as I already mentioned, the boxes are in different VLANs, that's why the range is different (192.168.1.130 & 192.168.2.130).

Without connecting them in different VLANs, there is no other way (if you know of an other way, please share!) that both boxes can connect to the router because the MAC Addresses are the SAME.
 
I am sorry but I do not understand why you are doing that, it would be better to jtag one of the DB's and give it another MAC address if indeed they are the same, although again I cannot understand why they would be.
A VLAN is a group of PCs, servers and other network resources that behave as if they were connected to a single, network segment — even though they may not be. The resources and servers of other users in the colocation facility will be invisible to each of the other VLAN members. Equally important, VLANs help meet performance needs by segmenting the network more effectively. Unlike standard switching, they restrict the dissemination of broadcast as well as node-to-node traffic, so the burden of extraneous traffic is reduced throughout the network. Security can also be improved. Since all packets traveling between VLANs may also pass through a router, standard router-based security measures can be implemented to restrict access as needed.

Thus you can never share information or cards between the two
 
The MAC addresses are identical because the dreamboxes are China made clones. It's a widely known issue that all Chinese DM500S clones have identical MACs.

I have no knowledge in JTAG, but If I've understand correctly, I must open the dreambox and solder a cable to some points, is this correct?

As sharing is possible over internet, I suppose that via internet it should work also with 2 separate vlans. Why would this not be possible?
 
dolbyr said:
As sharing is possible over internet, I suppose that via internet it should work also with 2 separate vlans. Why would this not be possible?
Click to expand...

The resources and servers of other users in the colocation facility will be invisible to each of the other VLAN members

If they are invisible to each other they cannot share anything hence it cannot work
 
I see your problem here, As you have discovered, identical MAC addresses wont work on the same network.

Are you using a switch or router for your VLANs?

There are a few ways around this using routing, bridging, NAT.

Probably the most simple way would be to add static routes in your router/modem if it allows this. This will tell your router where to route the traffice from each VLAN. That way, any time a machine on one network or VLAN tries to contact a machine on the other, the router will know where to send the traffic.

I would suggest you establish that the boxes can talk to each other via ping or similar, rather than trying to trouble shoot network problems using CCcam.

Another slightly more expensive way would be to get something like a Linksys WRT54G router and split the network using it. 192.168.1.0 on one side and 192.168.2.0 on the other.

The WRT54G is a powerful piece of kit when flashed with the third party firmware, DD-WRT.

dd-wrt.com
 
compufunk said:
Another slightly more expensive way would be to get something like a Linksys WRT54G router and split the network using it. 192.168.1.0 on one side and 192.168.2.0 on the other.

The WRT54G is a powerful piece of kit when flashed with the third party firmware, DD-WRT.

dd-wrt.com
Click to expand...

This is exactly what I did, I'm running wrt54gl with dd-wrt. Ports 1-3 are on 192.168.1.0 (living room dreambox is with dhcp and static lease for 192.168.1.130) and port 4 is on 192.168.2.0 (bedroom dreambox is with dhcp and static lease for 192.168.2.130)
 
Topper said:
I am sorry but I do not understand why you are doing that, it would be better to jtag one of the DB's and give it another MAC address
Click to expand...


Glad you agree mhku, the words slegehammer crack and nut spring to mind
 
To me, Jtaging is the sledge hammer. (If its a case that you need to JTAG to change the MAC address, I haven't been following that thread.)

Especially since you already have the hardware to get around your problem.

Forget about VLANs as this is just clouding the issue.

If you have a WRT54G there will be 5 Ethernet ports, 4LAN and 1 uplink.

You just need to set it up so that one network is on the LAN side (4 ports) and the other network is on the uplink (Labeled 'Internet' on mine).

If you cant get that set up, bring out the hammer and JTAG one of the boxes.

It depends which which you are more comfortable with, JTAGing or fidling with your router.
 
The link is to one post. No JTAG involved:

To check if your MAC address box login to your box using telnet and enter either:

1. ifconfig

or

2. cat /proc/bus/dreambox



I found the info below elsewhere but either it loses something in translation or seems to do it twice.. so perhaps choose one method only.

To change your MAC address:

Use an init file:

Create an init file with another MAC address in a text editor (ideally a UNIX compatible one) and enter this:


#!/bin/sh
ifconfig eth0 down
ifconfig eth0 hw ether 00:09:34:F4:xx:xx
ifconfig eth0 up


Save this file with the name init and ftp the file to /var/etc on the Dreambox. Reboot the Dreambox and re-check your MAC address. Do NOT delete the init file after you have changed your MAC address.

Change it using telnet:

Login again to your Dreambox in telnet mode and click Format option and type:

ifconfig eth0 down ; ifconfig eth0 hw ether 00:09:34:xx:xx:xx ; ifconfig eth0 up

(xx xx xx can be any HEX double digits) and click enter. To check your new MACaddress enter ifconfig
 
In that case,
Changing the MAC is the easiest option. I thought this involved JTAGing.
 
I've tried the .init file noth with Nabilo and with the SifTeam image that came with the boxes, but for some reason I couldnt make it to work. I don't know what can I be doing wrong.
 
compufunk said:
In that case,
Changing the MAC is the easiest option. I thought this involved JTAGing.
Click to expand...

Probably attributable to me as originally I thought it was all part and parcel of the clone recovery system, apparently it is simpler than that
 
Thanks mhku,
seems like my best bet would be the upload the file to etc/init.d or var/etc/init.d

I tried changing the MAC through Telnet last night. It worked but after that I had no internet connection to the box, it was still seen by the router by I couldnt access the net or other devices in the same LAN.
Does is need a reboot after the MAC change? If so, then the init file is really my only option, I guess.

Btw. I checked last night and atleast CCcam 2.0.9. doesn't decode my card. If I get this MAC thing fixed, maybe Gbox would be te correct one for me, with the SifTeam image I was using Gbox as softcam and there were no problems. Scam blocks quite often and needs to be restarted :(
 
I can't really suggest any further that isn't mentioned in the thread in post #18

Create a test init file to write to a test file. If it works you know the init file has been run; if not try again.
 
Back
Top