You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to forward incoming request from any network participant to the supplicant to the host running silentbridge (in my case a Rapsberry Pi)? I'm using the classic 802.1x bypass.
Use case
My use case is that I want to run e.g. a HTTP server on the Raspberry Pi "in the name of the Supplicant". Incoming packets to the supplicants IP and port 80 should be "taken out" of the transparent bridge and destined to the HTTP server.
In this scheme requests to 192.168.0.38:80 should be processed by the services running on the Raspberry Pi and the rest should flow to the supplicant, as usual.
Usually I would use iptables DNAT rules or policy based routing to accomplish this, but as the silentbridge host does not have own IP addresses on the phy and upstream interfaces, so I don't really know what to do here. I would appreciate some help or ideas :)
Thanks for this very nice tool.
The text was updated successfully, but these errors were encountered:
Is it possible to forward incoming request from any network participant to the supplicant to the host running silentbridge (in my case a Rapsberry Pi)? I'm using the classic 802.1x bypass.
Use case
My use case is that I want to run e.g. a HTTP server on the Raspberry Pi "in the name of the Supplicant". Incoming packets to the supplicants IP and port 80 should be "taken out" of the transparent bridge and destined to the HTTP server.
In this scheme requests to
192.168.0.38:80
should be processed by the services running on the Raspberry Pi and the rest should flow to the supplicant, as usual.Usually I would use iptables DNAT rules or policy based routing to accomplish this, but as the silentbridge host does not have own IP addresses on the phy and upstream interfaces, so I don't really know what to do here. I would appreciate some help or ideas :)
Thanks for this very nice tool.
The text was updated successfully, but these errors were encountered: