[email protected] <[email protected]> [14-11-29 04:28]: > [email protected] wrote: > > > [email protected] <[email protected]> [14-11-29 02:56]: > > > On 2014-11-28 18:35, [email protected] wrote: > > > >Do I really need two interfaces isb0 and usb1 with different > > > >subnets here? > > > >Or do I miss something? > > > > > > > > > howdy, > > > yes you do. > > > i.e. > > > PC has real-eth0="192.168.1.1/24" > > > PC has usb-eth0="192.168.2.1/24" > > > PC has usb-eth1="192.168.2.2/24" > > > sysA has usb-eth0="192.168.2.101/24" > > > sysB has usb-eth0="192.168.2.102/24" > > > > > > from PC you want to ping 192.168.2.101, ok it pings > > > then you want to ping 192.168.2.102 and you have a cached route for > > > 192.168.2.0/24 dev usb-eth0 > > > you can get around this using policy routing but that is a bit much for > > > what you want. > > > you can always use smaller ranges for example: > > > > > > PC usb-eth0="192.168.2.1/25" > > > PC usb-eth1="192.168.2.129/25" > > > sysA usb-eth0="192.168.2.101/25" > > > sysB usb-eth1"192.168.2.254/25" > > > > > > > > Hi James, hi thegeezer > > > > I want to summerize here what works, what dont work and what I tried > > -- sorry I am no natie english speaker and my english is not exact > > enough for such things...but well...lets see.. > > > > Current setup > > PC: > > usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.10.1 netmask 255.255.255.0 broadcast 192.168.10.255 > > ether ee:6c:bc:6c:03:79 txqueuelen 1000 (Ethernet) > > > > Arietta A: > > usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.10.10 netmask 255.255.255.0 broadcast 192.168.10.255 > > inet6 fe80::215:f2ff:fe18:b030 prefixlen 64 scopeid 0x20<link> > > ether 00:15:f2:18:b0:30 txqueuelen 1000 (Ethernet) > > > > Arietta B: > > usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.10.11 netmask 255.255.255.0 broadcast 192.168.10.255 > > inet6 fe80::215:f2ff:fe18:b030 prefixlen 64 scopeid 0x20<link> > > ether 00:15:f2:18:b0:31 txqueuelen 1000 (Ethernet) > > > > > > Tried: > > (I only have one PC...) > > Only Arietta A connected to PC: Works fine -- ssh login ok > > Only Arietta B connected to PC: Works fine -- ssh login ok > > > > Arietta A connected to PC, after it has booted Arietta B connected > > to the same (motherboard internal) usb-hub of the PC: Cant ssh to Arietta B > > but > > can ssh to Arietta A. > > Switch result if connecting done in opposite order. > > > > Question: > > Is one usb_0 interface on the PC enough? > > Is there something else wrong with my setup? > > You can't have the same ethernet card connected to two different things > -- you have the same ethernet address on both boards, so the poor > thing can only do the first one, you need another interface with a > different ethernet address. > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici > [email protected] >
Hi John, After your email I read the output of dmesg more precisely ... and now knowing (due to your post :) what to look for and found that the detection of another usb-ethernet-device attached to my PC created another usb<n> (first: usb0, second: usb1). I put the first Arietta into the net 192.168.10.x and the second Arietta into net 192.168.11.x and do two different ifconfig for usb0 and the other one for usb1 and TADA! - I could ssh into both! This is not THAT elegant (wasting a complete subnet), but it proofes, that both boards are /relly/ ok... This becomes especially important for me since I had soldered three """PCB connectors""" (<<--- this is bloody typical "german English"... hopefully netherless at least half understandable) to both boards... and soldering such tiny things on very limited space is not what I do like most... ;) So nothing is damaged, and I am happy...until the next """challange""". Thanks a lot for your help!!! Best regards, Meino
