question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sniffing automatically happens on the interface with the default route

See original GitHub issue
  • amazon-dash version: 1.0.4
  • Python version: 3.5.3
  • Operating System: Debian Stretch 9.4

Description

Hi, I just wanted to use amazon-dash and installed it on my homeserver, but during discovery I realised that something is not working as expected. The problem seems to be that sniffing happens on the interface with the default IPv4 route. Due to the fact that my homeserver is also my router, the interface with the default route is not the interface where my LAN is conencted. Therefore the sniff function does not see the Layer2 traffic from my LAN (and therefore not my Dash Button) but only all UDP Traffic from the VPN interface which contains my default route. Due to the fact that it’s a Layer3 VPN amazon-dash discovery shows IP Addresses instead of MAC addresses which proves my hypothesis. When I delete my v4 default route and set the default gateway to something inside of my LAN, everything works as expected.

A possible solution could be to optionally set an interface name in the /etc/amazon-dash.yml and pass this as an argument to scapy’s sniff() function? Haven’t read that much of scapy docu so I’m not sure if this is possible. But you will probably know scapy better.

Let my know if I can help you any more with debugging this problem.

Best regards, Felix

What I Did

$ pip3 install amazon-dash
$ python3 -m amazon_dash.install
$ amazon-dash discovery

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
Nekmocommented, Jul 12, 2018

Interface is now available on develop branch:

Settings:

settings:
  delay: 15
  interface: '<interface>'

On discovery command:

amazon-dash discovery --interface <interface>

Tell me if it works for you 😃

0reactions
Nekmocommented, Jul 13, 2018

You’re welcome 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

Default Gateway - an overview | ScienceDirect Topics
Automatic Determination of Interface Metric ... the speed of the interface for each default gateway and to assign the metric, ... Network Packet...
Read more >
Route Behavior When Using an Interface Acting as DHCP Client
It is common when there is a DHCP assigned IP address, a default route is automatically populated on the Palo Alto Networks firewall....
Read more >
Sniffing (network wiretap, sniffer) FAQ
Automatic sifting of clear-text passwords and usernames from the network. ... They take a direct route of communication, and the traffic never goes...
Read more >
Routing concepts - Fortinet Documentation Library
Routing concepts. This section contains the following topics: Default route; Adding or editing a static route; Configuring FQDNs as a destination address in ......
Read more >
Understanding Default Routes | Junos OS - Juniper Networks
A default route is the route that takes effect when no other route is available for an IP destination address. If a packet...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found