when i try to restart network service, ending up with following errors. There are two interfaces eth0 and eth1
below are ifcfg-eth0 and eth1 files under /etc/sysconfig/network-scripts/ directory
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
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
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 CENTOS
pppoe-relay
PPPOE-RELAY(8) System Manager's Manual PPPOE-RELAY(8)NAME
pppoe-relay - user-space PPPoE relay agent.
SYNOPSIS
pppoe-relay [options]
DESCRIPTION
pppoe-relay is a user-space relay agent for PPPoE (Point-to-Point Protocol over Ethernet) for Linux. pppoe-relay works in concert with the
pppoe client and pppoe-server server. See the OPERATION section later in this manual for details on how pppoe-relay works.
OPTIONS -S interface
Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Only PPPoE servers may be connected to this
interface.
-C interface
Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Only PPPoE clients may be connected to this
interface.
-B interface
Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Both PPPoE clients and servers may be con-
nected to this interface.
-n num Allows at most num concurrent PPPoE sessions. If not specified, the default is 5000. num can range from 1 to 65534.
-i timeout
Specifies the session idle timeout. If both peers in a session are idle for more than timeout seconds, the session is terminated.
If timeout is specified as zero, sessions will never be terminated because of idleness.
Note that the idle-session expiry routine is never run more frequently than every 30 seconds, so the timeout is approximate. The
default value for timeout is 600 seconds (10 minutes.)
-F The -F option causes pppoe-relay not to fork into the background; instead, it remains in the foreground.
-h The -h option prints a brief usage message and exits.
OPERATION
pppoe-relay listens for incoming PPPoE PADI frames on all interfaces specified with -B or -C options. When a PADI frame appears, pppoe-
relay adds a Relay-Session-ID tag and broadcasts the PADI on all interfaces specified with -B or -S options (except the interface on which
the frame arrived.)
Any PADO frames received are relayed back to the client which sent the PADI (assuming they contain valid Relay-Session-ID tags.) Likewise,
PADR frames from clients are relayed back to the matching access concentrator.
When a PADS frame is received, pppoe-relay enters the two peers' MAC addresses and session-ID's into a hash table. (The session-ID seen by
the access concentrator may be different from that seen by the client; pppoe-relay must renumber sessions to avoid the possibility of
duplicate session-ID's.) Whenever either peer sends a session frame, pppoe-relay looks up the session entry in the hash table and relays
the frame to the correct peer.
When a PADT frame is received, pppoe-relay relays it to the peer and deletes the session entry from its hash table.
If a client and server crash (or frames are lost), PADT frames may never be sent, and pppoe-relay's hash table can fill up with stale ses-
sions. Therefore, a session-cleaning routine runs periodically, and removes old sessions from the hash table. A session is considered
"old" if no traffic has been seen within timeout seconds. When a session is deleted because of a timeout, a PADT frame is sent to each
peer to make certain that they are aware the session has been killed.
EXAMPLE INVOCATIONS
pppoe-relay -C eth0 -S eth1
The example above relays frames between PPPoE clients on the eth0 network and PPPoE servers on the eth1 network.
pppoe-relay -B eth0 -B eth1
This example is a transparent relay -- frames are relayed between any mix of clients and servers on the eth0 and eth1 networks.
pppoe-relay -S eth0 -C eth1 -C eth2 -C eth3
This example relays frames between servers on the eth0 network and clients on the eth1, eth2 and eth3 networks.
AUTHORS
pppoe-relay was written by David F. Skoll <dfs@roaringpenguin.com>.
The pppoe home page is http://www.roaringpenguin.com/pppoe/.
SEE ALSO pppoe-start(8), pppoe-stop(8), pppoe-connect(8), pppd(8), pppoe.conf(5), pppoe(8), pppoe-setup(8), pppoe-status(8), pppoe-sniff(8), pppoe-
server(8)4th Berkeley Distribution 26 January 2001 PPPOE-RELAY(8)