TippingPoint X506 Hardware

Sifter

On that bios you could access the bios using Ctl-C via the serial console.

Steve


                 +---------------------------------------------+
                 |              Enter password:                |
                 +---------------------------------------------+

stephenw10

Awesome! Shame the bios is locked but never mind if it boot's OK. Could always try extracting the bios and looking for likely passwords later.

Is that booting the standard NanoBSD image? Strange that it's looking for root on ad2. :-
Edit: Or is it a standard install with embedded kernel?

Anyway it's actually ad0, the primary master, so at the mount root prompt enter:

ufs:/dev/ad0s1a

It should then boot.

I only see one NIC detected, sis0. I wonder how it's connected to the others ports? VLANs via a switch chip perhaps, SOHO router style.

ubsec is loaded, nice.

Steve

Sifter

I pulled a 4gig microdrive from another system that has a full install on it.

mountroot> ufs:/dev/ad0s1a
Trying to mount root from ufs:/dev/ad0s1a
WARNING: / was not properly dismounted
Configuring crash dumps...
No suitable dump device was found.
Mounting filesystems...
ZFS NOTICE: Prefetch is disabled by default on i386 -- to enable,
            add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior.
             Consider tuning vm.kmem_size and vm.kmem_size_max
             in /boot/loader.conf.
ZFS filesystem version 5
ZFS storage pool version 28
mount: /dev/ad0s1a R/W mount of / denied. Filesystem is not clean - run fsck.: Operation not permitted
** /dev/ad0s1a
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=188460 (4 should be 0)
CORRECT? yes

** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=188422  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188423  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188424  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188425  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188426  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188442  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188443  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188444  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188445  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188446  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188447  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188448  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188449  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188450  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE I=188451  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 13 23:48 2014
CLEAR? yes

UNREF FILE  I=188544  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 19 19:05 2014
RECONNECT? yes

NO lost+found DIRECTORY
CREATE? yes

UNREF FILE  I=188545  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 19 19:05 2014
RECONNECT? yes

UNREF FILE  I=188546  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 19 19:05 2014
RECONNECT? yes

UNREF FILE  I=188547  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 19 19:05 2014
RECONNECT? yes

UNREF FILE  I=188548  OWNER=root MODE=100644
SIZE=0 MTIME=Feb 19 19:05 2014
RECONNECT? yes

LINK COUNT FILE I=235668  OWNER=dhcpd MODE=100644
SIZE=673 MTIME=Feb 15 22:33 2014  COUNT 2 SHOULD BE 1
ADJUST? yes

** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? yes

SUMMARY INFORMATION BAD
SALVAGE? yes

BLK(S) MISSING IN BIT MAPS
SALVAGE? yes

6209 files, 95092 used, 1333071 free (159 frags, 166614 blocks, 0.0% fragmentation)

***** FILE SYSTEM MARKED CLEAN *****

***** FILE SYSTEM WAS MODIFIED *****
Disabling APM on /dev/ad0

     ___
 ___/ f \
/ p \___/ Sense
\___/   \
    \___/

Welcome to pfSense 2.1-RELEASE  ...

Dump device does not exist.  Savecore not run.
Creating symlinks......done.
External config loader 1.0 is now starting... ad0s1b
Launching the init system... done.
Initializing............................. done.
Starting device manager (devd)...done.
Loading configuration......done.
Warning: Configuration references interfaces that do not exist: rl0 rl3

Network interface mismatch -- Running interface assignment option.
sis0: link state changed to DOWN

Valid interfaces are:

sis0  ff:ff:ff:ff:ff:ff   (up) NatSemi DP8381[56] 10/100BaseTX

Do you want to set up VLANs first?

If you are not going to use VLANs, or only for optional interfaces, you should
say no here and use the webConfigurator to configure VLANs later, if required.

Do you want to set up VLANs now [y|n]?

Sifter

The box isnt showing me any love when I put the pfSense-2.1-RELEASE-512mb-i386-nanobsd.img.gz image on a Transcend 4gig ultra cf card.

Like literally no output on the serial, both 9600 and 115200.

Sifter

After writing the pfSense-memstick-serial-2.1-RELEASE-i386.img.gz image to a usb stick and trying to boot from it, I got the following:

TippingPoint OS, MFG version
BSP: [t10 1.2] Bootloader: [15]
Creation date: Jun  2 2006, 10:24:47

Press any key to stop auto-boot...
 0
auto-booting...

boot device          : ata=0,0
unit number          : 0
processor number     : 0
host name            : NDS
file name            : auto
flags (f)            : 0x0

Could not initialize ATA.

Error loading file: errno = 0x0.
Can't load boot file!!

stephenw10

Hmm, OK.
What baud rate do you see the locked BIOS at?

Maybe it just can't boot that card for some reason.
No booting from USB either. That's not surprising it would be big security risk if you could just plug in your own compromised OS and reboot the box without even opening it.

Can you try setting up the NICs with the microdrive?
First you need to find out if you can actually get any networkaccess at all. I aimagine it might be VLANs to whatever the chip under the heatsink is but they may require setting up via some out of band service like i2c which would be bad.

Steve

Sifter

@stephenw10:

Hmm, OK.
What baud rate do you see the locked BIOS at?

Steve

I can see the TippingPoint OS prompt and bios password prompt at 115200. When the microdrive is in, I have to close putty and reopen it at 9600 in order to see the full boot.

stephenw10

Sometimes if you're running at 115200 the bootloader sees that as some random input when it gets to the F1 prompt and then waits for you to press return which you can't because your not actually connected.
Try booting the CF card with putty at 9600 the whole time.
Also if you've just changed the boot media you sometimes have to boot twice as the first boot halts with a message about hardware change. Only the case with some BIOSes and I wouldn't expect it on something designed for embedded but still…

Steve

Sifter

Interesting, it doesnt like my Transcend Compact Flash ULTRA 4GB Industrial.

As soon as I imaged my microdrive with the pfSense-2.1-RELEASE-512mb-i386-nanobsd.img.gz image and popped it in, it booted right away.

Here is a snippet from assigning vlan interfaces.

     ___
 ___/ f \
/ p \___/ Sense
\___/   \
    \___/

Welcome to pfSense 2.1-RELEASE  ...

Creating symlinks......done.
External config loader 1.0 is now starting... ad0s3
Launching the init system... done.
Initializing............................. done.
Starting device manager (devd)...done.
Loading configuration......done.

Default interfaces not found -- Running interface assignment option.
sis0: link state changed to DOWN

Valid interfaces are:

sis0  ff:ff:ff:ff:ff:ff   (up) NatSemi DP8381[56] 10/100BaseTX

Do you want to set up VLANs first?

If you are not going to use VLANs, or only for optional interfaces, you should
say no here and use the webConfigurator to configure VLANs later, if required.

Do you want to set up VLANs now [y|n]? y

VLAN Capable interfaces:

sis0    ff:ff:ff:ff:ff:ff   (up)

Enter the parent interface name for the new VLAN (or nothing if finished): sis0
Enter the VLAN tag (1-4094): 100

VLAN Capable interfaces:

sis0    ff:ff:ff:ff:ff:ff   (up)

Enter the parent interface name for the new VLAN (or nothing if finished): sis0
Enter the VLAN tag (1-4094): 200

VLAN Capable interfaces:

sis0    ff:ff:ff:ff:ff:ff   (up)

Enter the parent interface name for the new VLAN (or nothing if finished): sis0
Enter the VLAN tag (1-4094): 300

VLAN Capable interfaces:

sis0    ff:ff:ff:ff:ff:ff   (up)

Enter the parent interface name for the new VLAN (or nothing if finished):

VLAN interfaces:

sis0_vlan100    VLAN tag 100, parent interface sis0
sis0_vlan200    VLAN tag 200, parent interface sis0
sis0_vlan300    VLAN tag 300, parent interface sis0

*NOTE*  pfSense requires *AT LEAST* 1 assigned interface(s) to function.
        If you do not have *AT LEAST* 1 interfaces you CANNOT continue.

        If you do not have at least 1 *REAL* network interface card(s)
        or one interface with multiple VLANs then pfSense
        *WILL NOT* function correctly.

If you do not know the names of your interfaces, you may choose to use
auto-detection. In that case, disconnect all interfaces now before
hitting 'a' to initiate auto detection.

Enter the WAN interface name or 'a' for auto-detection: sis0_vlan100

Enter the LAN interface name or 'a' for auto-detection
NOTE: this enables full Firewalling/NAT mode.
(or nothing if finished): sis0_vlan200

Enter the Optional 1 interface name or 'a' for auto-detection
(or nothing if finished): sis0_vlan300

Enter the Optional 2 interface name or 'a' for auto-detection
(or nothing if finished):

The interfaces will be assigned as follows:

WAN  -> sis0_vlan100
LAN  -> sis0_vlan200
OPT1 -> sis0_vlan300

Do you want to proceed [y|n]?y

Writing configuration...done.
Updating configuration...done.
Cleaning backup cache...done.
Setting up extended sysctls...done.
Setting timezone...done.
Configuring loopback interface...done.
vlan0: changing name to 'sis0_vlan100'

Starting Securevlan1: changing name to 'sis0_vlan200'
 Shell Services.vlan2: changing name to 'sis0_vlan300'
..done.
Setting up polling defaults...done.
Setting up interfaces microcode...done.
Configuring loopback interface...done.
Creating wireless clone interfaces...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring QinQ interfaces...done.
Configuring WAN interface...Generating new MAC address.done.
Configuring LAN interface...done.
Syncing OpenVPN settings...done.
Configuring firewall......done.
Starting PFLOG...done.
Setting up gateway monitors...done.
Synchronizing user settings...done.
Starting webConfigurator...done.
Configuring CRON...done.
Starting DNS forwarder...done.
Starting NTP time client...done.
Starting DHCP service...done.
Starting DHCPv6 service...done.
Configuring firewall......done.
Generating RRD graphs...done.
Starting syslog...done.
Starting CRON... done.
Bootup complete

FreeBSD/i386 (pfSense.localdomain) (console)

*** Welcome to pfSense 2.1-RELEASE-nanobsd (i386) on pfSense ***

 WAN (wan)       -> sis0_vlan100 ->
 LAN (lan)       -> sis0_vlan200 -> v4: 192.168.1.1/24
 OPT1 (opt1)     -> sis0_vlan300 ->

 0) Logout (SSH only)                  8) Shell
 1) Assign Interfaces                  9) pfTop
 2) Set interface(s) IP address       10) Filter Logs
 3) Reset webConfigurator password    11) Restart webConfigurator
 4) Reset to factory defaults         12) pfSense Developer Shell
 5) Reboot system                     13) Upgrade from console
 6) Halt system                       14) Disable Secure Shell (sshd)
 7) Ping host                         15) Restore recent configuration

Enter an option:

Sifter

@stephenw10:

Can you try setting up the NICs with the microdrive?
First you need to find out if you can actually get any networkaccess at all. I aimagine it might be VLANs to whatever the chip under the heatsink is but they may require setting up via some out of band service like i2c which would be bad.

Steve

So even after assigning vlan's 100, 200, and 300 to the sis0 interface, no interfaces come alive when I plug in a CAT5 cable to each of the 6 jacks.

Sifter

And here is our mystery chip under the heatsink.

stephenw10

Ok so as suspected a switch IC. These are normally configured via spi in soho routers but usually (often) that's only neccessary if you need to change the default config.
You can't just assign VLANs at random. Assign the sis interface directly. Run a packet capture on it. Whilst it's running send some traffic into external switch ports. Now look at the capture to see what vlans traffic arrived on. Of course you'll have to get the capture file off the box to analyse it, or do it the hard way. ;)

Steve

Sifter

@stephenw10:

You can't just assign VLANs at random. Assign the sis interface directly.

Steve

I need 2 interfaces before pfsense will proceed, do I assign one generic vlan as WAN and then assign the sis0 directly to LAN? How would you do it?

stephenw10

PfSense only requires 1 interface. But yes you could use one real interface and one VLAN interface.
The other possibility is that the default config of the switch is no vlans at all, just like an unmanaged switch.

Steve

_Adrian_

I'm keeping an eye on this thread :)

_Adrian_

I wonder if this has similar hardware :P
http://www.ebay.ca/itm/HP-Tippingpoint-Core-Controller-48-Port-Gigabit-Switch-/321258224413?pt=US_Network_Switches&hash=item4acc7b7b1d

stephenw10

Unlikely. You need some serious power for a 48 port gig switch. You're suggesting it might have an x86 backend? Maybe if it has any firewall or routing features. I doubt it though.

Steve

_Adrian_

@stephenw10:

You're suggesting it might have an x86 backend?
Steve

Its a posibility…

And that's what I'm after :)

Sifter

@stephenw10:

PfSense only requires 1 interface. But yes you could use one real interface and one VLAN interface.
The other possibility is that the default config of the switch is no vlans at all, just like an unmanaged switch.

Steve

Ive now assigned sis0 as LAN and since it asked for WAN first, I just filled in a random vlan name. However, nomatter what cable or port I plug into, none of the ports light up. They dont recognize that a cat5 cable is plugged in.

If it doesnt see that a cat5 cable is plugged in, how is a packet capture going to work? Dont we first have to work through getting sis0 "UP"?

stephenw10

Ah, well that makes things a lot more complex. If the default config of the switch is no config at all, everything off, then it needs to be configured before anything will work. ~~Yes you need to see sis0 as UP before anything else.~~
Where are you reading this though, at the console I assume. What do you see from 'ifconfig -a'? If it is vlans only at sis0 then an interface set to use no tags or vlan1 might show as down. What does is show for media and status?

Steve