Xxx.yyy.142.0/24 dev eth0 proto kernel scope link src xxx.yyy.142.226 metric 202 TX packets:199 errors:0 dropped:0 overruns:0 carrier:0 RX packets:271 errors:0 dropped:49 overruns:0 frame:0 TX packets:108 errors:0 dropped:0 overruns:0 carrier:0 RX packets:108 errors:0 dropped:0 overruns:0 frame:0 TX packets:3381 errors:0 dropped:0 overruns:0 carrier:0 RX packets:72200 errors:98 dropped:740 overruns:0 frame:0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Here are some outputs from programs for more information: # route -nĭestination Gateway Genmask Flags Metric Ref Use IfaceĠ.0.0.0 xxx.yyy.142.1 0.0.0.0 UG 202 0 0 eth0Ġ.0.0.0 xxx.yyy.234.1 0.0.0.0 UG 303 0 0 wlan0 I don't understand why the echo isn't being routed back to its origin. When I ping the IP given to wlan0, tcpdump sees the echo requests (and even goes so far to resolve the hostname). However, I can no to anything to access the IP address given to wlan0. I can ping, ssh, and otherwise access the pi over the IP address given to eth0. This pi is going somewhere where it can't reach an ethernet port, so it needs to work over wifi. Right now it gets an IP address from the DHCP server on both eth0 and wlan0. I'm working on getting a Raspberry Pi setup on a WPA2-Enterprise network.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |