I have a Raspberry pi 3b, running on "Raspbian GNU/Linux 8 (jessie)" that is currently using a 3G USB dongle to gain internet connectivity. The dongle is a vodafone k5160 set up as an ethernet connection (eth1).
My problem is that whenever i try to connect my rpi to a router on another network using the ethernet port, eth0, it fails to obtain an ip address. It simply gets assigned a random 169.254 local link address, and from reaserching i see that this means it faild to obtain an ip address from the DHCP server. A bit more details on my set up:
Raspberry Pi 3b, using vodafone k5160 to gain internet connectivity, which works and has been working with no issues. The dongle is set up as an ethernet interface eth1, with private ip address 192.168.9.0/24
I tried to connect my raspberry pi to another router, to communicate with another linux system within the router's network. This was done by connecting a straight trough ethernet cable, from the onboard ethernet port to the router.
I have no direct control over the second system i am trying to reach, but i know its ip address within the network. Will be using tcp/ip commands to retrieve data off of this system.
The problem i'm having is that my eth0 interface gets assigned a 169.254.0.0/16 link local ip address meaning it failed to obtain one from the router. The expectation was to obtain an ip address within the range of 10.x.x.x.
I cannot see or ping the other system, and vice versa. Also, this is a remote application i can't easily play with the hardware (i.e. unplug the dongle, plug in the etherent link, and keep trying different things). I do no directly manage the second system but i can get info if required by the person managing it.
Also, as an extra objective, i would like to be able to "split" the traffic between the 2 interfaces. By this i mean to allow to cap the amount of data sent/received by each of these interfaces, and control how much goes through each of these (i hope this makes sense). This is an extra, i would like to focus on my initial issue, and possibly implement this feature once the rest is working.
I received a couple of useful answers prior to my edit to the question. Here is the output of suggested commands to try:
ip route default via 192.168.9.1 dev eth1 metric 203 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.134.241 metric 202 192.168.9.0/24 dev eth1 proto kernel scope link src 192.168.9.100 metric 203
ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:27:eb:e4:f8:66 brd ff:ff:ff:ff:ff:ff inet 169.254.134.241/16 brd 169.254.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::d24f:eade:5e86:f087/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 0c:5b:8f:27:9a:64 brd ff:ff:ff:ff:ff:ff inet 192.168.9.100/24 brd 192.168.9.255 scope global eth1 valid_lft forever preferred_lft forever inet6 fe80::584f:751f:bb3e:e26b/64 scope link valid_lft forever preferred_lft forever 4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT group default qlen 1000 link/ether b8:27:eb:b1:ad:33 brd ff:ff:ff:ff:ff:ff inet6 fe80::ba27:ebff:feb1:ad33/64 scope link valid_lft forever preferred_lft forever