no. still, the host gets not assigned an ip address. if I assign one
manually, doesn't change the fact, that somehow messages don't get through
to the bone...
on host:
eth1 Link encap:Ethernet HWaddr 84:eb:18:ae:cb:aa
inet addr:192.168.7.1 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:174 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7511 (7.5 KB) TX bytes:520 (520.0 B)
fdalbert@edge ~/beaglebone/kernel4-1-new/ti-linux-kernel-dev $ sudo tcpdump
-i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
19:46:52.116552 IP 192.168.7.1.netbios-ns > 192.168.7.3.netbios-ns: NBT UDP
PACKET(137): REGISTRATION; REQUEST; BROADCAST
19:46:52.116593 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui
Unknown), length 28
19:46:52.116595 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 84:eb:18:ae:cb:aa (oui Unknown), length 300
19:46:52.116606 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui
Unknown), length 28
19:46:52.116608 IP 192.168.7.1.netbios-ns > 192.168.7.3.netbios-ns: NBT UDP
PACKET(137): REGISTRATION; REQUEST; BROADCAST
19:46:52.116658 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui
Unknown), length 28
19:46:52.238846 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 28
19:46:52.238866 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui
Unknown), length 28
19:46:53.238687 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 28
19:46:53.238711 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui
Unknown), length 28
19:46:53.741673 IP 192.168.7.1.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)?
_ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
19:46:54.247896 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 28
19:46:54.247917 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui
Unknown), length 28
19:46:54.941595 IP 192.168.7.1.1534 > 192.168.7.3.1534: UDP, length 8
on the bone:
usb0 Link encap:Ethernet HWaddr da:3d:72:a2:b3:7a
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::d83d:72ff:fea2:b37a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:76 (76.0 B) TX bytes:9547 (9.3 KiB)
root@beaglebone:~# ping 192.168.7.1
PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
>From 192.168.7.2 icmp_seq=1 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=2 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=3 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=4 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=5 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=6 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=7 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=8 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=9 Destination Host Unreachable
I'm stuck
On Monday, December 7, 2015 at 7:15:24 PM UTC+1, William Hermans wrote:
>
> SO is the hardware detected on both sides now or what ? If its just a dhcp
> thing, you can always just use static IPs. Which is exactly what I always
> do . . .
>
> On Mon, Dec 7, 2015 at 11:06 AM, Fabian Dalbert <[email protected]
> <javascript:>> wrote:
>
>> I restarted from a backup, updated /opt/scripts/ with kernel 3.8 and
>> installed the new kernel using dpkg as William suggested. No luck.
>>
>> usb0 Link encap:Ethernet HWaddr 84:eb:18:ae:cb:a0
>> inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0
>> inet6 addr: fe80::86eb:18ff:feae:cba0/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:76 (76.0 B) TX bytes:9563 (9.3 KiB)
>>
>> root@beaglebone:~# systemd-journalctl | grep usb
>> Mar 01 21:02:39 beaglebone udhcpd[772]: is interface usb0 up and
>> configured?...e
>> Mar 01 21:02:45 beaglebone avahi-daemon[692]: New relevant interface
>> usb0.IP....
>> Mar 01 21:02:46 beaglebone ntpd[1133]: Listen normally on 4 usb0
>> 192.168.7....23
>> Mar 01 21:02:46 beaglebone avahi-daemon[692]: New relevant interface
>> usb0.IP....
>> Mar 01 21:02:48 beaglebone ntpd[1133]: Listen normally on 5 usb0
>> fe80::86eb...23
>>
>> restarting udhcpd also does not do the trick. Any ideas?
>>
>> Thanks for your help!
>>
>>
>> On Monday, December 7, 2015 at 5:55:23 PM UTC+1, Fabian Dalbert wrote:
>>>
>>> it should be now. however I don't currently have network access on the
>>> beaglebone, I therefore cloned
>>> https://github.com/RobertCNelson/boot-scripts to my desktop and copied
>>> it over.
>>>
>>> On Monday, December 7, 2015 at 5:26:11 PM UTC+1, RobertCNelson wrote:
>>>
>>> ahh, looks like a race between usb0 & udhcpd..
>>>>
>>>> is /opt/scripts/ up to date?
>>>>
>>>> cd /opt/scripts/
>>>> git pull
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> Robert Nelson
>>>> https://rcn-ee.com/
>>>>
>>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
