Tag Info

Hot answers tagged

6

If find is available, try: find / -type f -exec grep -rHinF --colour=always -e "aa:aa:aa:aa" {} + This only applies to regular files so it will skip block and character devices. See man find. You probably want to skip directories like /proc or /sys; as Stephane Chazelas points out in the comments, some files in there will block (remain open, hanging the ...


4

Why does *BSD uses driver specific names for network interfaces? It's just a historical choice. The letters in the name come from the driver that talks to the card, so they will be the same for two separate interfaces if they happen to use the same driver. It does have one practical benefit: on BSD, the network drivers have their own manual pages in ...


3

The CUA devices are both serial ports. 3G modems have often 1 to 3 serial ports. One of them is the communication port and the rest are control and monitor ports that you can use for e.g. checking the signal level (with AT commands) while connected. The first port is almost always the communication port that you should use. You can see if dmesg gives any ...


3

The choice of using generic or driver-specific names has nothing to do with any driver limitation. It's mostly a cosmetic choice. Using generic names has the advantage of hiding information that is almost always irrelevant — a network interface is a network interface, no matter who made it. The capabilities of a device depend on the exact model and on its ...


2

It makes it easier to tell which network card you are talking to. If you have an Intel (igb0) and an Realtek (rl0) nic, you can now tell them apart immediately. Also, different drivers support different features. Some drivers support polling and some do not. Some support LRO, TSO and RSS etc. It is easier to track which support which when they are not all ...


1

I don't know about pfSense, but from the OpenVPN perspective the line of interest here is Options error: --server directive network/netmask combination is invalid This means that you've specified a VPN network address and netmask that do not combine. OpenVPN checks the network address to have zeroes where the netmask expects zeroes. E.g. 192.168.1.0 + ...


1

pfSense is currently based on FreeBSD 8.x. The ability to grow a UFS filesystem live is only coming with FreeBSD 10.x, so all this should be done from a rescue/install mode. First do a backup of your config.xml file ! To grow the pfSense root filesystem you must first properly re-size the BSD partition scheme (aka "bsd slices"): re-size the BSD partition ...


1

It looks like you can't do this in NanoBSD. From the document you linked to: Do not attempt this on NanoBSD, it relies on the boot manager for required functionality. That in mind, I am not surprised that removing the boot manager doesn't work and/or hozes things.


1

Web search suggests this modem knows AT command set, so you can easily check this using "tip" or "cu" commands with both ports and detect which one responds to AT.



Only top voted, non community-wiki answers of a minimum length are eligible