07-29-2011
Socket and interface (eth0, eth 1)relationship
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 above socket send data to ???????
please clarify
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
HI,
When I do 'service network restart' , I am getting the following error.
"3c501 device eth0 does not seem to be present, delaying initialization"
Can any one suggest me the cause/solution for this?
When I do 'lspci' it is showing the ehternet card as
" Ethernet controller"Marvell... (2 Replies)
Discussion started by: praveen_b744
2 Replies
2. Linux
Hi
I had a DL380 with two two port eth cards. I now replaced one with a four port eth card and my interfaces seemed to have jumped around.
Is there a method of moving eth ports... eg making port eth4 eth2.:confused: (2 Replies)
Discussion started by: theroncj
2 Replies
3. UNIX for Dummies Questions & Answers
folks;
This might sounds stupid but i hope someone can give me an answer:
On my Linux SUSE boxes, i have 2 NIC cards NIC1 & NIC2. I always assumed that NIC1 is eth0 when i run "ifconfig" and NIC2 is eth1
but i noticed that's not always the case.
Is there a way or a command i can run to find... (1 Reply)
Discussion started by: Katkota
1 Replies
4. UNIX for Advanced & Expert Users
Hi,
For one of my application(Linux 2.6) I am using a netlink socket to get the interface changes notification.
socket(PF_NETLINK, SOCK_RAW, NETLINK_ROUTE)
Application receives netlink notification for Ethernet, bond interfaces but there is no notification about bridge interfaces changes. ... (6 Replies)
Discussion started by: learn more
6 Replies
5. IP Networking
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)
Discussion started by: nicandro
2 Replies
6. Shell Programming and Scripting
I want to run dhcpclient for all the eth* which has no ip
for example
eth0 Link encap:Ethernet HWaddr 00:1E:67:3E:BA:EF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0... (6 Replies)
Discussion started by: yanglei_fage
6 Replies
7. Linux
Hi all,
OS: fedora release 10
when i try to restart network service, ending up with following errors. There are two interfaces eth0 and eth1
bringing up interface eth0 rtnetlink answers file exists
error adding <IP Address here> to eth0
bringing up interface eth0 rtnetlink answers... (2 Replies)
Discussion started by: lramsb4u
2 Replies
8. Red Hat
Hi,
I´ve given only this info to configure a network interface : "port 1 PCI 4"
I´ve been searching for any kind of relationship in the system which allow me to find the etc that must be configured...
Please, could anybody help me?
rhxx:#/root# lspci |grep -i "PCI BRIDGE"
00:01.0 PCI... (0 Replies)
Discussion started by: pabloli150
0 Replies
9. UNIX for Dummies Questions & Answers
hi guys
I have a server which has 2 nics eth0 and eth1
eth0 is used for our email traffic server. everything working fine
some time later a eth1 was added for backup purposes so this new nic sends data to another vlan for backup purposes
all of a sudden our mail server starts to fail... (3 Replies)
Discussion started by: karlochacon
3 Replies
10. IP Networking
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)
Discussion started by: postcd
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)