Could anyone help me assign IPs to interfaces?



  • Hey guys I need a bit of help. I am using pfsense 2.2 RC and am trying to configure the interfaces with IP addresses so that I can access pfsense through the Web thing but I can't get it to work. I'll list in detail the steps I have taken and maybe you guys can see what I am doing wrong?

    What I have done -
    I have already assigned interfaces, ath0 (build in Lan in mobo) to be WAN and em0 (Intel 82571 chipset pci network adapter -I have two of the but only one is being recognized).

    When of sense boots I select option 2 and configure the LAN interface. For new lan ipv4 address I enter 192.168.12.1
    For subnet I put 24.
    when it asks for a new lan ipv4 upstream gateway address I put in enter for none (I have tried putting a gateway address but it does nothing either)
    For lan ipv6 address I hit enter for none.
    I then enable DHCP server. Start address is 192.168.12.3 and end address is 192.168.12.248
    I do not revert to Http protocol.

    For WAN, it's the same steps however I have a block of 5 sattic IPs from my ISP so for the Wan interface I assign it one of my 5 wan ips.
    For subnet I put 24 as well.
    For gateway address I put my wan gateway provided by my ISP.
    nothing for ipv6 and I tell it I do not want dhcp.

    When I go to hook up an ethernet cable to my laptop (runs Manjaro/arch linux) I am not able to get an ip or access the Webconfigurator (https:/192.168.12.1), I also can access the web. If I go into the network settings and assign it an ip like 192.168.12.2, it still won't work.



  • So it turns out I had the lan cable plugged inot the wrong port when trying to connect from the laptop. Now I get an IP via DHCP but I still can't access https://192.168.12.1 or ping 192.268.12.1

    EDIT: alright so I am a bit confused. If I tell pfsense to configure the ipv4 address of the wan interface via dhcp and I give the lan interface something like 192.168.12.1 then I am able to access pfsense webconfigurator. Does pfsense require both wan and lan be on the same subnets? Is what I was trying to do in OP be done via NAT instead?

    Edit2: nvm I got it.



  • If you have static ips from your ISP you need to assign one to the WAN interface.
    My isp will not give dhcp if you have static.

    So assign one address to the WAN interface.
    lets say its 78.96.151.93 /29
    hen you need to input your gateway address to your isp.
    lets say thats 78.96.151.94

    Do not use /24 for your wan interface since you only have 5 ips to use.
    It should be a /29

    Assign 192.168.12.1/24 to the lan interface, do not select an gateway.

    Access the pfsense box on the lan interface.

    Make sure you connect your isp modem to the WAN interface and your switch to the LAN interface.
    You can setup DHCP for the LAN interface.

    That should do it.



  • @Heimire:

    If you have static ips from your ISP you need to assign one to the WAN interface.
    My isp will not give dhcp if you have static.

    So assign one address to the WAN interface.
    lets say its 78.96.151.93 /29
    hen you need to input your gateway address to your isp.
    lets say thats 78.96.151.94

    Do not use /24 for your wan interface since you only have 5 ips to use.
    It should be a /29

    Assign 192.168.12.1/24 to the lan interface, do not select an gateway.

    Access the pfsense box on the lan interface.

    Make sure you connect your isp modem to the WAN interface and your switch to the LAN interface.
    You can setup DHCP for the LAN interface.

    That should do it.

    Thank you for spending the time and assistinget me. So I have followed your advice and set the wan interface's IP and gateway appropriately as well as set it with the subnet of 29 instead of 24. I then connected via ether net cable the wan interface to my modem and for lan I only hooked up the laptop straight to the pfsense box for now. However, the problem is that on the pfsense Web configuration the wan interface shows that it is down but the lan interface is up. It is also saying no carrier, why is this?

    IMPORTANT Aedit: alright so the way I had it set up, was that the wan interface was assigned to the built in chipset/port from my motherboard and the LAN was assigned on a port on an hp nc364t (this nic uses a Intel 82571 chipset which is supported, I am using pfsense 2.2 rc). So either pfsense 2.2 is incompatible with the built in motherboard chipset (Intel I217-V) OR its incompatible with having a Wan and lan interface on separate chipsets.


  • LAYER 8 Netgate

    Have your modem plugged into the wrong interface?  Bad cable?



  • @Heimire:

    If you have static ips from your ISP you need to assign one to the WAN interface.

    That isn't a universal truth but depends on the ISP.

    I believe multiple ISPs (especially those targeting households more than businesses) use "fixed" dynamically allocated addresses. You always get the same address on the specific connection but you have to use DHCP. If your equipment doesn't request the address from the DHCP-server, the routing out on the internet doesn't work.

    If I'm not wrong, at least ISPs Bredbandsbolaget and Ownit in Sweden use "fixed" adresses but with this DHCP-requirement.

    The reason for this policy is probably that it simplifies support when having many non-professional customers.


  • Netgate Administrator

    Mmm. Some other ISPs seem to offer a subnet of fixed IPs and an additional dynamic IP to use as the WAN to which the static IPs are then routed.

    @altiris:
    So are you up and running? You have said 'never mind I got it' but it looks like you didn't solve the problem?
    Your mentioning of ath0 as WAN looks wrong, ath0 is a wireless interface.
    The i217v should be supported under 2.2RC as far as I know.
    There is no restriction on using different NIC types for WAN and LAN (or any other interface).

    Steve



  • @stephenw10:

    Mmm. Some other ISPs seem to offer a subnet of fixed IPs and an additional dynamic IP to use as the WAN to which the static IPs are then routed.

    @altiris:
    So are you up and running? You have said 'never mind I got it' but it looks like you didn't solve the problem?
    Your mentioning of ath0 as WAN looks wrong, ath0 is a wireless interface.
    The i217v should be supported under 2.2RC as far as I know.
    There is no restriction on using different NIC types for WAN and LAN (or any other interface).

    Steve

    EAverything is up and running so yes. I didn't really solve the problem that's true, I just avoided it but I think it's some type of restriction in pfsense but you say otherwise so I have to test a bit more. Ah wait a minute! I just noticed the motherboard I have also has a wireless interface (it has these two gold colored pins that I can attach an antenna), so maybe what I thought was ath0 (I thought it was the built in port on mobo) is actually that wireless thing. That makes sense, and I didn't know freebsd supported it. Now the question is how do I find the interface of the built in chipset on mobo, I remebet someone gave me a command to list devices or something, I'll try that and report back. Thank you.



  • Yes, ath0 is a wireless device, as you have guessed.
    On the webGUI, go to Interfaces->(assign)
    Available Network Ports dropdown at the bottom will show you the device names of any unassigned network devices that pfSense knows about.


Log in to reply