when i try to restart network service, ending up with following errors. There are two interfaces eth0 and eth1
Code:
bringing up interface eth0 rtnetlink answers file exists
error adding <IP Address here> to eth0
bringing up interface eth0 rtnetlink answers invalid argument
below are ifcfg-eth0 and eth1 files under /etc/sysconfig/network-scripts/ directory
Code:
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
BROADCAST=19.16.12.255
HWADDR=<MAC ADDRESS HERE>
IPADDR=19.16.12.125
IPV6_AUTOCONF=yes
NETMASK=255.255.255.0
NETWORK=19.16.12.0
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
NM_CONTROLLED=yes
# cat /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=none
HWADDR=<MAC ADDRESS HERE>
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
NETMASK=255.255.255.0
IPADDR=<IP ADDRESS HERE>
GATEWAY=<GATEWAY HERE>
NM_CONTROLLED=yes
PEERDNS=No
DNS1=127.0.0.1
DNS2=<DNS IP HERE>
# service network status
Configured devices:
lo eth0 eth1
Currently active devices:
lo eth0 eth1
# service NetworkManager status
NetworkManager (pid 4236) is running...
There is another similar server, and ifcfg-eth0 and ifcfg-eth1 are similar(ofcourse different IP etc).
The other server is working fine.
difference is
Code:
on WORKING server
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
IP ADDRESS HERE * 255.255.255.0 U 1 0 0 eth1
19.16.12.1 * 255.255.255.0 U 1 0 0 eth0
default GATEWAY HERE 0.0.0.0 UG 0 0 0 eth1
on NON-WORKING server
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
IP ADDRESS HERE * 255.255.255.0 U 1 0 0 eth1
19.16.12.0 * 255.255.255.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1002 0 0 eth0
link-local * 255.255.0.0 U 1003 0 0 eth1
default GATEWAY HERE 0.0.0.0 UG 0 0 0 eth1
and WORKING server is able to resolve IP but NON-WORKING server is not able resolve IP and ending up with an error when it try to use nslookup command to resolve some other server
Code:
on WORKING server
# more /etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.0.1
nameserver <DNS IP HERE>
on NON-WORKING server
# more /etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.0.1
nameserver <SAME DNS IP HERE AS ABOVE FOR WORKING SERVER>
Please help to solve this issue.
Thanks in advance!
OK...I'm using the latest version of Fedora 10.
My network connection was working fine, and I had several network LAN shares on my desktop. Then I rebooted the system without dismounting those shares first. ooops. <:(
...When the system came back up, my network connection was gone. All... (2 Replies)
If i have a single file i would just press fg but if i have multiple files running in the backgound and want to bring a specific one to the foreground how would i do that? Thanks!! (1 Reply)
Dear all,
I am a newbie in solaris and I need your advice.
I have a Solaris version 5.9 installed on Sunfire V240.
I am able to ssh the machine from putty remotely.
My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Hi all
I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface?
If you have any ideas, please tell me then. Thank you (2 Replies)
hi,
Could some one answer this please
we have a program with client socket declared which connect to a server
for the above program description we wont send an interface information ... let us suppose, I have two interfaces (eth0 , eth1) which are assigned some ip, which interface the... (1 Reply)
Hello everybody,
I have been reading many posts about this topic but I have no figure out how to solve it.
I need to split the traffic incoming on eth0 on two other interfaces (for instance one receiving on port 80 and the others on the other interface).
I cannot understand how to do that.... (2 Replies)
Hello,
I have a opensuse Linux server with two nics.
eth0 = internal network with 172.16.1.24
eth1 = external network with ip 172.19.3.2
Internal networks: 172.16.0.0/16, 172.17.0.0/16 and 192.168.0.0/16.
External network: 172.19.3.0/16
The default gateway is 172.19.3.1 on eth1.
... (3 Replies)
Server is stuck at "Stuck at "bringing up interface eth0:""
after i hard reset the server
I have IPMI access, please help me diagnose the cause if you can :( (0 Replies)
Hello All,
While I am studying on RTNETLINK, I understand that the kernel will send RTM_ADDLINK or RTM_DELLINK if interface is added/removed at kernel space. However, I have a question regarding to the RTNETLINK message if adding or removing ethernet to/from bridge? Since adding or removing... (0 Replies)
Discussion started by: urnoicxk
0 Replies
LEARN ABOUT DEBIAN
dibbler-relay
dibbler-relay(8) Dibbler dibbler-relay(8)NAME
dibbler-relay - a portable DHCPv6 relay
DESCRIPTION
dibbler-relay is a portable implementation of the DHCPv6 relay. DHCPv6 relays are proxies, which allow one server to support links, which
server is not directly connected to. There are ports available for Linux 2.4/2.6 systems as well as MS Windows XP and 2003. They are freely
available under GNU GPL version 2 (or later) license.
SYNOPSIS
dibbler-relay [ run | start | stop | status ]
OPTIONS
run - starts relay in the console. Relay can be closed using ctrl-c.
start - starts relay in daemon mode.
stop - stops running relay.
status - shows status of the relay.
EXAMPLES
Relay forwards DHCPv6 messages between interfaces. Messages from client are encapsulated and forwarded as RELAY_FORW messages. Replies from
server are received as RELAY_REPL message. After decapsulation, they are being sent back to clients.
It is vital to inform server, where this relayed message was received. DHCPv6 does this using interface-id option. This identifier must be
unique. Otherwise relays will get confused when they will receive reply from server. Note that this id does not need to be alligned with
system interface id (ifindex). Think about it as "ethernet segment identifier" if you are using Ethernet network or as "bss identifier" if
you are using 802.11 network.
Let's assume this case: relay has 2 interfaces: eth0 and eth1. Clients are located on the eth1 network. Relay should receive data on that
interface using well-known ALL_DHCP_RELAYS_AND_SERVER multicast address (ff02::1:2). Relay also listens on its global address 2000::123.
Packets received on the eth1 should be forwarded on the eth0 interface, also using multicast address:
log-level 8
log-mode short
iface eth0 {
server multicast yes
}
iface eth1 {
client multicast yes
client unicast 2000::123
interface-id 1000
}
Here is another exmaple. This time messages should be forwarded from eth1 and eth3 to the eth0 interface (using multicast) and to the eth2
interface (using server's global address 2000::546). Also clients must use multicasts (the default approach):
iface eth0 {
server multicast yes
}
iface eth2 {
server unicast 2000::456
}
iface eth1 {
client multicast yes
interface-id 1000
}
iface eth3 {
client multicast yes
interface-id 1001
}
FILES
All files are created in the /var/lib/dibbler directory. During operation, Dibbler saves various file in that directory. Dibbler relay
reads /etc/dibbler/relay.conf file. Log file is named client.log.
STANDARDS
This implementation aims at conformance to the following standards:
RFC 3315 DHCP for IPv6
RFC 3736 Stateless DHCPv6
BUGS
Bugs are tracked with bugzilla, available at http://klub.com.pl/bugzilla/. If you belive you have found a bug, don't hesitate to report it.
AUTHOR
Dibbler was developed as master thesis on the Technical University of Gdansk by Tomasz Mrugalski and Marek Senderski. Currently Marek has
not enough free time, so this project is being developed by Tomasz Mrugalski. Author can be reached at thomson@klub.com.pl.
SEE ALSO
There are dibbler-server(8) and dibbler-client(8) manual pages available. You are also advised to take a look at project website located at
http://klub.com.pl/dhcpv6/. As far as authors know, this is the only Windows DHCPv6 stateful implementation available and the only one
with relay support. It is also one of two freely available under Linux. The other Linux implementation is available at
http://dhcpv6.sourceforge.net, but it is rather outdated and seems not being actively developed.
GNU 2004-12-11 dibbler-relay(8)