Accessing PPPoE Modem
-
Shouldn't matter what media it bridges to. You got a PPPoE connection to your pfSense's WAN and that's working, right?
Your WAN is static you said. Does it get the same address/IP via DHCP when connecting?Yes, I get my external IP showing up on the 'Interfaces' page on pfSense, along with my ISPs DNS and Gateway.
You should not config your vr0 if manually. This can/might/will break things.
Just leave it the way it is. Redir just forwards to the caddr.Not quite sure what you mean, should I use fxp0, even though thats not currently a valid interface? ng0 was rejected, and when I used vr0, it was accepted but I had to disconnect/connect the PPPoE interface to regain internet connectivity.
You rebooted already…
After I rebooted, redir was found, but didn't work properly, getting the error
redir –lport 8080 --cport 80 -caddr 10.0.0.2
addr: host unknown.
-
redir –lport 8080 --cport 80 -caddr 10.0.0.2
addr: host unknown.
OK, forget about the comments about the interface in my previous post…
Use your WAN interface (vr0) and assign an IP to it:
ifconfig vr0 10.0.0.1/24Add the redir proxy then:
redir --lport 8080 --cport 80 -caddr 10.0.0.2 &You should be able to access the modem through http://pfsense-lan-ip:8080 then.
Maybe you forgot the trailing '&'?
Just checked it over here. I can access my modem's web server and have access to the internet, of course. The latter shouldn't be affected by this.
-
Why not let the modem do the PPPoE authentication to your ISP, …
You don't have your WAN IP in pfSense then.
This prevent using Dyndns from pfSense and you dont see your actual WAN status, e.g. if you're connected with your ISP or not… -
I never did notice that trailing '&' before. Added it on though and it made no difference.
ifconfig vr0 10.0.0.1/24
redir –lport 8080 --cport 80 -caddr 10.0.0.2 &
[1] 98991
addr: host unknown.
My modem is definatly 10.0.0.2, just verified it again by connecting my laptop up to it. Subnet mask is 255.255.255.0, could this be causing problems?
-
I don't think you need that redir at all since you are using PPPoE with pfSense just set WAN(vr0) with the ip disable the option to block private networks on pfSense if you have not done already and just set up and advanced nat if you're using another subnetwork scheme on you LAN to nat your ip to 10.0.0.0/24 if you're trying to reach port 80.
This should work.
-
I don't think you need that redir at all since you are using PPPoE with pfSense just set WAN(vr0) with the ip …
Everything you send out the WAN is encapsulated in PPPoE. This should not work.
-
My modem is definatly 10.0.0.2, just verified it again by connecting my laptop up to it. Subnet mask is 255.255.255.0, could this be causing problems?
It shouldn't matter on which (private) subnet the modem responds to and the net mask if /24. Mine is on 192.168.1.1 and it works. Even without disabling 'block private networks'.
Are you sure vr0 is the real interface that WAN is assigned to?I'm a bit clueless here…
-
It shouldn't matter on which (private) subnet the modem responds to and the net mask if /24. Mine is on 192.168.1.1 and it works. Even without disabling 'block private networks'.
Are you sure vr0 is the real interface that WAN is assigned to?Yes
It should be noted i'm running 1.2RC3, built on Wed Nov 7 19:10:57 EST 2007. I should probably update that.
-
10.0.0.2 (and 10.0.1.3) are your DNS servers on WAN as well.
What the heck is your ISP doing there? -
10.0.0.2 (and 10.0.1.3) are your DNS servers on WAN as well.
What the heck is your ISP doing there?Thats not my ISP, thats me. For some reason, DNS dosen't get passed through to pfSense, so I set it as 10.0.1.3 (Primary server on the wan side) and 10.0.0.2 (old router that this modem setup replaced). Reverted it to just 10.0.1.3, with the option to have it overidden enabled.
Edit: Updated to latest snapshot (1.2-RC3 built on Mon Nov 26 14:47:57 EST 2007) and it now gets my ISP DNS servers on vr0, or it could have been the reboot I don't know, I was pressing disconnect/connect last time and not getting the ISP dns.