31 replies to this topic

[digidude]

that seemed to work, as the attached screen grab shows, but after a restart both boxes have the same MAC address again, is this to be done after every restart, or is it meant to be a permenant change?

Attached Files

•  changemac_1.jpg   34.53KB   4 downloads

[dAF2000]

that seemed to work, as the attached screen grab shows, but after a restart both boxes have the same MAC address again, is this to be done after every restart, or is it meant to be a permenant change?

It's not permanent. To make it permanent you need to add a file. I think this will work, but didn't try it myself:

ln -s /bin/changemac.sh /etc/rcS.d/S41changemac
(the first character on the line is "L")

[digidude]

ill try this once ive got the kids to bed in an hour or so, will this line of text copy the file thats needed to make this a permenant change?

once again thanks for all the help

[WanWizard]

No, it will not make a copy. It creates a link to your change script in the rcS.d directory, where all the system startup scripts reside. So next time you boot the box, your script will be executed.

[digidude]

thank you soooooooo much :)

i did the above, and checked the MAC had changed, which it had, then reset the power to the receiver and checked again, and it had stayed changed

thank you

Attached Files

•  changemac_2.jpg   27.25KB   8 downloads

[digidude]

i think this may be an actual hardware issue

the MAC is showing as changed in the receiver OSD, yet im still getting the same conflict when both boxes are connected together but thank you for all the help and advise

[jonc]

from your shell or cmd on your computer do this;

ping yourdm500
ping yourdm7020

now do this command

arp -a (it will show something like this)

# arp -a

(192.168.1.202) at 00:9C:03:43:03:1A [ether] on eth0
(192.168.1.201) at 00:9C:03:43:03:4A [ether] on eth0


If the script did not work it will still look something like this with duplicate MAC addreses [which is wrong]

# arp -a

(192.168.1.202) at 00:9C:03:43:03:4A [ether] on eth0
(192.168.1.201) at 00:9C:03:43:03:4A [ether] on eth0

[pieterg]

your network equipment (or dhcp server) probably gets confused because while booting, before you change the mac, the box is actively using the old mac.

The only solution is to get a real dreambox.
The problem with those clones is that the manufactorors only care about how genuine it looks. How well the box works is of no real concern to them, they already made their money by then.

[digidude]

the problem boxes are 2 7020Si clones

one has IP 192.168.1.9 andthe other 192.168.1.99, they both have the MAC 00:09:34:14:BE:70. the .9 one is being used as my server, but even if i let the .99 one boot up fully (with time to change the MAC with the script as shown) and then connect it to the network, after about 45 seconds everything crashes untill i disconnect one of the boxes. DHCP is turned off on both receivers so that the IP stays the same for port forwarding reasons, so i think my router may be interrogating the actual hardware and seeing the 'real' MAC address and this is causing the confusion.

I had even had the ethernet controler chip replaced in the one box as i was convinced this was the fault, so was a bit of a let down when after repair, it was still the same

guess ill have to sell it on and await the release of the DM8000 now

[digidude]

i did the command and attached the results, everything crashed about 20 seconds later

192.168.1.6 is a genuine DMM 600s, .9 is a 7020 running as my server and .99 is the one im trying to get onto my network without crashing it all, while it reports the mac that i put into the script file, something is still causing it to crash

Attached Files

•  changemac_3.jpg   52.91KB   3 downloads

[jonc]

Well as you say there is something else at issue now as it is reporting to the LAN as it should with the updated addresses.
So your next job is to find out why it is crashing.

[digidude]

i did a factory reset on this receiver and now about 20 secs after reboot the lan port dies, the receiver has also been reflashed but it still not connecting to LAN at all, is it possible that the factory reset deleted the reference in /var and now one of the other copies has survived and is disabling the port upon bootup?

if so, where would i find the file, and how would i get to it without LAN access?

cheers for looking