-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PPPwn trought VLAN and Managed Switch #66
Comments
I suggest not introducing too many variables. First, test whether it can work under freebsd before considering the issue of VLAN. I forgot where I saw it, but someone has said that he can run pppwnd_cpp normally using VLAN |
Thank you for suggestion. I can try it with USB Ethernet adapter. |
With usb ethernet adapter its working. So, i can confirm OPNSense/FreeBSD compatibility. So, i would like to ask, what kind of traffic does PPPwn require? I dont understand how those works, specially multicast. but i know both Firwall and managed swithch have separate settings for it, so can possibly block that traffic. |
So, I tried it from FreeBSD without VLAN, and it was working. Only thing comes to my mind is some limits in PPPoE packets, I don't know what exactly can be reason, but I thought about MTU. |
if you always stuck at: I think the problem may be related to multicast. This is the post I saw where someone said he can use VLAN to run pppwn (in Chinese): https://tieba.baidu.com/p/9015522053 |
Interesting. I don't understand much about multicast. I tried some settings, but without any success. But PPPoE server (mpd5 for internet access) is working. Is there something related to multicast that differs on PPPwn and regular PPPoE (for internet connection)? |
A real pppoe server will use the real MAC address of your device. |
Thank
Thank you. This seems to be most likely reason. Currently I'm having trouble with Multicast settings, as I never used it before. Can you please leave this Open, so once I figure out multicast in my network, I can confirm it working or keep looking for other possible reason. |
I can't get it working. But once I get home, I will try dedicated USB Ethernet adapter for PPPwn, connected to untagged vlan port (same vlan as PS4), and see if it works. So, my problem seems to be not running thought VLAN, but having tagged VLAN on device which runs PPPwn I guess. EDIT: maybe I can create bridge, with VLAN as it's member, and set Mac address on that bridge I guess. |
So, I wasn't able to figure out how get PPPwn working thought LAGG and VLAN using managed switch. Not even using dedicated USB Ethernet adapter to managed switch with untagged vlan port. But I can run mpd5 (pppoe server) on that vlan. But, when connected thought dumb switch and dedicated USB Ethernet, pppwn is working. But once connected thought managed switch, it's not. So it is clearly related to some issue on managed switch itself. (Maybe not only issue, as there is also LAGG in way if I wouldn't use USB ethernet, but that would be maybe next issue I would face once I figure out USB Ethernet working thought managed switch). |
Hello.
I successfully jailbroken my PS4 using direct connection to PC with PPPwn_cpp.
I would like to run jailbreak from my OPNSense firewall/router.
Its FreeBSD based OS. I compiled PPPwn_cpp directly on router, and it seems to be running.
But im stuck at:
[*] Waiting for PADR...
I do not have direct connection to PS4, and that can be a problem.
I am using VLANS on OPNSense, and assigning them as Untagged on Cisco managed switch.
So, PS4 is on my LAN, which is vlan1 interface on OPNSense, and its Untagged on multiple ports of managed switch.
As its untagged, PS4 has no clue that traffic comes from VLAN.
Is there any way to get this working over VLAN? If so, are there some recommendations about settings that can possibly prevent it working trought VLAN?
The text was updated successfully, but these errors were encountered: