4. OPT1 not working

OPT1 not working

  • C

    Hello o/

    I'm not sure into which subforum this fits, so I'm putting it here.

    My Situation:
    I installed pfSense on an "old" computer of mine. With a realtek onboard nic and I bought two aditional (cheap) NICs (D-Link DFE-528TX).
    Then I went ahead and installed and configured pfSense. I got the WAN interface working wit pppoe for my ADSL connection and I got the LAN1 working for my network with DHCP and everything. I left the OPT1 interface deactivated. I also added, after everything was working, the squid proxy, which is also working as expected.
    WAN and LAN1 are configured and working.
    Today I decided to activate OPT1. I set it up for a different IP and activated DHCP for the range on opt1.
    I also added a firewall rule that was basicaly allow any.

    The Problem:
    OPT1 is not working. It is shown as up and with the correct configuration in the webinterface and via ifconfig.
    When a cable is connected the card notices it. And I know that the nic and the cable i used are working.
    The connected client does not recieve anything from the dhcp. And after manual IP configuration on the client i cant ping the pfsense box from there either.

    The switch I connected to the pfsense box on OPT1 shows only the light for 10base on the port the pfsense box is connected not 100, though pfsense says it is operating with "100baseTX <full-duplex>".

    http://i.imgur.com/JAgTa.png http://i.imgur.com/rho9E.png http://i.imgur.com/fYTax.png</full-duplex>

    0
  • S

    What version are you using?

    You have 3 interfaces as I understand

    What is your built in NIC configured for? WAN? LAN?
    and also you additional NICs, what are the configured for?

    You can try to diagnose the problem by going to "interfaces" and then the interface in question, then chose "speed and duplex" and try setting a different option, try playing with the 10baseT* stuff to see if you get connectivity.

    0
  • S

    Something just came to mind which happened to me ages ago….with the problem NIC if its not the one thats built in, try putting it in another pci slot

    0
  • G

    Where is the picture of the LAN interface Status screen?

    0
  • W

    Do you see the DHCP requests in the pfSense log (Status -> System Logs, click on DHCP tab)?

    If not, do you see the DHCP requests in the firewall log? (Status -> System Logs, click on Firewall tab)

    f not, do you see the DHCP requests in a packet capture on OPT1?

    0
  • C

    Thanks for the replys!

    I'm using 2.0.2-RELEASE (i386)

    The onboard NIC is a realtek chipset with gigabit ethernet. Thats used for LAN1.
    WAN is one of the two dlink nics (rl1).
    And OPT1 is supposed to be the second dlink nic (rl0).

    You can try to diagnose the problem by going to "interfaces" and then the interface in question, then chose "speed and duplex" and try setting a different option, try playing with the 10baseT* stuff to see if you get connectivity.

    I tried different settings there, still no conectivity in any way. However it now gets recognized by the switch as 100base. Even with the standard "autoselect" Option and 100baseTX <full-duplex>.

    try putting it in another pci slot

    Using a different pci slot did not help either.

    Where is the picture of the LAN interface Status screen?

    http://i.imgur.com/abQJI.png

    $ ifconfig
re0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=3898 <vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic>ether 00:25:22:8f:53:25
	inet 10.0.0.1 netmask 0xff000000 broadcast 10.255.255.255
	inet6 fe80::225:22ff:fe8f:5325%re0 prefixlen 64 scopeid 0x1 
	nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
fwe0: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
	options=8 <vlan_mtu>ether 02:8f:13:fa:0b:00
	ch 1 dma -1
fwip0: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
	lladdr 0.8f.13.0.7b.fa.b.0.a.2.ff.fe.0.0.0.0
rl0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=8 <vlan_mtu>ether 5c:d9:98:a7:6e:a7
	inet6 fe80::5ed9:98ff:fea7:6ea7%rl0 prefixlen 64 scopeid 0x4 
	inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
	nd6 options=43 <performnud,accept_rtadv>media: Ethernet 100baseTX <hw-loopback>
	status: active
plip0: flags=8810 <pointopoint,simplex,multicast>metric 0 mtu 1500
pfsync0: flags=0<> metric 0 mtu 1460
	syncpeer: 224.0.0.240 maxupd: 128 syncok: 1
pflog0: flags=100 <promisc>metric 0 mtu 33200
enc0: flags=0<> metric 0 mtu 1536
lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
	options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x9 
	nd6 options=43 <performnud,accept_rtadv>pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492
	inet XXX.XXX.XXX.XXX --> XXX.XXX.XXX.XXX netmask 0xffffffff 
	inet6 XXX:5325%pppoe0 prefixlen 64 scopeid 0xa 
	nd6 options=43<performnud,accept_rtadv></performnud,accept_rtadv></up,pointopoint,running,noarp,simplex,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></promisc></pointopoint,simplex,multicast></hw-loopback></performnud,accept_rtadv></vlan_mtu></up,broadcast,running,simplex,multicast></broadcast,simplex,multicast></vlan_mtu></broadcast,simplex,multicast></full-duplex></performnud,accept_rtadv></vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic></up,broadcast,running,simplex,multicast>

    Do you see the DHCP requests in the pfSense log (Status -> System Logs, click on DHCP tab)?

    If not, do you see the DHCP requests in the firewall log? (Status -> System Logs, click on Firewall tab)

    f not, do you see the DHCP requests in a packet capture on OPT1?

    No, no and no.

    Aside from the standard:

    Jan 10 21:31:42	dhcpd: Listening on BPF/rl0/5c:d9:98:a7:6e:a7/192.168.0.0/24
Jan 10 21:31:42	dhcpd: Sending on BPF/rl0/5c:d9:98:a7:6e:a7/192.168.0.0/24

    and occasional:

    
Jan 10 21:52:10	OPT1	   192.168.2.1	   224.0.0.1	IGMP

    nothing on OPT1. The packet capture only records PPPoE packets on OPT1.

    What I noticed earlier after a reboot (when I did not yet had OPT1 activated) was that it switched both "rlX" interfaces and suddenly used the other NIC as WAN.
    That is why WAN is on rl1 and not on rl0. While PPPoE over WAN was still on rl0 it was working just as well as it does now over rl1.

    Sorry for my bad english :/</full-duplex>

    0
  • W

    @carlos456:

    The packet capture only records PPPoE packets on OPT1.

    PPPoE transmitted or received? That doesn't seem right.

    @carlos456:

    What I noticed earlier after a reboot (when I did not yet had OPT1 activated) was that it switched both "rlX" interfaces and suddenly used the other NIC as WAN.
    That is why WAN is on rl1 and not on rl0. While PPPoE over WAN was still on rl0 it was working just as well as it does now over rl1.

    Why doesn't rl1 appear in the ifconfig output you posted earlier?

    Perhaps when you added a card the new card became rl0 and the card previously in the system became rl1. (The unit number is assigned according to the order in which the devices are seen as the systems walks the PCI device tree. Hence adding a new device can easily cause existing devices to be renumbered.)

    If you are expecting to serve DHCP requests on OPT1 you almost certainly shouldn't be seeing PPPoE traffic on OPT1. But packet capture generally put an interface into "promiscuous" mode which can cause the display of traffic a device would not normally receive. What do have connected to OPT1? Please provide a network diagram.

    Note you can attach graphics to replies by clicking on the Additional Options link just below the reply composition box. (It is easier for the readers if they can see graphics "inline" rather than having to open a new web page.)

    0
  • C

    @wallabybob:

    PPPoE transmitted or received? That doesn't seem right.

    00:14:24.980423 PPPoE  [ses 0x275d] IP 65.31.218.243.51413 > 77.12.xxx.xxx.35388: UDP, length 94
00:14:25.714079 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 51231, length 44
00:14:25.714107 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 51487, length 44
00:14:25.746101 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 51231, length 44
00:14:25.747362 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 51487, length 44
00:14:25.920435 PPPoE  [ses 0x275d] IP 46.129.125.233.7475 > 77.12.xxx.xxx.31856: UDP, length 101
00:14:26.714668 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 51743, length 44
00:14:26.746649 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 51743, length 44
00:14:27.714927 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 51999, length 44
00:14:27.746493 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 51999, length 44
00:14:28.003618 PPPoE  [ses 0x275d] IP 177.42.242.64.10000 > 77.12.xxx.xxx.31856: UDP, length 117
00:14:28.640683 PPPoE  [ses 0x275d] IP 82.233.196.188.51413 > 77.12.xxx.xxx.63159: UDP, length 94
00:14:28.714877 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 52255, length 44
00:14:28.746270 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 52255, length 44
00:14:29.348673 PPPoE  [ses 0x275d] IP 168.234.49.206.22222 > 77.12.xxx.xxx.33635: UDP, length 106
00:14:29.379210 PPPoE  [ses 0x275d] IP 109.226.112.34.43723 > 77.12.xxx.xxx.33635: UDP, length 106
00:14:29.715818 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 52511, length 44
00:14:29.747170 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 52511, length 44
00:14:30.093476 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.41114 > 194.95.249.23.36653: UDP, length 0
00:14:30.125589 PPPoE  [ses 0x275d] IP 195.71.188.118 > 77.12.xxx.xxx: ICMP time exceeded in-transit, length 36
00:14:30.623444 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.41114 > 194.95.249.23.36653: UDP, length 0
00:14:30.655047 PPPoE  [ses 0x275d] IP 195.71.188.118 > 77.12.xxx.xxx: ICMP time exceeded in-transit, length 36
00:14:30.715857 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 52767, length 44
00:14:30.747631 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 52767, length 44
00:14:31.292159 PPPoE  [ses 0x275d] IP 87.237.39.199.443 > 77.12.xxx.xxx.2131: tcp 27
00:14:31.292433 PPPoE  [ses 0x275d] IP 87.237.39.199.443 > 77.12.xxx.xxx.2131: tcp 0
00:14:31.293828 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.2131 > 87.237.39.199.443: tcp 0
00:14:31.354514 PPPoE  [ses 0x275d] IP 87.237.39.199.443 > 77.12.xxx.xxx.2131: tcp 0
00:14:31.383325 PPPoE  [ses 0x275d] IP 46.129.125.233.7475 > 77.12.xxx.xxx.31856: UDP, length 101
00:14:31.684175 PPPoE  [ses 0x275d] IP 54.243.128.92.443 > 77.12.xxx.xxx.53418: tcp 37
00:14:31.684445 PPPoE  [ses 0x275d] IP 54.243.128.92.443 > 77.12.xxx.xxx.53418: tcp 0
00:14:31.685775 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.53418 > 54.243.128.92.443: tcp 0
00:14:31.715866 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 53023, length 44
00:14:31.747954 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 53023, length 44
00:14:31.892392 PPPoE  [ses 0x275d] IP 5.9.202.82.5222 > 77.12.xxx.xxx.44462: tcp 282
00:14:31.949130 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.44462 > 5.9.202.82.5222: tcp 0
00:14:32.364844 PPPoE  [ses 0x275d] IP 46.129.125.233.7475 > 77.12.xxx.xxx.31856: UDP, length 101
00:14:32.715892 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 53279, length 44
00:14:32.747977 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 53279, length 44
00:14:33.212386 PPPoE  [ses 0x275d] IP 189.18.96.51.2521 > 77.12.xxx.xxx.32448: UDP, length 103
00:14:33.718819 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 53535, length 44
00:14:33.750506 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 53535, length 44
00:14:34.723808 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 53791, length 44
00:14:34.755470 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 53791, length 44
00:14:35.148597 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 572
00:14:35.149380 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 1430
00:14:35.161626 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 459
00:14:35.207351 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 37
00:14:35.224477 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 0
00:14:35.237910 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 0
00:14:35.310372 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 67
00:14:35.311929 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 1350
00:14:35.312729 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 0
00:14:35.313350 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 1350
00:14:35.314425 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 1203
00:14:35.314705 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 306
00:14:35.334937 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 0
00:14:35.348523 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 494
00:14:35.349367 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 1430
00:14:35.351268 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 1430
00:14:35.382191 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 556
00:14:35.418480 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 0
00:14:35.440739 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 0
00:14:35.475636 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 53
00:14:35.476388 PPPoE  [ses 0x275d] IP 74.125.230.227.443 > 77.12.xxx.xxx.63923: tcp 514
00:14:35.477856 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.63923 > 74.125.230.227.443: tcp 0
00:14:35.679160 PPPoE  [ses 0x275d] IP 46.129.125.233.7475 > 77.12.xxx.xxx.31856: UDP, length 101
00:14:35.728816 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 54047, length 44
00:14:35.760949 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 54047, length 44
00:14:36.147163 PPPoE  [ses 0x275d] IP 74.125.230.248.443 > 77.12.xxx.xxx.25527: tcp 61
00:14:36.147503 PPPoE  [ses 0x275d] IP 74.125.230.248.443 > 77.12.xxx.xxx.25527: tcp 41
00:14:36.147657 PPPoE  [ses 0x275d] IP 74.125.230.248.443 > 77.12.xxx.xxx.25527: tcp 0
00:14:36.148705 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.25527 > 74.125.230.248.443: tcp 0
00:14:36.149036 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.25527 > 74.125.230.248.443: tcp 0
00:14:36.149507 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.25527 > 74.125.230.248.443: tcp 0
00:14:36.201688 PPPoE  [ses 0x275d] IP 74.125.230.248.443 > 77.12.xxx.xxx.25527: tcp 0
00:14:36.705746 PPPoE  [ses 0x275d] IP 41.132.178.36.59008 > 77.12.xxx.xxx.33635: UDP, length 103
00:14:36.733819 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 54303, length 44
00:14:36.765706 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 54303, length 44
00:14:37.235726 PPPoE  [ses 0x275d] IP 82.215.231.67.18359 > 77.12.xxx.xxx.31856: UDP, length 117
00:14:37.738827 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 54559, length 44
00:14:37.758897 PPPoE  [ses 0x275d] IP 5.9.202.82.5222 > 77.12.xxx.xxx.44462: tcp 266
00:14:37.770681 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 54559, length 44
00:14:37.819487 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.44462 > 5.9.202.82.5222: tcp 0
00:14:38.407151 PPPoE  [ses 0x275d] IP 46.129.125.233.7475 > 77.12.xxx.xxx.31856: UDP, length 101
00:14:38.743815 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 54815, length 44
00:14:38.775204 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 54815, length 44
00:14:39.127922 PPPoE  [ses 0x275d] IP 219.92.128.206.27049 > 77.12.xxx.xxx.4799: UDP, length 103
00:14:39.164138 PPPoE  [ses 0x275d] IP 93.1.252.80.15005 > 77.12.xxx.xxx.33635: UDP, length 103
00:14:39.748842 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 55071, length 44
00:14:39.780919 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 55071, length 44
00:14:40.194988 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.26875 > 8.8.8.8.53: UDP, length 35
00:14:40.257414 PPPoE  [ses 0x275d] IP 8.8.8.8.53 > 77.12.xxx.xxx.26875: UDP, length 110
00:14:40.588203 PPPoE  [ses 0x275d] IP 207.134.230.99.2983 > 77.12.xxx.xxx.33635: UDP, length 103
00:14:40.753792 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 55327, length 44
00:14:40.786364 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 55327, length 44
00:14:41.166535 PPPoE  [ses 0x275d] IP 46.129.125.233.7475 > 77.12.xxx.xxx.31856: UDP, length 101
00:14:41.686129 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx.53418 > 54.243.128.92.443: tcp 0
00:14:41.758674 PPPoE  [ses 0x275d] IP 77.12.xxx.xxx > 213.20.59.135: ICMP echo request, id 31260, seq 55583, length 44
00:14:41.790344 PPPoE  [ses 0x275d] IP 213.20.59.135 > 77.12.xxx.xxx: ICMP echo reply, id 31260, seq 55583, length 44

    This is how the capture on OPT1 looks.
    @wallabybob:

    Why doesn't rl1 appear in the ifconfig output you posted earlier?

    Perhaps when you added a card the new card became rl0 and the card previously in the system became rl1. (The unit number is assigned according to the order in which the devices are seen as the systems walks the PCI device tree. Hence adding a new device can easily cause existing devices to be renumbered.)

    If you are expecting to serve DHCP requests on OPT1 you almost certainly shouldn't be seeing PPPoE traffic on OPT1. But packet capture generally put an interface into "promiscuous" mode which can cause the display of traffic a device would not normally receive. What do have connected to OPT1? Please provide a network diagram.

    Note you can attach graphics to replies by clicking on the Additional Options link just below the reply composition box. (It is easier for the readers if they can see graphics "inline" rather than having to open a new web page.)

    I assumed for the whole time that "rl1" became "pppoe0" when I setup the PPPoE connection for WAN!?
    I just looked into "Interfaces >> Assign" and there it lists for WAN PPPOE0(rl0).
    So if it is using "rl0" for pppoe0 (and therefor WAN) and also as OPT1 then really, where is rl1? :P

    The Image shows how I want the "Network" to be. Nothing fancy.


    0
  • W

    @carlos456:

    So if it is using "rl0" for pppoe0 (and therefor WAN) and also as OPT1 then really, where is rl1? :P

    Please post the output of pfSense shell commands```
    ifconfig
    /etc/rc.banner

    0
  • C

    Success!!! :D
    Okay, after i just realized that WAN/PPPOE actually was on rl0 and not how I assumed the whole time on rl1.
    I went looking for the now missing rl1 and could not find it in the system.  I then plugged the "rl1" nic back into the pci slot it has been in before and then it got detected again by pfsense.
    So the only problems there really were, were that i am dumb :P and that something is wrong with one of my pci slots :/
    WAN, LAN1 and OPT1 are now working as intended! :)

    Thanks for all the help!!! <3

    0
Log in to reply
 

Products

Services

Support

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive for past announcements.

© 2020 Rubicon Communications, LLC | Privacy Policy