User Tools

Site Tools


documentation:end-users_docs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
documentation:end-users_docs [2019/01/29 19:35] – external edit 127.0.0.1documentation:end-users_docs [2021/02/23 12:01] (current) – [Installation] olivier
Line 5: Line 5:
  
 For BSDRP you need: For BSDRP you need:
-  * a 1GB flash disk (Compact Flash, USB stick, mSATA flash module, etc.). +  * a 2GB flash disk (Compact Flash, USB stick, mSATA flash module, etc.). 
-  * a minimum of 256MB RAM.+  * a minimum of 512MB RAM.
  
-[[http://www.freebsd.org/releases/10.3R/hardware.html|All hardware supported by FreeBSD 10.3]] are supported by BSDRP with the exception of following drivers:+[[https://www.freebsd.org/releases/12.1R/hardware.html|All hardware supported by FreeBSD 12.1]] are supported by BSDRP with the exception of following drivers:
  
 Wireless, PCMCIA cards, SCSI adapters, USB printer, fire wire, etc. drivers were removed from the FreeBSD kernel. Wireless, PCMCIA cards, SCSI adapters, USB printer, fire wire, etc. drivers were removed from the FreeBSD kernel.
Line 58: Line 58:
 == Mac OS X users == == Mac OS X users ==
  
-Insert the USB key, and run mount in a terminal (or disk utility if you prefer graphical method) to see what device OSX has assigned to your USB key. You should see something like this:+Insert the USB key, and display list of external devices:
  
 <code> <code>
 +% diskutil list | grep external
 +/dev/disk3 (external, physical):
 +</code>
 +
 +Check if it is already mounted
 +
 +<code>
 +% mount | grep '/dev/disk3'
 /dev/disk0s2 on / (hfs, local, journaled) /dev/disk0s2 on / (hfs, local, journaled)
 devfs on /dev (devfs, local) devfs on /dev (devfs, local)
Line 68: Line 76:
 /dev/disk3s1 on /Volumes/UNTITLED (msdos, local, nodev, nosuid, noowners) /dev/disk3s1 on /Volumes/UNTITLED (msdos, local, nodev, nosuid, noowners)
 </code> </code>
-The last line is your USB device. Unmount it and write the BSDRP image to it with:+The last line is your USB device. Unmount it and write the BSDRP image to the device adding the 'r' letter:
 <code> <code>
 sudo umount -f /dev/disk3s1 sudo umount -f /dev/disk3s1
-xzcat BSDRP_full_amd64_vga.1.0.img.xz | dd of=/dev/disk3 bs=256k+xzcat BSDRP_full_amd64_vga.1.0.img.xz | sudo dd of=/dev/rdisk3 bs=1m
 </code> </code>
-If successful, OSX will pop up an error dialog telling you it doesn'recognize the disk. Click 'Eject', remove the USB key, and you're done.+If successful, OSX will pop up an error dialog telling you it doesn'recognise the disk. Click 'Eject', remove the USB key, and you're done.
  
 === To an hard drive === === To an hard drive ===
Line 114: Line 122:
  
 === Special notes for PC-Engines === === Special notes for PC-Engines ===
- 
-==  WRAP platform == 
- 
-The FreeBSD (BSDRP) bootloader default configuration isn't compatible with the WRAP: You need to change the bootloader mode before to use it on a WRAP platform. 
-From a FreeBSD host, once you had installed the image on your CF, change the bootloader mode (replace daX by your device): 
- 
-<code> 
-boot0cfg -o nopacket /dev/daX 
-</code> 
- 
-<note warning>Upgrading BSDRP on WRAP is not possible: The PC-Engines WRAP is not able to boot from the second partition (BIOS limitation)</note> 
  
 ==  Alix platform == ==  Alix platform ==
Line 198: Line 195:
 <code> <code>
 fetch 'http://URL/BSDRP-upgrade.image.xz' -o - | xzcat | upgrade fetch 'http://URL/BSDRP-upgrade.image.xz' -o - | xzcat | upgrade
 +</code>
 +
 +Real example to upgrade to 1.96:
 +<code>
 +fetch 'https://sourceforge.net/projects/bsdrp/files/BSD_Router_Project/1.96/amd64/BSDRP-1.96-upgrade-amd64-serial.img.xz/download' -o - | xzcat | upgrade
 </code> </code>
  
Line 416: Line 418:
 BSDRP v1.4 and earlier have a default configuration that prevent remote syslog. This behavior can be changed by editing /etc/rc.conf.misc and replacing syslogd_flags="-ss" by syslogd_falgs="-s" BSDRP v1.4 and earlier have a default configuration that prevent remote syslog. This behavior can be changed by editing /etc/rc.conf.misc and replacing syslogd_flags="-ss" by syslogd_falgs="-s"
 </note> </note>
 +
 +==== Firmware Upgrade ====
 +
 +=== Mellanox ===
 +
 +Stat by identifying your NIC ID:
 +<code>
 +# mstfwmanager
 +Querying Mellanox devices firmware ...
 +
 +Device #1:
 +----------
 +
 +  Device Type:      ConnectX4
 +  Part Number:      MCX416A-CCA_Ax
 +  Description:      ConnectX-4 EN network interface card; 100GbE dual-port QSFP28; PCIe3.0 x16; ROHS R6
 +  PSID:             MT_2150110033
 +  PCI Device Name:  pci0:2:0:0
 +  Base GUID:        e41d2d0300fdbd90
 +  Base MAC:         e41d2dfdbd90
 +  Versions:         Current        Available
 +     FW             12.26.1040     N/A
 +     PXE            3.5.0803       N/A
 +     UEFI           14.19.0014     N/A
 +
 +  Status:           No matching image found
 +</code>
 +
 +Then go to the [[https://www.mellanox.com/page/firmware_download|Mellanox firmware web site]] in section "Device Type" -> "Part Number" -> "PSID", then fetch it into your BSDRP and upgrade it:
 +
 +<code>
 +# mount /data
 +# cd /data
 +# fetch http://www.mellanox.com/downloads/firmware/fw-ConnectX4-rel-12_26_4012-MCX416A-CCA_Ax-UEFI-14.19.17-FlexBoot-3.5.805.bin.zip
 +# unzip fw-ConnectX4-rel-12_26_4012-MCX416A-CCA_Ax-UEFI-14.19.17-FlexBoot-3.5.805.bin.zip
 +# mstfwmanager -u -i fw-ConnectX4-rel-12_26_4012-MCX416A-CCA_Ax-UEFI-14.19.17-FlexBoot-3.5.805.bin
 +Querying Mellanox devices firmware ...
 +
 +Device #1:
 +----------
 +
 +  Device Type:      ConnectX4
 +  Part Number:      MCX416A-CCA_Ax
 +  Description:      ConnectX-4 EN network interface card; 100GbE dual-port QSFP28; PCIe3.0 x16; ROHS R6
 +  PSID:             MT_2150110033
 +  PCI Device Name:  pci0:2:0:0
 +  Base GUID:        e41d2d0300fdbd90
 +  Base MAC:         e41d2dfdbd90
 +  Versions:         Current        Available
 +     FW             12.26.1040     12.26.4012
 +     PXE            3.5.0803       3.5.0805
 +     UEFI           14.19.0014     14.19.0017
 +
 +  Status:           Update required
 +
 +---------
 +Found 1 device(s) requiring firmware update...
 +
 +Perform FW update? [y/N]: y
 +Device #1: Updating FW ...
 +Initializing image partition -   OK
 +Writing Boot image component -   OK
 +Done
 +
 +Restart needed for updates to take effect.
 +</code> 
 +
 +
  
 ===== Debugging ===== ===== Debugging =====
  
 ==== Enabling crash dump ==== ==== Enabling crash dump ====
 +
 +=== Local swap dump device ===
  
 For saving and extracting a crash dump you need: For saving and extracting a crash dump you need:
Line 517: Line 589:
 </code> </code>
  
 +=== netdump ===
 +
 +In case where you didn't have enough disk space to localy store dump, you can use netdump(4).
 +
 +On the receiving FreeBSD server (not your router):
 +<code>
 +pkg install netdumpd
 +service netdumpd enable
 +service netdumpd start
 +</code>
 +
 +Then on your router, declare source interface to use, source IP address, gateway
 +<code>
 +sysrc dumpdev=igb1
 +sysrc dumpon_flags="-s 198.19.0.24 -c 192.168.1.10 -g 192.168.1.254
 +</code>
 +
 +and enable it:
 +
 +<code>
 +# service dumpon restart
 +kernel dumps on priority: device
 +0: /dev/null
 +server address: 198.19.0.24
 +client address: 192.168.1.10
 +gateway address: 192.168.1.254
 +</code>
 ==== Installing debug symbols ==== ==== Installing debug symbols ====
 Symbol files of kernel and binary are available in the separate DEBUG archive file. Symbol files of kernel and binary are available in the separate DEBUG archive file.
documentation/end-users_docs.1548786904.txt.gz · Last modified: 2019/01/29 19:35 by 127.0.0.1

Except where otherwise noted, content on this wiki is licensed under the following license: BSD 2-Clause
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki