Satellite Internet via Dreambox.
Satellite Internet via the receiver Dreambox
Satellite receiver Dreambox in the right hands fully justifies its name. The Linux operating system used in it makes it possible for almost any programmer to write their applications that expand the capabilities of the device. Among the interfaces with which the receiver is equipped, there are USB 1.2 and 10/100 MBit Ethernet, which makes it possible to connect it to a local network.
Naturally, inquiring users the question arises - is it possible to use the Dreambox to receive data? Hardware receiver is ready for this. However, for a long time these functions were not implemented. Then the situation began to change. Using the DreamData plug-in from the German programmer Mechatron, the task of receiving multicast streams of services Casablanka (Sat @ once), Filiago, EasyNet, AliceSat, etc. was solved. For grabbing (fishing) Internet streams, the receiver began to work as a premix for the popular SkyNet program .
And finally, this summer on the allrussian.info forum, the joint work of several people led to a positive result. The technique of using the Dreambox DM-7000S receiver as a receiver of a full-fledged asymmetric Internet has been developed. To clarify - the connection to the terrestrial and satellite providers is made on the computer using a modem, GPRS, local area network, ADSL, etc. The Dreambox itself works as a satellite receiver and a DVB / IP router.
So, we give the floor to visitors of the forum allrussian.info.
We have a receiver Dreambox DM-7000S. Pay attention that the image is not very ancient, dvbnet support has been built in since March 2005.
. We use the operator SpaceGate, Express AM22 satellite (53 E).
We configure the Dreambox on the channel with the SpaceGate data: fr = 10969 s / r = 24128 fec = 7/8 pol = V
Connect to the receiver, go to telnet and give these commands:
~> dvbnet 1B58
(created a new network interface that listens to PID 7000 (1B58 - hex) - PID
You can create several such interfaces, for your own PIDs and MACs (for example, for different subscriptions).
To remove an unnecessary interface: dvbnet -X (dvb0_X is the interface number)
For example, dvbnet -2 removes dvb0_2.
~> ifconfig dvb0_0 192.168.3.1 netmask 255.255.255.0 hw ether 00: xx: xx: xx: xx: xx mtu 1500
192.168.3.1 - IP address for the newly created dvb0_0 (you can also substitute another). Do not substitute here a gray IP, which assigns you a satellite operator.
00: xx: xx: xx: xx: xx - the MAC address of your subscription
further we configure routing
~> echo 1> / proc / sys / net / ipv4 / ip_forward
(we allow packet forwarding, i.e. it makes a router from the driver)
~> echo 0> / proc / sys / net / ipv4 / conf / all / rp_filter
(reset the filter responsible for sending the packet only from the interface from which it came. rp_filter - reverse path filtering)
~> echo 0> / proc / sys / net / ipv4 / conf / dvb0_0 / rp_filter
(the same, but for our new interface dvb0_0 - reverse path filtering)
~> route del default
(remove old defaul gateway)
~> route add 0.0.0.0 gw 192.168.XX.XX dev eth0
(we direct all flow to the gateway 192.168.XX.XX (i.e. on the PC)
where: 192.168.XX.XX is the IP of the network card in the computer to which the Dream is connected.
In the Manual transponder menu, we tune to the frequency with the parameters at which SpaceGate works, the signal should be locked. (crosses should appear in Lock and Synch).
We connect to the ground-based Internet (modem, gprs), turn on the VPN and try it - everything should work
You can work with satellite accelerator GlobaX. The first option is via the GlobaX + loopback adapter (loopback), which contains the IP issued by SpaceGate. The second option - without VPN and without loopback. We put on the network card in the computer the IP address that the provider issued. In this case, neither VPN nor loopback is needed. GlobaX works fine in this configuration. (Note - all IP protocols go through VPN. Through Globax, and it is a local HTTP proxy - a limited number).
Later, there were reports of successful work on the receiver DreamBox 500, firmware Gemini 2.10.
Well, now all that remains is to automate. The first step in automating this process is to place the script in /var/bin/sat_inet.sh, give it execution rights (755), write it in Expert Setup -> Scripts Autoexec Setup (there are images in the ruDREAM command).
#! / bin / sh
ifconfig dvb0_0 192.168.3.1 netmask 255.255.255.0 hw ether 00: d0: d7: XX: XX: XX mtu 1500
echo 1> / proc / sys / net / ipv4 / ip_forward
echo 0> / proc / sys / net / ipv4 / conf / all / rp_filter
echo 0> / proc / sys / net / ipv4 / conf / dvb0_0 / rp_filter
route del default
route add 0.0.0.0 gw 192.168.XX.XX dev eth0
DreamBox and SatGate.
In continuation of the theme of using DreamBox as a DVB / IP router, the following scheme was assembled:
Equipment: We have access to the Internet via D-Link DSL-G604T (Router, ADSL, 4 port switch, Wi-Fi 802.11g), a subscription to satellite Internet at SatGate (Sirius 5E). We work on VPN, Dreambox DM-7000S with the winchester.
Task: launching satellite Internet for home users, downloading files at night during cheap tariffs on the Dreambox hard drive on a schedule without PC involvement.
To do this, you need to raise the VPN on D-Link e and use the Dreambox as a DVB / IP router.
First, I had to install an alternative firmware from mcmcc on D-Link (there is a benefit there for Linux) in order to run pptp ("Native" branded firmware does not have this capability).
So, the Dreambox is configured and "drives" packets on the default gw from the satellite to D-Link. We raise VPN on D-Link - everything works, satellite Internet is distributed everywhere, and on Wi-Fi too.
But periodically there is a hemorrhage with a VPN connection, and then terrible packet loss begins. But at the same time, if the VPN is launched under Windows, everything is stable and with the Dreambox as DVP / IP works for hours.