How to properly set up bridge in deb jessie?

Question

linux

Damn, I've been suffering for 2 days, I can't set up the bridge, can anyone tell me what the reason is, or at least advise where to dig? ((
here is my interfaces:
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
auto br0
iface br0 inet dhcp
bridge_ports eth0 eth1
bridge_maxwait 0
bridge_stp off
I restart the network, the IP address (ip4) appears on eth0 and br0, while the Internet is only eth0 (wrong behavior)
did purely through the console:
initial state:
auto eth0 - Internet only here
eth1 is not configured
# ifconfig eth0 0.0.0.0 down
# ifconfig eth1 0.0.0.0 down
# brctl addbr br0
# brctl addif br0 eth0 eth1
# ifconfig eth0 up
# ifconfig eth1 up
# ifconfig br0 up
# dhclient br0
further on the ifconfig output, 2 interfaces are up, the bridge is up, IP is only at the bridge (it seems to be true, but) - and again only eth0 has Internet 25,
everything seems to be fine but eth1 bridge doesn't have internet... it just doesn't even come to mind, what to do next?
Threat question about devices, I have 2 network cards and 1 vlan on my computer, but according to the output of ifconfig there is another eth2 - it does not have an IP, the poppy is almost the same as eth1, only the last byte is different and when I look in the interface ( parameters) there is only: wifi / eth1 / eth2 and everything (well, the bridge if it is raised accordingly) - I don’t understand where eth2 came from, and why is eth0 not visible in the interface?
ZZY By the way, I have an Internet: a direct connection tied to a network poppy (when he made the bridge, his poppy was the same as that of eth0 - it was he who was attached).
Actually 3 questions:
1) why is the behavior different when I do it through the config and through the console?
2) Why is eth0 not visible in the network parameters and some strange eth2 has appeared?
3) Well, actually how to properly configure the bridge through the console and through interfaces?

Answer 1

iface eth0 inet dhcp
iface eth1 inet dhcp

What for? Of course the outcome will be strange.
inet manual
This is a bridge. You will have 2 physical interfaces in promiscuous mode without any addresses and one bridge. All further work with L2 and above is carried out on behalf of the bridge. The DHCP client rises there, it is registered in the firewall
1) because you are trying to do stupid things in the config
2) lsusb, lspci, dmesg
3) you configured it correctly through the console. Via interfaces - inet manual on service interfaces.