hi,
below is the situation:
my server is in 128.10.200.xxx network.
i have a solaris computer running in a subnet. this computer got 2 nic card.
1 is 172.18.198.xxx , another 1 is 10.100.xxx.11
there is a machine stick with this computer, ip is 10.100.xxx.12
so, 10.100.xxx.11 and... (3 Replies)
Does anyone know how to delete a an ip off the routing table ? i tried route delete 10.0.0.0 and gateway but it still comes back. i have 2 zones sharing one interface. help... (4 Replies)
hi all,
how do i make sure that the new routing should take effect on the os memory right away? what should i run after i add all the new "route add ....".
I have an example below:
bash-2.03# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface... (1 Reply)
Hi,
I got problem of Sun Solaris 8 routing.
IP of SunA is 10.16.64.164, and have routing table:
10.16.64.0 10.16.64.164 U 1 19236 bge1
10.6.0.0 10.6.0.3 U 1 16534 bge0
224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
I have a SUN ultra 5 machine running Solaris 6. it has two ethernet interfaces qe0 192.168.0.111 and qe1 192.168.1.111
the two subnets are 192.168.0.111 255.255.255.0
192.168.1.111 255.255.255.0
the specified routes are
add route -net 192.168.0.0 255.255.255.0 192.168.0.111
add route... (3 Replies)
Hi everyone,
Hopefully there is someone here that can help me with the problem I got.
At my office I have 1 ubuntu firewall/gateway and several networks.
On the firewall/gateway I have three network cards, one for internet, one for network 192.168.100.0 and one for network 172.20.1.0
We... (0 Replies)
Hello All,
Problem is that redundancy doesn't work, probably a routing issue I need to get sorted out When 172.29.11.x net is down, neither node3 nor node4 is trying 172.29.12.x network,The problem lies in network 172.29.13.x
if 172.29.11.x network is down, node3/node4 should route to... (6 Replies)
Discussion started by: nadeemahmed
6 Replies
LEARN ABOUT FREEBSD
ntb_hw
NTB(4) BSD Kernel Interfaces Manual NTB(4)NAME
ntb, ntb_hw, if_ntb -- Intel(R) Non-Transparent Bridge driver
SYNOPSIS
To compile this driver into your kernel, place the following lines in your kernel configuration file:
device ntb_hw
device if_ntb
Or, to load the driver as a module at boot, place the following line in loader.conf(5):
if_ntb_load="YES"
DESCRIPTION
The ntb driver provides support for the Non-Transparent Bridge (NTB) in the Intel S1200, Xeon E3 and Xeon E5 processor families.
The NTB allows you to connect two computer systems using a PCI-e link if they have the correct equipment and connectors.
CONFIGURATION
The NTB memory windows need to be configured by the BIOS. If your BIOS allows you to set their size, you should set the size of both memory
windows to 1 MiB. This needs to be done on both systems.
Each system needs to have a different IP address assigned. The MAC address is randomly generated. Also for maximum performance, the MTU
should be set to 16 kiB. This can be done by adding the line below to rc.conf(5):
ifconfig_ntb0="inet 192.168.1.10 netmask 255.255.255.0 mtu 16384"
And on the second system :
ifconfig_ntb0="inet 192.168.1.11 netmask 255.255.255.0 mtu 16384"
If you are using the UDP protocol, you may want to increase the net.inet.udp.maxdgram sysctl(8) variable.
SEE ALSO rc.conf(5), sysctl(8)AUTHORS
The ntb driver was developed by Intel and originally written by Carl Delsey <carl@FreeBSD.org>.
BUGS
If the driver is unloaded, it cannot be reloaded without a system reboot.
The network support is limited. It isn't fully configurable yet. It also isn't integrated into netgraph(4) or bpf(4).
NTB to Root Port mode is not yet supported.
There is no way to protect your system from malicious behavior on the other system once the link is brought up. Anyone with root or kernel
access on the other system can read or write to any location on your system. In other words, only connect two systems that completely trust
each other.
BSD Apr 11, 2013 BSD