Timeline for ExitPolicy reject *:* some traffic seems to sneak throu anyway?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 7, 2017 at 5:24 | vote | accept | Orphans | ||
| Apr 7, 2017 at 5:24 | comment | added | Orphans | @P.Gerber Thanks for the explanation. I have talked to UBNT and they still claim that their product identifies services via Deep Packet Inspection and not just the ports the communication is. But I did some test again and send mysql trafik over port 80 - and it identified as HTTP! So the problem here in EdgeOS and not Tor. Regarding specialized hardware/software for DPI, check out Palo Alto Networks firewalls - they are pretty neat (using them myself and work and they have REAL DPI) | |
| Apr 6, 2017 at 19:38 | comment | added | Peter Gerber |
Non-exit relays will connect to other relays using any port. The ExitPolicy, as its name suggest, only limits what IPs and ports that can be connected to when exiting. I too doubt that any packages inspection is done: a) some protocols listed are very hard to distinguish (in particular anything using TLS/SSL), b) doing so is quite resource intensive, c) it isn't exactly easy to implement and d) I doubt that anyone interested in package inspection will use EdgeOS (I'm sure there is specialized software/hardware for it)
|
|
| Apr 6, 2017 at 13:18 | comment | added | Orphans | I really do not think that this is the case. EdgeOS is inspectning the packets from the it can identify the services. I thought so too but I did some tests and it could correctly identify the services even if the defaults ports was changed. However, why is the Relay generation traffic over thoose ports? I have only opened up 9001 and 9030 and it is not an Exit Node - even if you explanation could be valid it does not explain why the relay is generating traffic over thoose ports. | |
| Apr 6, 2017 at 12:48 | history | answered | cacahuatl | CC BY-SA 3.0 |