Sponsored Content
Operating Systems Solaris Getting Network Interface details in solaris Post 302454760 by forumguest on Monday 20th of September 2010 02:33:16 AM
Old 09-20-2010
Getting Network Interface details in solaris

Hi,

/sbin/ifconfig -a

when i login as guest user , output like below,

Code:
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
eri0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
        inet 192.168.118.232 netmask ffffff00 broadcast 192.168.118.255

As root login, output like below,

Code:
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
eri0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
        inet 192.168.118.232 netmask ffffff00 broadcast 192.168.118.255
        ether 0:3:ba:3a:27:cb

whether the ether can get only in root login or do i need to give proper command ?

what arguments i need to give in ifconfig -a to get the ether value as guest login


Please guide me.
 

9 More Discussions You Might Find Interesting

1. Solaris

network interface problem solaris 2.5

Hi guys, Hope somebody can help me on this. I have a Sun Sparc 20 workstation and it has a boot problem. During boot, an error message " ifconfig:socket: Bad File Number" come up and the workstation hang (cannot boot). I did boot -s and checked using ifconfig -a command but i got the same... (0 Replies)
Discussion started by: kroegand
0 Replies

2. Solaris

Solaris 9 on x86- Can't detect network interface

Hi All, I recently installed Solaris 9 on my Compaq Presario V2000 Series (V2069CL) laptop. Everything is working fine except that Solaris is not able to detect the Network Interface after boot. While the system is booting, it shows that it has detected "Xircom Pocket Ethernet parallel port... (3 Replies)
Discussion started by: com2com
3 Replies

3. Solaris

Determine Solaris box network interface?

Given a new Solaris box, with a fresh, unconfigured install on it, how does one figure out what kind of network interface it has (bge,le, hme, etc)? (8 Replies)
Discussion started by: akbar
8 Replies

4. Solaris

Route new network interface Solaris 8

Hi there, I'm trying to configure an additional network interface on Solaris 8 (eri0). The interface has been activated, but all the frames are still routed to the current default interface (ce0) I've tried following command (with various syntaxes...) unsuccessfully so far: # route add... (2 Replies)
Discussion started by: sreiniche
2 Replies

5. Solaris

What are the kernel parameter of network interface in Solaris?

Hi gurus Could anybody tell me that what are the kernal parameter of network interface in solaris Regards (3 Replies)
Discussion started by: girish.batra
3 Replies

6. Solaris

Solaris Network Interface and USB Drive issues

Hi I had installed Sun Solaris 10 on my dell vostro 1400.Problem is iam unable to mount the usb drives as there was no detections at all.And also iam unable to find my network interface or iam not able to install the network card. If try to type ifconfig -a It is showing only loop back... (4 Replies)
Discussion started by: testerindia25
4 Replies

7. Solaris

Configure network interface for Solaris 10

Hi, I have installed Solaris 10 on VMware7, When i used ifconfig -a to check network interface, it has shown lo0 as loopback interface. Please advise how to configure network interfaces using VMware. (1 Reply)
Discussion started by: ajhal04
1 Replies

8. Solaris

Network Interface -- Solaris

Dear All, I have a solaris Server in which I have 4 network interfaces , out of which only one is used . So all the applications are using this interface . The interface speed is 1000Mbps . I find no hardware issue or packets g being dropped. But i find that no of Input and Output... (4 Replies)
Discussion started by: jegaraman
4 Replies

9. Solaris

Network interface configuration - Solaris 11

Hi, I am new in Solaris 11. I can't even make the NIC work. Here is the issue: Any help will be greatly appreciated. (6 Replies)
Discussion started by: aixlover
6 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 06:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy