02-18-2019
I'm a bit puzzled. Did you use "alias interfaces", as both seem to share the same MAC address? Pls show the output from ifconfig or its ip equivalent.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:confused:
Hi:
I donīt know how to add route gateway and when restart the machine lose this route and put other.
In SCO ver 5.6 Enterprise write:
etc\route delete gateway
route add gateway 199.199.1.1.
so , netstat -rn to see if has change -> all ok
Restart -> !!!... (2 Replies)
Discussion started by: AlvaroD
2 Replies
2. AIX
Hello ,
We have 3 rs/6000 server's running aix on our local network, so each time I try to ping one of these servers we get a "network is down" error , I've been instructed to use to route add command which is ...
#route add server.ip router.ip
after this the ping command works fine ,... (6 Replies)
Discussion started by: cubicle^dweller
6 Replies
3. IP Networking
I have two networks connected by cisco routers. My first subnet is 192.168.0.0 and my second is 192.168.1.0.
My SCO unix machine is on the 192.168.1.0 subnet with an IP of 192.168.1.231. It can see the entire .1.0 subnet but nothing on the other network.
My cicso router(gateway) to the other... (6 Replies)
Discussion started by: agoodrich
6 Replies
4. Shell Programming and Scripting
Hello all!
We have two fedora routers one at each site. What we are trying to do worked using freesco but not on fedora, i'm not very good at scripting and need a little guidence. Basicly what we are trying to do is if the primary line dies, the router will change it's routes to go through our... (0 Replies)
Discussion started by: slacker
0 Replies
5. IP Networking
We are unable to bring one of our linux boxes into the network once it was restarted. But once we stop and start the network service. We are able to ping the gateway and get into network. After a minute or two we get the following reponse for the ping command
64 bytes from 124.168.215.40:... (6 Replies)
Discussion started by: chrisanto_2000
6 Replies
6. Solaris
Hi,
I am trying to add route command in Solaris 10 machine in the following fashion:
route add -host 10.8.112.10 180.144.1.250 -interface lo0:1
this command fails with an error "lo0:1: bad value"
I want to add a route to 10.8.112.10 that picks 180.144.1.250 as the gateway via the... (3 Replies)
Discussion started by: sudhir_shet
3 Replies
7. AIX
Just want to know if someone has a clue about what could be happening here:
I have an AIX box with four NICs in Ether channel connected to a Cisco Switch.
When I try to ping the default gateway, sometimes it works, but sometimes it doesn't work unless it has a defined static route.
Thanks... (1 Reply)
Discussion started by: witt
1 Replies
8. UNIX for Advanced & Expert Users
I have setup a Linux machine on my server but for some reason Im unable to reach my default gateway. This is causing me to not communicate with the outside world (unable to connect to CentOS repos)
# ifconfig
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies
9. Red Hat
Hi all,
i have a rhel 6.2 with a default gateway.
This server is an Intranet office with no internet access.
DNS are already configured and it's possible to resolve my target.
My goal is to link my application (apache forward) only to http://mytarget.yyy through a new gateway (That does... (0 Replies)
Discussion started by: kamose
0 Replies
10. UNIX for Beginners Questions & Answers
Dear friends
I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 Replies
AGR(4) BSD Kernel Interfaces Manual AGR(4)
NAME
agr -- link aggregation pseudo network interface driver
SYNOPSIS
pseudo-device agr
DESCRIPTION
The agr driver provides link aggregation functionality (a.k.a. L2 trunking or bonding).
It supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol.
The agr driver supports the following link specific flags for ifconfig(8):
link0 Use the round-robin distribution algorithm. Don't use it unless you're really sure, because it violates the frame ordering rule.
-link0 Use the default distribution algorithm, which is based on the hash of DA/SA, TCI, and, if available, some upper layer protocol infor-
mation like ip(4) DA/SA.
link1 Disable LACP. Prevents any LACP or Marker messaging which leaves the ports in the default static configuration. Set this prior to
adding ports.
EXAMPLES
Create an agr interface, agr0, and attach re0 and re1 to it. In other words, aggregate re0 and re1 so that they can be used as a single
interface, agr0. The physical interfaces which are attached to the agr interface must not have any IP addresses, neither IPv4 nor IPv6.
ifconfig re0 inet xxx.xxx.xxx.xxx delete
ifconfig re0 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig re1 inet xxx.xxx.xxx.xxx delete
ifconfig re1 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig agr0 create
ifconfig agr0 agrport re0
ifconfig agr0 agrport re1
Destroy an interface created in the above example.
ifconfig agr0 -agrport re0
ifconfig agr0 -agrport re1
ifconfig agr0 destroy
SEE ALSO
ifconfig(8)
STANDARDS
IEEE 802.3ad Aggregation of Multiple Link Segments
HISTORY
The agr driver first appeared in NetBSD 4.0.
AUTHORS
The agr driver was written by YAMAMOTO Takashi.
BUGS
There is no way to configure LACP administrative variables, including system and port priorities. The current implementation of the agr
driver always performs active-mode LACP and uses 0x8000 as system and port priorities.
The agr driver uses the MAC address of the first-added physical interface as the MAC address of the agr interface itself. Thus, removing the
physical interface and using it for another purpose can result in non-unique MAC addresses.
The current implementation of the agr driver doesn't prevent unsafe operations like some ioctls against underlying physical interfaces. Such
operations can result in unexpected behaviors, and are strongly discouraged.
There is no way to configure agr interfaces without attaching physical interfaces.
Physical interfaces being added to the agr interface shouldn't have any addresses except for link level address. Otherwise, the attempt will
fail with EBUSY. Note that it includes an automatically assigned IPv6 link-local address.
BSD
February 23, 2010 BSD