PPPoE configuration!?



  • Hi,

    Sorry about my english, is not good but I think you will understand me!

    I have problem with configure PPPoE. My router is TP-LINK and I had set them in bridge mode. In pfSense WAN is set on PPPoE. Ip for TP-LINK is 192.168.1.1. What all I must adjust in order to internet work properly?



  • @KaSper(S)ky:

    I have problem with configure PPPoE. My router is TP-LINK and I had set them in bridge mode. In pfSense WAN is set on PPPoE. Ip for TP-LINK is 192.168.1.1. What all I must adjust in order to internet work properly?

    More information would be useful: What have you tried and what has been the outcome?

    Is the TP-Link an ADSL Modem/router?



  • Yes, TP-LINK is ADSL Modem-Router (TD-8811). I want that all processes switch to pfSense PC, and that I can do everything on the internet as with the TP-LINK (download via Torrent, use ftp conection on total commander , open all sites, use skype, voip….without any restrictions.).

    I want this ==>

    How to configure pfSense that this work? Please step by step! I have pfSense 1.2.3. :(



  • Nice drawing!

    However there are a few problems:
    1. If the pfSense WAN interface is really using PPPoE then it shouldn't have an IP address assigned.
    2. The WAN subnet and the LAN subnet should have different network addresses. If you are using DHCP on the LAN network then it could be easier to change the LAN subnet to (say) 192.168.5.0/24 than change the IP address of the modem/router.
    3. pfSense 1.2.3 was superseded by 2.0 which was in turn superseded by pfSense 2.0.1 some months ago. Is there a very good reason not to use up to date pfSense? The pfSense 1.2.3 instructions to access an ADSL modem on the pfSense WAN side are different from the pfSense 2.x instructions.

    Have you read any of the pfSense tutorials or configuration guides (see http://doc.pfsense.org)? You will find there (in a FAQ or How-to) a guide for configuring pfSense to allow access to web server in a ADSL modem.



  • 1. 2. I undestand.
    3. pfSense 2.0.1 cant work to me. After installation I cant accsess to pfSense settings in internet browser.

    Yes, I read some tutorial but I can not dispense. Can you help me to configure pfSense 1.2.3 step by step please?

    What is most important that I set up?

    WAN:

    username: my username
    password: my password
    MTU: 1480
    periodic reset: ?
    Dial on demand: ?
    Idle timeout: ?

    LAN:

    bridge with: LAN
    IP Adress: 192.168.1.4/24

    I have this set up now, what else should I adjust?



  • @KaSper(S)ky:

    I have this set up now, what else should I adjust?

    I would work with pfSense 2.0.1 (or even a snapshot of pfSense 2.1 which is still in development) because, as time goes by, it will become increasingly difficult to persuade people to seriously look at any problems you might encounter in pfSense 1.2.3.

    If you ever want to troubleshoot something in the modem it will have to have an IP address that is not on the LAN subnet. Therefore I would change the pfSense LAN interface to have IP address 192.168.4.1/24. (It is possible having the modem configured with an IP address on the pfSense LAN subnet may have caused the problem you had with pfSense configuration but there isn't enough information to say definitely.)

    I would configure all the LAN clients to use DHCP, though I would reserve the possibility of using a static IP address temporarily on one client for initial pfSense configuration.

    I suggest you take the following steps AFTER reading through this list to make sure you understand them all and where they are going.
    1. Disconnect pfSense box from modem and change pfSense WAN interface to have static IP address 192.168.8.2/24
    2. Make sure pfSense LAN interface is bridged with "NONE"
    3. Upgrade pfSense firmware to version 2.0.1 (or later)
    4. Access pfSense web GUI from LAN interface. If that fails then try using https (or http, depending on what you tried first). If that doesn't work report the URL you were using and what the browser reported. Don't waste your time and our time by reporting "it didn't work".

    When you get that far we'll go through configuring DHCP on the LAN side so we can add the modem on the WAN interface so its web server can be accessed and then we'll configure PPPoE.



  • Hi

    I installed a fresh version of pfSense 2.1 developer. Installation proceeded correctly, without any problems. I set the ip addresses that you told me but I still have a problem with access via web browser.

    What should I do? The same problems with version 2.0.1 and version 2.1.



  • Thanks for the extra details.

    Sorry, I left out a part. The system you are using to access the pfSense web GUI needs to be directly connected (or connected through a switch) to the pfSense LAN interface and have an IP address on the 192.168.4.0/24 subnet, for example, 192.168.4.10.
    It is possible that after changing the IP address you might need to reboot the system from which you access the pfSense web GUI so the networking is properly initialised. Once this is done you should be able to get a ping response from the IP address of the pfSense LAN interface.

    I'm sorry I didn't write this more clearly. I didn't expect you would be changing the IP address of the pfSense LAN interface. That wasn't in the step by step instructions but it was something in my mind to do at a later stage. I can see that mentioning it when it did could cause confusion. But now that it is done lets stick with that.



  • In other words, check with ipconfig / ifconfig what is your current ip, and if it ain't .4 subnet then refresh your dhcp address or reboot your computer



  • @wallabybob:

    Thanks for the extra details.

    Sorry, I left out a part. The system you are using to access the pfSense web GUI needs to be directly connected (or connected through a switch) to the pfSense LAN interface and have an IP address on the 192.168.4.0/24 subnet, for example, 192.168.4.10.

    I know it.

    Problem is the same.



  • Seemingly trivial details can be important.

    Why are you showing me a screenshot of failed attempt to access the web server at 192.168.4.2 when your screenshots clearly show the pfSense LAN interface configured at 192.168.4.1? Typo you didn't notice OR is there a configuration change you didn't think was important enough to mention?

    Why doesn't your Windows client have a Default Gateway configured? (It should be the IP address of the pfSense LAN interface.) I don't know that Windows networking needs to have a Default Gateway or what you are currently trying to do but it will need a default gateway for you to be able to access the internet.



  • The first picture was the ip address 192.168.4.1, and later I changed to the 192.168.4.2. I dont set up default getway because I dont know which ip address should be standing there. I just trying to log in via web browser on pfSense. Version 1.2.3 works fine while 2.0.1 is not. That's why I asked for help with the setup version 1.2.3.



  • @KaSper(S)ky:

    The first picture was the ip address 192.168.4.1, and later I changed to the 192.168.4.2.

    Later changed what to 192.168.4.2? Clearly you changed the IP address you told the browser but did you also change the IP address of the pfSense LAN interface?

    And why did you change what you changed?

    On the information you have supplied I'm left believing you have your pfSense LAN interface with IP address 192.168.4.1 and you are attempting to access the pfSense web interface by accessing IP address 192.168.4.2 and complaining you can't access it. If you can't see what is wrong with that combination then you are out of your depth and probably need to get help from someone who can sit beside you and watch what you are doing and challenge you immediately you do something "unusual".

    Maybe you just "forgot" to say you had also changed the pfSense LAN interface IP address to 192.168.4.2. If you repeatedly give me incorrect information or "forget" to tell me you just made a change or a few changes to my suggestions then I'm likely to feel my time would be better spent working with someone who provides accurate configuration data and closely follows my suggestions and tells when they do something different and why they did something different.

    @KaSper(S)ky:

    I dont set up default getway because I dont know which ip address should be standing there.

    I hope you know now what the default gateway IP address should be.

    @KaSper(S)ky:

    Version 1.2.3 works fine while 2.0.1 is not. That's why I asked for help with the setup version 1.2.3.

    I would be very happy to step aside if another reader wants to help you with pfSense 1.2.3. I'm not prepared to give you any assistance with pfSense 1.2.3.


Log in to reply