3 ms·

How is this supposed to work? How will the packet destined to the WiFi IP address get to the Ethernet interface?

loeg 7y ago
The kernel internally routes it to the logical IP address. Since it's an internal address, the packet never goes down to the NIC.
- arielb1 7y ago
  What's the configuration you're talking about? In the Wifi+Ethernet case, how do the routers know to send the packets towards the "right" interface, without the computer having the "right" IP address? I mean, suppose the computer has WiFi IP address 10.0.0.3 & Ethernet IP address 10.0.0.5, then after NAT the return packets will go to 10.0.0.3, and therefore should go to the WiFi interface, not to the Ethernet interface (or, if they don't, how do they know which interface they should go to?).
  - inetknght 7y ago
    > how do the routers* know to send the packets towards the "right"* The described attack utilized a malicious router. I imagine, in theory, that any middle router (such as your ISP) could then be used for such an attack. Imagine Comcast being able to inject their garbage [0] into even VPN sessions. Or a government actor that Comcast is known to route for. [0]: https://tools.ietf.org/html/rfc6108 https://tools.ietf.org/html/rfc6108
  - arielb1 7y ago
    > The described attack utilized a malicious router. I understand how cross-interface packets can be used maliciously. I'm just trying to figure out the non-malicious use cases for them.
    - zrm 7y ago
      Suppose you have a VPN server that routes traffic between several offices. It has tun0 with 192.168.0.1/24 linked to the New York office and tun1 with 192.168.1.1/24 linked to the London office. The server also runs some service, say ssh, and you have a name for it in the DNS that resolves to one of its IP addresses. When you type "ssh vpn-server.example.com" it should work regardless of whether you're in New York or London, right? If 192.168.0.42 can reach 192.168.1.42 by routing through the VPN server then it should generally also be able to reach 192.168.1.1 on the VPN server itself.
- Dylan16807 7y ago
  I believe you're interpreting the question wrong. This isn't "How does the packet get fixed?", it's "How did a packet going to the WiFi IP get transmitted to the Ethernet port in the first place?"

loeg 7y ago

The kernel internally routes it to the logical IP address. Since it's an internal address, the packet never goes down to the NIC.

arielb1 7y ago
What's the configuration you're talking about? In the Wifi+Ethernet case, how do the routers know to send the packets towards the "right" interface, without the computer having the "right" IP address? I mean, suppose the computer has WiFi IP address 10.0.0.3 & Ethernet IP address 10.0.0.5, then after NAT the return packets will go to 10.0.0.3, and therefore should go to the WiFi interface, not to the Ethernet interface (or, if they don't, how do they know which interface they should go to?).
- inetknght 7y ago
  > how do the routers* know to send the packets towards the "right"* The described attack utilized a malicious router. I imagine, in theory, that any middle router (such as your ISP) could then be used for such an attack. Imagine Comcast being able to inject their garbage [0] into even VPN sessions. Or a government actor that Comcast is known to route for. [0]: https://tools.ietf.org/html/rfc6108 https://tools.ietf.org/html/rfc6108
- arielb1 7y ago
  > The described attack utilized a malicious router. I understand how cross-interface packets can be used maliciously. I'm just trying to figure out the non-malicious use cases for them.
  - zrm 7y ago
    Suppose you have a VPN server that routes traffic between several offices. It has tun0 with 192.168.0.1/24 linked to the New York office and tun1 with 192.168.1.1/24 linked to the London office. The server also runs some service, say ssh, and you have a name for it in the DNS that resolves to one of its IP addresses. When you type "ssh vpn-server.example.com" it should work regardless of whether you're in New York or London, right? If 192.168.0.42 can reach 192.168.1.42 by routing through the VPN server then it should generally also be able to reach 192.168.1.1 on the VPN server itself.
Dylan16807 7y ago
I believe you're interpreting the question wrong. This isn't "How does the packet get fixed?", it's "How did a packet going to the WiFi IP get transmitted to the Ethernet port in the first place?"