A connection to the Internet can be realized with different Internet access technologies implementing diverse protocols:
See the following sections that pertain to your particular connection requirements:
# Configure pppoe connection uci set network.wan.proto=pppoe uci set firstname.lastname@example.org' uci set network.wan.password='yourpassword' # Configure atm bridge uci set network.atm.encaps='llc' uci set network.atm.payload='bridged' uci set network.atm.vpi='8' uci set network.atm.vci='32' # Configure adsl settings uci set network.adsl.fwannex='a' uci set network.adsl.annex='a2p' # Save changes uci commit network # Restart network service to reflect changes /etc/init.d/network restart # Bring up the atm bridge and start it automatically on boot /etc/init.d/br2684ctl start /etc/init.d/br2684ctl enable
uci set network.wan.proto=pppoe uci set email@example.com' uci set network.wan.password='yourpassword' uci commit network ifup wanOne might read more at network
uci set network.wan.proto=static uci set network.wan.ipaddr=18.104.22.168 uci set network.wan.netmask=255.255.255.0 uci set network.wan.gateway=22.214.171.124 uci set network.wan.dns='126.96.36.199 188.8.131.52' uci commit network ifup wan
Note:The opposite (USB reverse tethering aka USB internet passthrough) is also possible.
Next-generation network comprises VoIP and IPTV and everything is based on the Internet Protocol! These data streams should be separated from the usual data stream and routed to some hardware port where you can grab them with whatever device you wish to use them. If the output does not take place over a standard Ethernet Port, but e.g. over an ISDN- or a TAE connector, a corresponding signal has to be generated in hardware. This needs Linux support as well.
A trick to make the data packets belonging to the different services easily distinguishable from one another, is the usage of VLAN trunking. It has to be done on both sides, and you have to utilize the same VIDs as your ISP does. So, go learn about VLANs.
While you learn about VLAN and VLAN trunking it might be helpful to keep in mind, that with VLAN trunking you send three (respectively two) data services over one line, but want to simulate that you do this over three (respectively two) lines. So you have three virtual ports on the ISP side, each sends its packets over its own virtual line, to each its virtual port in your router. Now to get the data OUT of your router, each of the three virtual ports, has to have second port connected to it.
So, on your side, you would need six ports and three lines, but you (most likely) have only four ports and one line. So make the one port with the line connected to it, act as if it was three ports with each one separate line connected to it. That's it. As easy as eating pancakes or opening a can with an electrical can opener.