9 More Discussions You Might Find Interesting
1. Solaris
Hi,
I need to block ssh port 22 from all the servers except one server ip.
Until solaris11.3 and below, I used to do like below(under /etc/ipf/ipf.conf),and it's working fine
pass in quick from $server_ip to any port=22
block in quick from any to any port=22
But I tried almost same in... (1 Reply)
Discussion started by: Sumanthsv
1 Replies
2. Solaris
Hi all,
Just istalled Solaris 11.
Want to configure network interfaces and got some problems:
#dladm show-phys
#
#dladm show-link
#
If i run ifconfig -a, i am getting 2 lo0 (loopback) interfaces and thats all.
I can't enable interface, can't list it, can't assign IP to it.
Can... (2 Replies)
Discussion started by: nypreH
2 Replies
3. Solaris
Simple question.
I have a solaris11 test machine
When i try to join a samba4 domain
give me this error
"kinit succeeded but ads_sasl_spnego_krb5_bind failed: invalid credentials"
When i join a w2003r2 AD..works perfect
I check network ok,dig,reverse ok..
my conf file is
... (0 Replies)
Discussion started by: Linusolaradm1
0 Replies
4. Solaris
I am trying to connect via Xmanager 4 to a T4-2 server running Solaris 11.
I checked the /etc/gdm.custom.conf file.
The error I get is
The MAC (Message Authentication Code) of packet is incorrect
When I start the Xmanager on soalris I get a message
/dev/fb (file or directory) does not... (2 Replies)
Discussion started by: Maqsood Mohamme
2 Replies
5. Solaris
Short version:
pfexec zpool scrub rpool fails saying I do not have permission to perform that action. Apparently scrub is not one of the pfexec allowed actions. Any idea on how to get around it?
Long version:
I got tired of manually running scrubs and am trying to set it to happen... (4 Replies)
Discussion started by: taltamir
4 Replies
6. UNIX for Advanced & Expert Users
I can log into a unix system with Putty. I've set the "X11 forwarding" checkbox, and I've verified that I can display an X11 window back on my laptop. What I need to be able to do is "su" to another uid after logging in and then run something which display a window back on my laptop, with the... (2 Replies)
Discussion started by: dkarr
2 Replies
7. Solaris
Hi,
I'm new on this forum. I'm working on Solaris 11 (Express Edition) and I must install some programm created only for RedHat system (I don't want to buy or download RedHat). So I search for this tools and I find a working script for Solaris 9 and 10, but I need that for Solaris 11. So I search... (1 Reply)
Discussion started by: Fraste_
1 Replies
8. Solaris
Hello,
I am trying to install Nmap on my Solaris machine. I got errors at the very last of "make" command though. Could someone point me out what I am lacking?
Thank you!
Nmap version: 5.50 (nmap-5.50.tar.bz2)
Solaris version (cat /etc/release):
Error message ( run "./configure &&... (0 Replies)
Discussion started by: fragile_it
0 Replies
9. Windows & DOS: Issues & Discussions
Hello All.
Really a newbie to Linux/Unix. Trying to get into Linux. Using XP PE currently. Installed cygwin and trying to intall cygwin-x. Everything else is setup nice but i can't seem to install these two packages (without whom xwin won't start)
1. xorg-x11-f100
2. xorg-x11-fnts
Tried the... (1 Reply)
Discussion started by: binodbdrchand
1 Replies
hubd(7D) hubd(7D)
NAME
hubd - USB hub driver
SYNOPSIS
hub@unit-address
The hubd is a USBA (Solaris USB Architecture) compliant client driver that supports USB hubs conforming to the Universal Serial Bus Speci-
fication 2.0. The hubd driver supports bus-powered and self-powered hubs. The driver supports hubs with individual port power, ganged power
and no power switching.
When a device is attached to a hub port, the hubd driver enumerates the device by determining its type and assigning an address to it. For
multi-configuration devices, hubd sets the preferred configuration (refer to cfgadm_usb(1M) to select a configuration). The hubd driver
attaches a driver to the device if one is available for the default or selected configuration. When the device is disconnected from the hub
port, the hubd driver offlines any driver instance attached to the device.
/kernel/drv/hubd
32- bit ELF kernel module
/kernel/drv/amd64/hubd
64- bit ELF kernel module
/kernel/drv/sparcv9/hubd
64-bit SPARC ELF kernel module
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC, , PCI-based systems |
+-----------------------------+-----------------------------+
|Availability |SUNWusb |
+-----------------------------+-----------------------------+
cfgadm_usb(1M), attributes(5), usba(7D)
Writing Device Drivers
Universal Serial Bus Specification 2.0
System Administration Guide: Basic Administration
http://www.sun.com/io
In addition to being logged, the following messages may also appear on the system console. Messages are formatted in the following manner:
WARNING: <device path> <hubd<instance number>): Message...
where <instance number> is the instance number of hubd and <device path> is the physical path to the device in /devices directory. Messages
from the root hub are displayed with a usb<instance number> prefix instead of hub<instance number> as the root hub is an integrated part of
the host controller.
Connecting device on port <number> failed.
The driver failed to enumerate the device connected on port <number> of hub. If enumeration fails, disconnect and re-connect.
Use of a USB 1.0 hub behind a high speed port may cause unexpected failures.
Devices connected to a USB 1.0 hub which are in turn connected to an external USB 2.0 hub, may misbehave unexpectedly or suddenly go
offline. This is due to a documented incompatibility between USB 1.0 hubs and USB 2.0 hub Transaction Translators. Please use only USB
2.0 or USB 1.1 hubs behind high-speed ports.
Connecting a high speed device to a non-high speed hub (port x) will result in a loss of performance. Please connect the device to a high
speed port to get the maximum performance.
USB 2.0 devices connected to USB 1.0 or 1.1 hubs cannot run at their highest speed, even when the hub is in turn connected to a high-
speed port. For best performance, reconnect without going through a USB 1.0 or 1.1 hub.
Cannot access <device>. Please reconnect.
This hub has been disconnected because a device other than the original one has been inserted. The driver informs you of this fact by
displaying the name of the original device.
Devices not identical to the previous one on this port. Please disconnect and reconnect.
Same condition as described above; however in this case, the driver is unable to identify the original device with a name string.
Hub driver supports max of <n> ports on hub. Hence, using the first <number of physical ports> of <n> ports available.
The current hub driver supports hubs that have <n> ports or less. A hub with more than <n> ports has been plugged in. Only the first
<n> out of the total <number of physical ports> ports are usable.
The following messages may be logged into the system log. They are formatted in the following manner:
<device path> <hubd<instance number>): message...
Global over current condition, please disconnect hub.
The driver detected an over current condition. This means that the aggregate current being drawn by the devices on the downstream port
exceeds a preset value. Refer to section 7.2.1.2 and 11.13 of the Universal Serial Bus Specification 2.0. You must remove and insert
this hub to render it and its downstream devices functional again. If this message continues to display for a particular hub, you may
need to remove downstream devices to eliminate the problem.
Local power has been lost, please disconnect hub.
A USB self-powered hub has lost external power. All USB devices connected down-stream from this hub will cease to function. Disconnect
the hub, plug in the external power-supply and then plug in the hub again.
Local power has been lost, the hub could draw <x> mA power from the USB bus.
A USB self/bus-powered hub has lost external power. Some USB devices connected down-stream from this hub may cease to func-
tion. Disconnect the external power-supply and then plug in the hub again.
20 June 2005 hubd(7D)