5.3.2. Network Interface Configuration
Procedure 5.2. Define and Configure Network Interfaces
Remove
unsecureNetwork Interface[standalone@localhost:9999 /]
/interface=unsecure/:removeCreate
internalandclusterNetwork Interfaces[standalone@localhost:9999 /]
/interface=cluster/:add(inet-address=expression "${jboss.bind.address.cluster:127.0.0.1}")[standalone@localhost:9999 /]/interface=internal/:add(inet-address=expression "${jboss.bind.address.internal:127.0.0.1}")Bind each socket to the specified network interface.
For each line in Table 5.1, “Network Bindings”, use the following command to bind the socket to the specified network interface. Refer to the Administration and Configuration Guide.[standalone@localhost:9999 /]
/socket-binding-group=standard-sockets/socket-binding=BINDING_NAME/:write-attribute(name=interface,value=NETWORK_INTERFACE)For example, the following command bindsmanagement-nativeto theinternalnetwork interface:[standalone@localhost:9999 /]
/socket-binding-group=standard-sockets/socket-binding=management-native/:write-attribute(name=interface,value=internal)Restart JBoss EAP
Restart JBoss EAP so that the network bindings take effect.
Table 5.1. Network Bindings
| Binding Name | Network Interface | Port Number |
|---|---|---|
| management-native | internal | 9999 |
| management-http | internal | 9990 |
| management-https | internal | 9443 |
| ajp | internal | 8009 |
| http | public | 8080 |
| https | public | 8443 |
| jacorb | internal | 3528 |
| jacorb-ssl | internal | 3529 |
| jgroups-mping | cluster | 0 - multicast: 45700 |
| jgroups-tcp | cluster | 7600 |
| jgroups-tcp-fd | cluster | 57600 |
| jgroups-udp | cluster | 55200 - multicast: 45688 |
| jgroups-udp-fd | cluster | 54200 |
| messaging | internal | 5445 |
| messaging-group | internal | 0 - multicast: 9876 |
| messaging-throughput | internal | 5455 |
| modcluster | public/internal | 0 - multicast: 23364 |
| remoting | internal | 4447 |
| txn-recovery-environment | internal | 4712 |
| txn-status-manager | internal | 4713 |

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.