TippingPoint 330 (HP S330)

[NetworKing16]

I did as you described got the bios to update. Did update I heard the relays switch when it re-booted. I then had link light on the ports. Some reason though when I went into shell and did ifconfig it shows as disconnected. I used this same thing to check the mgmt port (em4) and it would show connected. Almost makes me think I have a little more work to do making all the relays trip or maybe it needs some sort of driver for these other NIC cards to work. <ay be="" i="" just="" need="" to="" reboot="" again="" too.="" <br="">I saw a few jumpers on it too that were not marked, one was in the very front by the mgmt port, and I think was one other, maybe these have something to do with the relays, etc.</ay>

[stephenw10]

Hmm, can you access the settings in the BIOS now?

If you see link LEDs on the ports I would think they are connected to the PHYs. If the PHYs were somehow not connected to the NIC chips it might appear like that but I thought the LEDs are usually controlled by the NICs.

Hmmm.

[NetworKing16]

I need to do some more research into this in the next few days. I did try connecting to ports before and had no light, until now I assume related to the relay connections. I have not looked at the bios I didn't notice that it was any different than before and there was no settings, etc to change in the OEM BIOS. May just need a good reboot too, or maybe that port is just bad.

[NetworKing16]

I am working on the unit right now and still not sure what is going on. I went in via console and GUI to the I.P I sat on EM4 (WAN) originally.  The system boot,s I hear relay click, the nic lights flash. I went into the GUI and CLI and all the interfaces besides EM4 show as being down. I set up all the interfaces in the GUI for LAN, WAN, opt, etc.

I tried a different port and still nothing showing in status that it is connected. After I flashed the bios I rebooted it, it still didn't work, relays never tripped I then did the CMOS reset on it and then it worked. Maybe I still have something holding over from that, or maybe I corrupted the bios with the improper reboot.

I tried to get into the BIOS, but no idea what key or command I would use to access it. Testing all the ports I get link and act lights on both ports in segment 1 and 2, but only get link light and NO act light on both ports in segment 3 and 4.

[stephenw10]

How do you have the additional ports configured in pfSense?

Try running ifconfig at the CLI, if the ports show the media type as, for example:

media: Ethernet autoselect (1000baseT <full-duplex>)</full-duplex> 

Then they are seeing the connection.

Having to reset the cmos after flashing the bios is expected. Probably only the default settings for the by-pass relays were changed so they need to be wiped and regenerated to the new default values.

Try pressing TAB to enter the bios from the serial console.

Steve

[NetworKing16]

Well tried flashing bios again, reloading PFsense, even going to the X64 version, the X64 don't seem to work though because of some issue with BIOS.
I get em4 mgmt port to work, but that is all I can do anything with for some reason. They all (em1-4) appear to be Intel pro 1000 NICs V 7.6.1-K.

When I go into the shell and do ifconfig I get the below output, I have tried various ports on the S330, different cables, different switches (both 100 meg and gigabit) Still seems to do the same thing. I don't think until changed BIOS I could even get lights on the ports, now I get link lights on all ports, but only activity on ports in segmet 1 and 2.

[2.3.3-RELEASE][root@pfSense.localdomain]/root: ifconfig

igb0: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
        options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:07:99:a3:20:e2
        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
        status: no carrier

igb1: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
        options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:07:99:a3:20:e3
        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
        status: no carrier

igb2: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
        options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:07:99:a3:20:e4
        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
        status: no carrier

igb3: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
        options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:07:99:a3:20:e5
        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
        status: no carrier

em0: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
        options=4219b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic,vlan_hwtso>ether 00:07:99:a3:20:e1
        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
        status: no carrier

em1: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
        options=4209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso>ether 00:07:99:a3:20:e0
        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
        status: no carrier

em2: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
        options=4209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso>ether 00:07:99:a3:20:df
        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
        status: no carrier

em3: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
        options=4209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso>ether 00:07:99:a3:20:de
        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

em4: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
        options=4209b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso>ether 00:07:99:a3:20:dd
        inet6 fe80::207:99ff:fea3:20dd%em4 prefixlen 64 scopeid 0x9
        inet 192.168.22.225 netmask 0xffffff00 broadcast 192.168.22.255
        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

pflog0: flags=100 <promisc>metric 0 mtu 33184

pfsync0: flags=0<> metric 0 mtu 1500
        syncpeer: 224.0.0.240 maxupd: 128 defer: on
        syncok: 1

lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
        options=600003 <rxcsum,txcsum,rxcsum_ipv6,txcsum_ipv6>inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0xc
        nd6 options=21 <performnud,auto_linklocal>enc0: flags=0<> metric 0 mtu 1536
        nd6 options=21 <performnud,auto_linklocal>[2.3.3-RELEASE][root@pfSense.localdomain]/root:</performnud,auto_linklocal></performnud,auto_linklocal></rxcsum,txcsum,rxcsum_ipv6,txcsum_ipv6></up,loopback,running,multicast></promisc></full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso></up,broadcast,running,simplex,multicast></full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></broadcast,oactive,simplex,multicast>

[stephenw10]

What was connected and how when you took that output?

You have em4 and em3 showing as up correctly there. When interface do you have assigned in pfSense? It looks like only em4 has a static IP right now.

Steve

[NetworKing16]

I was just using the port A of segment 1,2,3. I think I see what you mean there where it says no carrier or active. I am more used to looking at CLI output from Cisco gear, so I was expecting the part at the top to say something like up, connected, speed, etc. Sort if like EM4 shows.

[stephenw10]

Yes, if it shows a media state and status as active the driver is seeing the connection to the port.

It might be simple that the interface is not yet configured in pfSense.

Steve

[bombshellnetworks]

Ive actually seen alot of jitter online, including this thread since I made the post.  Ill see what I can do for a very detailed write up and maybe a video on flashing the BIOS.  I modded the BIOS firmware with (I think Pheonix BIOS modder?) Ill have to check my notes at the house.

Quick info:

System does refuse to boot properly with x64 image, a panic IIRC.

IIRC I couldnt get CF install to boot, had to use a SATA SSD and USB install stick.

I just changed settings in each copy of the firmware, and saved changes as defaults (so you can default the BIOS via battery or jumper to modded version)

I had to do the following to get the interfaces to work properly after flashing new BIOS (in OP):

shut system down, remove power cable, remove cmos batt and move JP2 to 2-3 position and wait 5 mins.
Move jumper back to 1-2, and install battery, reboot.  It should kill off once, and reboot.

[bombshellnetworks]

I used AMIBCP V3.46 below are some screenshots and pics of the system.  You can see the jumpers, type of BIOS, and the bypass relays:

[NetworKing16]

I did manage to get working. In my messing around I ended up trying the RESET button on the S330 It ended up basically corrupting PFsense and had to re-load it. Tried reload many times doing similar to before, no swap, etc. No luck. Ended up just finding an old 80GB SATA HDD and loading on that I can only assume the CF card was corrupted or had sector issues.

I then set the various interfaces, the setup was sort of strange to me and what I was expecting. I was a bit surprised that setting an I.P for EM4(mgmt interface) did not work but can manage from the LAN interface. Maye some sort of ACL, etc in play, but seems would be nice to use the mgmt port as it was meant to be used. I also set the other segments as optional interfaces, but not sure yet these can be used for firewall/ NAT/ IPS interfaces like the LAN and WAN ports can be.

I think would be kind of nice if was a bit more options in PFsense for making and linking multiple LAN/WAN interfaces, or one WAN to 2 LAN E.G a DMZ and another for the intranet.

[stephenw10]

In pfSense any interface can be either an external or internal interface. It only depends on whether you set a gateway on that interface.

Only the LAN interface has any firewall rules on it by default. That is to make it easier to get started. All other interfaces will block all traffic by default.

I'm sure you can use em4 to connect to the gui for management if you wish you simply need to add a firewall rule on that interface to allow it.

Steve