LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 12-16-2010, 11:55 PM   #1
issacnewton
LQ Newbie
 
Registered: Dec 2010
Location: Mumbai, India
Distribution: Debian
Posts: 16

Rep: Reputation: 0
configuring pppoe for internet


Hi

I finally managed to install pppoe and pppoeconf. When I
type command 'pppoeconf' , it invokes some window and I put username, passwd etc. But my net connection won't start. I have posting the output of various commands related to networking.

ifconfig

Code:
eth0      Link encap:Ethernet  HWaddr 
00:0f:b0:4a:54:a7 inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:b0ff:fe4a:54a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1388 errors:0 dropped:0 overruns:0 frame:0 TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:437394 (427.1 KiB) TX bytes:6594 (6.4 KiB) Interrupt:18 Base address:0x7000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)
interfaces

Code:
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf provider dsl-provider
lspci

Code:
00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4) 00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev a6) 00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4) 00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5) 00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5) 00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 Audio (rev a2) 00:06.1 Modem: nVidia Corporation nForce3 Audio (rev a2) 00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5) 00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go 32M] (rev a3) 02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) 02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) 02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) 02:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading Function (rev 01)
plog

Code:
Dec 17 02:06:57 physics pppd[4029]: Connection terminated. Dec 17 02:07:27 physics pppd[4029]: PPP session is 37700 Dec 17 02:07:27 physics pppd[4029]: Using interface ppp0 Dec 17 02:07:27 physics pppd[4029]: Connect: ppp0 <--> eth0 Dec 17 02:07:27 physics pppd[4029]: Remote message: Authentication failure Dec 17 02:07:27 physics pppd[4029]: PAP authentication failed Dec 17 02:07:27 physics pppd[4029]: Connection terminated. Dec 17 02:07:27 physics pppd[4029]: Exit. Dec 17 02:20:25 physics pppd[4147]: In file /etc/ppp/peers/provider: unrecognized option '/dev/modem'
One thing I have noticed is that my MAC address is that of my own laptop. But we have given the MAC address of my brother's laptop to my ISP. And when I am in windows, I clone his MAC address.
So maybe I need to that in Debian. Can you see any other problem ? So suggest me how do I clone MAC address in linux.
By the way , I have learned how to redirect the output
of Linux commands to txt files to post here. I had to
first convert txt files in Linux to txt files in Dos
so that I can post them here (I have to use Win XP for internet)

Last edited by issacnewton; 12-16-2010 at 11:56 PM.
 
Old 12-17-2010, 08:18 AM   #2
Samotnik
Member
 
Registered: Jun 2006
Location: Belarus
Distribution: Debian GNU/Linux testing/unstable
Posts: 471

Rep: Reputation: 40
It's possible.
You can change MAC address in linux with ip command ip link set eth0 address <new_mac> or with old ifconfig command ifconfig eth0 hw ether <new_mac>
 
Old 12-17-2010, 09:54 AM   #3
issacnewton
LQ Newbie
 
Registered: Dec 2010
Location: Mumbai, India
Distribution: Debian
Posts: 16

Original Poster
Rep: Reputation: 0
samotnik,
I tried that and nothing happened. No internet. If you want to analyse, please suggest which
command's output should I post here
 
Old 12-17-2010, 11:59 AM   #4
ilvista
Member
 
Registered: Nov 2010
Location: Ghazaouet
Distribution: Fedora OpenSuse
Posts: 150

Rep: Reputation: 21
try this:

http://mybroadband.co.za/vb/showthre...432#post970432

good luck
 
Old 12-17-2010, 11:59 AM   #5
ilvista
Member
 
Registered: Nov 2010
Location: Ghazaouet
Distribution: Fedora OpenSuse
Posts: 150

Rep: Reputation: 21
try this:

http://mybroadband.co.za/vb/showthre...432#post970432

good luck
 
Old 12-17-2010, 12:08 PM   #6
repo
LQ 5k Club
 
Registered: May 2001
Location: Belgium
Distribution: Arch
Posts: 8,528

Rep: Reputation: 899Reputation: 899Reputation: 899Reputation: 899Reputation: 899Reputation: 899Reputation: 899
Did the mac address changed ?
Error messages?
Quote:
Dec 17 02:07:27 physics pppd[4029]: PAP authentication failed
Does the ISP use pap or chap ?

Kind regards
 
Old 12-17-2010, 07:20 PM   #7
Samotnik
Member
 
Registered: Jun 2006
Location: Belarus
Distribution: Debian GNU/Linux testing/unstable
Posts: 471

Rep: Reputation: 40
Quote:
Dec 17 02:07:27 physics pppd[4029]: Remote message: Authentication failure
Dec 17 02:07:27 physics pppd[4029]: PAP authentication failed
It means that for some reason you ISP don't want to recognize you.
Than first, check if MAC address is correct. Check, if your username and password are correct. They are found in /etc/ppp/pap-secrets and /etc/ppp/chap-secrets as pairs "username" * "password" (You can access this files only as root). If password is incorrect, then correct it. If username is incorrect, then correct it, then correct user option in /etc/ppp/peers/dsl-provider.

After all, as mentioned by repo, PAP authentication is very insecure, because password is transmitted as plain text. If your ISP supports authentication through CHAP, you would prohibit PAP authentication by adding -pap in /etc/ppp/options.
 
Old 12-18-2010, 07:08 AM   #8
issacnewton
LQ Newbie
 
Registered: Dec 2010
Location: Mumbai, India
Distribution: Debian
Posts: 16

Original Poster
Rep: Reputation: 0
Hi

Thanks for responses. Here is some more info I want to share. I am in Win xp now.

Device Name - WAN Miniport (PPPOE)
Device Type- PPPoE
Server Type- PPP
Authentication - PAP
Compression- none
PPP multilink framing OFF
Server IP Address- 203.187.210.1
Client IP Address- 123.201.200.227

So, repo, its seems my ISP uses PAP. Now samotnik, I checked all the files you mentioned.
and the username and paasswd is ok. I am posting some files from /etc/ppp

pap-secrets
Code:
# # /etc/ppp/pap-secrets # # This is a pap-secrets file to be used with the AUTO_PPP function of # mgetty. mgetty-0.99 is preconfigured to startup pppd with the login option # which will cause pppd to consult /etc/passwd (and /etc/shadow in turn) # after a user has passed this file. Don't be disturbed therefore by the fact # that this file defines logins with any password for users. /etc/passwd # (again, /etc/shadow, too) will catch passwd mismatches. # # This file should block ALL users that should not be able to do AUTO_PPP. # AUTO_PPP bypasses the usual login program so it's necessary to list all # system userids with regular passwords here. # # ATTENTION: The definitions here can allow users to login without a # password if you don't use the login option of pppd! The mgetty Debian # package already provides this option; make sure you don't change that. # INBOUND connections # Every regular user can use PPP and has to use passwords from /etc/passwd * hostname "" * # UserIDs that cannot use PPP at all. Check your /etc/passwd and add any # other accounts that should not be able to use pppd! guest hostname "*" - master hostname "*" - root hostname "*" - support hostname "*" - stats hostname "*" - # OUTBOUND connections # Here you should add your userid password to connect to your providers via # PAP. The * means that the password is to be used for ANY host you connect # to. Thus you do not have to worry about the foreign machine name. Just # replace password with your password. # If you have different providers with different passwords then you better # remove the following line. # * password "username" * "801154"
I have replaced the username with "username" for privacy reasons. Its there.

Now /etc/ppp/chap-secrets (again username is replaced with "username". Password is as it is.

Code:
# Secrets for authentication using CHAP # client server secret IP addresses "username" * "801154"
Now /etc/ppp/peers/provider

Code:
# example configuration for a dialup connection authenticated with PAP or CHAP # # This is the default configuration used by pon(1) and poff(1). # See the manual page pppd(8) for information on all the options. # MUST CHANGE: replace myusername@realm with the PPP login name given to # your by your provider. # There should be a matching entry with the password in /etc/ppp/pap-secrets # and/or /etc/ppp/chap-secrets. user "myusername@realm" # MUST CHANGE: replace ******** with the phone number of your provider. # The /etc/chatscripts/pap chat script may be modified to change the # modem initialization string. connect "/usr/sbin/chat -v -f /etc/chatscripts/pap -T ********" # Serial device to which the modem is connected. /dev/modem # Speed of the serial line. 115200 # Assumes that your IP address is allocated dynamically by the ISP. noipdefault # Try to get the name server addresses from the ISP. usepeerdns # Use this connection as the default route. defaultroute # Makes pppd "dial again" when the connection is lost. persist # Do not ask the remote to authenticate. noauth
Now /etc/ppp/peers/dsl-provider
Again I have removed my username and replaced it with the words "username". But believe me
its there

Code:
# Configuration file for PPP, using PPP over Ethernet # to connect to a DSL provider. # # See the manual page pppd(8) for information on all the options. ## # Section 1 # # Stuff to configure... # MUST CHANGE: Uncomment the following line, replacing the user@provider.net # by the DSL user name given to your by your DSL provider. # (There should be a matching entry in /etc/ppp/pap-secrets with the password.) #user myusername@myprovider.net # Use the pppoe program to send the ppp packets over the Ethernet link # This line should work fine if this computer is the only one accessing # the Internet through this DSL connection. This is the right line to use # for most people. #pty "/usr/sbin/pppoe -I eth0 -T 80 -m 1452" # An even more conservative version of the previous line, if things # don't work using -m 1452... #pty "/usr/sbin/pppoe -I eth0 -T 80 -m 1412" # If the computer connected to the Internet using pppoe is not being used # by other computers as a gateway to the Internet, you can try the following # line instead, for a small gain in speed: #pty "/usr/sbin/pppoe -I eth0 -T 80" # The following two options should work fine for most DSL users. # Assumes that your IP address is allocated dynamically # by your DSL provider... noipdefault # Try to get the name server addresses from the ISP. usepeerdns # Use this connection as the default route. # Comment out if you already have the correct default route installed. defaultroute ## # Section 2 # # Uncomment if your DSL provider charges by minute connected # and you want to use demand-dialing. # # Disconnect after 300 seconds (5 minutes) of idle time. #demand #idle 300 ## # Section 3 # # You shouldn't need to change these options... hide-password lcp-echo-interval 20 lcp-echo-failure 3 # Override any connect script that may have been set in /etc/ppp/options. connect /bin/true noauth persist mtu 1492 # RFC 2516, paragraph 7 mandates that the following options MUST NOT be # requested and MUST be rejected if requested by the peer: # Address-and-Control-Field-Compression (ACFC) noaccomp # Asynchronous-Control-Character-Map (ACCM) default-asyncmap plugin rp-pppoe.so eth0 user "username"
Now I am posting /etc/ppp/options

Code:
# /etc/ppp/options # # Originally created by Jim Knoble <jmknoble@mercury.interpath.net> # Modified for Debian by alvar Bray <alvar@meiko.co.uk> # Modified for PPP Server setup by Christoph Lameter <clameter@debian.org> # # To quickly see what options are active in this file, use this command: # egrep -v '#|^ *$' /etc/ppp/options # Specify which DNS Servers the incoming Win95 or WinNT Connection should use # Two Servers can be remotely configured # ms-dns 192.168.1.1 # ms-dns 192.168.1.2 # Specify which WINS Servers the incoming connection Win95 or WinNT should use # ms-wins 192.168.1.50 # ms-wins 192.168.1.51 # Run the executable or shell command specified after pppd has # terminated the link. This script could, for example, issue commands # to the modem to cause it to hang up if hardware modem control signals # were not available. #disconnect "chat -- \d+++\d\c OK ath0 OK" # async character map -- 32-bit hex; each bit is a character # that needs to be escaped for pppd to receive it. 0x00000001 # represents '\x01', and 0x80000000 represents '\x1f'. asyncmap 0 # Require the peer to authenticate itself before allowing network # packets to be sent or received. # Please do not disable this setting. It is expected to be standard in # future releases of pppd. Use the call option (see manpage) to disable # authentication for specific peers. auth # Use hardware flow control (i.e. RTS/CTS) to control the flow of data # on the serial port. crtscts # Use software flow control (i.e. XON/XOFF) to control the flow of data # on the serial port. #xonxoff # Specifies that certain characters should be escaped on transmission # (regardless of whether the peer requests them to be escaped with its # async control character map). The characters to be escaped are # specified as a list of hex numbers separated by commas. Note that # almost any character can be specified for the escape option, unlike # the asyncmap option which only allows control characters to be # specified. The characters which may not be escaped are those with hex # values 0x20 - 0x3f or 0x5e. #escape 11,13,ff # Don't use the modem control lines. #local # Specifies that pppd should use a UUCP-style lock on the serial device # to ensure exclusive access to the device. lock # Don't show the passwords when logging the contents of PAP packets. # This is the default. hide-password # When logging the contents of PAP packets, this option causes pppd to # show the password string in the log message. #show-password # Use the modem control lines. On Ultrix, this option implies hardware # flow control, as for the crtscts option. (This option is not fully # implemented.) modem # Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd # will ask the peer to send packets of no more than <n> bytes. The # minimum MRU value is 128. The default MRU value is 1500. A value of # 296 is recommended for slow links (40 bytes for TCP/IP header + 256 # bytes of data). #mru 542 # Set the interface netmask to <n>, a 32 bit netmask in "decimal dot" # notation (e.g. 255.255.255.0). #netmask 255.255.255.0 # Disables the default behaviour when no local IP address is specified, # which is to determine (if possible) the local IP address from the # hostname. With this option, the peer will have to supply the local IP # address during IPCP negotiation (unless it specified explicitly on the # command line or in an options file). #noipdefault # Enables the "passive" option in the LCP. With this option, pppd will # attempt to initiate a connection; if no reply is received from the # peer, pppd will then just wait passively for a valid LCP packet from # the peer (instead of exiting, as it does without this option). #passive # With this option, pppd will not transmit LCP packets to initiate a # connection until a valid LCP packet is received from the peer (as for # the "passive" option with old versions of pppd). #silent # Don't request or allow negotiation of any options for LCP and IPCP # (use default values). #-all # Disable Address/Control compression negotiation (use default, i.e. # address/control field disabled). #-ac # Disable asyncmap negotiation (use the default asyncmap, i.e. escape # all control characters). #-am # Don't fork to become a background process (otherwise pppd will do so # if a serial device is specified). #-detach # Disable IP address negotiation (with this option, the remote IP # address must be specified with an option on the command line or in # an options file). #-ip # Disable IPCP negotiation and IP communication. This option should # only be required if the peer is buggy and gets confused by requests # from pppd for IPCP negotiation. #noip # Disable magic number negotiation. With this option, pppd cannot # detect a looped-back line. #-mn # Disable MRU [Maximum Receive Unit] negotiation (use default, i.e. # 1500). #-mru # Disable protocol field compression negotiation (use default, i.e. # protocol field compression disabled). #-pc # Require the peer to authenticate itself using PAP. #+pap # Don't agree to authenticate using PAP. #-pap # Require the peer to authenticate itself using CHAP [Cryptographic # Handshake Authentication Protocol] authentication. #+chap # Don't agree to authenticate using CHAP. #-chap # Disable negotiation of Van Jacobson style IP header compression (use # default, i.e. no compression). #-vj # Increase debugging level (same as -d). If this option is given, pppd # will log the contents of all control packets sent or received in a # readable form. The packets are logged through syslog with facility # daemon and level debug. This information can be directed to a file by # setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If # pppd is compiled with extra debugging enabled, it will log messages # using facility local2 instead of daemon). #debug # Append the domain name <d> to the local host name for authentication # purposes. For example, if gethostname() returns the name porsche, # but the fully qualified domain name is porsche.Quotron.COM, you would # use the domain option to set the domain name to Quotron.COM. #domain <d> # Enable debugging code in the kernel-level PPP driver. The argument n # is a number which is the sum of the following values: 1 to enable # general debug messages, 2 to request that the contents of received # packets be printed, and 4 to request that the contents of transmitted # packets be printed. #kdebug n # Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer # requests a smaller value via MRU negotiation, pppd will request that # the kernel networking code send data packets of no more than n bytes # through the PPP network interface. #mtu <n> # Set the name of the local system for authentication purposes to <n>. # This is a privileged option. With this option, pppd will use lines in the # secrets files which have <n> as the second field when looking for a # secret to use in authenticating the peer. In addition, unless overridden # with the user option, <n> will be used as the name to send to the peer # when authenticating the local system to the peer. (Note that pppd does # not append the domain name to <n>.) #name <n> # Enforce the use of the hostname as the name of the local system for # authentication purposes (overrides the name option). #usehostname # Set the assumed name of the remote system for authentication purposes # to <n>. #remotename <n> # Add an entry to this system's ARP [Address Resolution Protocol] # table with the IP address of the peer and the Ethernet address of this # system. proxyarp # Use the system password database for authenticating the peer using # PAP. Note: mgetty already provides this option. If this is specified # then dialin from users using a script under Linux to fire up ppp wont work. # login # If this option is given, pppd will send an LCP echo-request frame to the # peer every n seconds. Normally the peer should respond to the echo-request # by sending an echo-reply. This option can be used with the # lcp-echo-failure option to detect that the peer is no longer connected. lcp-echo-interval 30 # If this option is given, pppd will presume the peer to be dead if n # LCP echo-requests are sent without receiving a valid LCP echo-reply. # If this happens, pppd will terminate the connection. Use of this # option requires a non-zero value for the lcp-echo-interval parameter. # This option can be used to enable pppd to terminate after the physical # connection has been broken (e.g., the modem has hung up) in # situations where no hardware modem control lines are available. lcp-echo-failure 4 # Set the LCP restart interval (retransmission timeout) to <n> seconds # (default 3). #lcp-restart <n> # Set the maximum number of LCP terminate-request transmissions to <n> # (default 3). #lcp-max-terminate <n> # Set the maximum number of LCP configure-request transmissions to <n> # (default 10). #lcp-max-configure <n> # Set the maximum number of LCP configure-NAKs returned before starting # to send configure-Rejects instead to <n> (default 10). #lcp-max-failure <n> # Set the IPCP restart interval (retransmission timeout) to <n> # seconds (default 3). #ipcp-restart <n> # Set the maximum number of IPCP terminate-request transmissions to <n> # (default 3). #ipcp-max-terminate <n> # Set the maximum number of IPCP configure-request transmissions to <n> # (default 10). #ipcp-max-configure <n> # Set the maximum number of IPCP configure-NAKs returned before starting # to send configure-Rejects instead to <n> (default 10). #ipcp-max-failure <n> # Set the PAP restart interval (retransmission timeout) to <n> seconds # (default 3). #pap-restart <n> # Set the maximum number of PAP authenticate-request transmissions to # <n> (default 10). #pap-max-authreq <n> # Set the maximum time that pppd will wait for the peer to authenticate # itself with PAP to <n> seconds (0 means no limit). #pap-timeout <n> # Set the CHAP restart interval (retransmission timeout for # challenges) to <n> seconds (default 3). #chap-restart <n> # Set the maximum number of CHAP challenge transmissions to <n> # (default 10). #chap-max-challenge # If this option is given, pppd will rechallenge the peer every <n> # seconds. #chap-interval <n> # With this option, pppd will accept the peer's idea of our local IP # address, even if the local IP address was specified in an option. #ipcp-accept-local # With this option, pppd will accept the peer's idea of its (remote) IP # address, even if the remote IP address was specified in an option. #ipcp-accept-remote # Disable the IPXCP and IPX protocols. # To let pppd pass IPX packets comment this out --- you'll probably also # want to install ipxripd, and have the Internal IPX Network option enabled # in your kernel. /usr/doc/HOWTO/IPX-HOWTO.gz contains more info. noipx # Exit once a connection has been made and terminated. This is the default, # unless the `persist' or `demand' option has been specified. #nopersist # Do not exit after a connection is terminated; instead try to reopen # the connection. #persist # Terminate after n consecutive failed connection attempts. # A value of 0 means no limit. The default value is 10. #maxfail <n> # Initiate the link only on demand, i.e. when data traffic is present. # With this option, the remote IP address must be specified by the user on # the command line or in an options file. Pppd will initially configure # the interface and enable it for IP traffic without connecting to the peer. # When traffic is available, pppd will connect to the peer and perform # negotiation, authentication, etc. When this is completed, pppd will # commence passing data packets (i.e., IP packets) across the link. #demand # Specifies that pppd should disconnect if the link is idle for <n> seconds. # The link is idle when no data packets (i.e. IP packets) are being sent or # received. Note: it is not advisable to use this option with the persist # option without the demand option. If the active-filter option is given, # data packets which are rejected by the specified activity filter also # count as the link being idle. #idle <n> # Specifies how many seconds to wait before re-initiating the link after # it terminates. This option only has any effect if the persist or demand # option is used. The holdoff period is not applied if the link was # terminated because it was idle. #holdoff <n> # Wait for up n milliseconds after the connect script finishes for a valid # PPP packet from the peer. At the end of this time, or when a valid PPP # packet is received from the peer, pppd will commence negotiation by # sending its first LCP packet. The default value is 1000 (1 second). # This wait period only applies if the connect or pty option is used. #connect-delay <n> # Packet filtering: for more information, see pppd(8) # Any packets matching the filter expression will be interpreted as link # activity, and will cause a "demand" connection to be activated, and reset # the idle connection timer. (idle option) # The filter expression is akin to that of tcpdump(1) #active-filter <filter-expression> # ---<End of File>---
in case you need to see that.

Samontik, as I have said above, my stupid ISP uses PAP and not CHAP. That's what my Win XP network connection says. I asked the people at my ISP and they have set up just 2 connections over linux till date. And that was Red Hat. ISP is

http://www.youbroadband.in/

Net in India is still in Stone Age,unlike EU , USA

ilvista, I will definitely check that link...

As I have already said, my ISP has registered my brother's PC and my brother has cloned MAC address into my PC. But when I do 'ifconfig'
the system still shows my real MAC, not the cloned MAC.

Last edited by issacnewton; 12-18-2010 at 07:12 AM.
 
Old 12-19-2010, 02:06 PM   #9
issacnewton
LQ Newbie
 
Registered: Dec 2010
Location: Mumbai, India
Distribution: Debian
Posts: 16

Original Poster
Rep: Reputation: 0
anybody can help ?
 
Old 12-19-2010, 02:36 PM   #10
ilvista
Member
 
Registered: Nov 2010
Location: Ghazaouet
Distribution: Fedora OpenSuse
Posts: 150

Rep: Reputation: 21
to change the mac
Code:
ifconfig -a | grep HWaddr
and then
Code:
# ifconfig eth0 down
# ifconfig eth0 hw ether xx:xx:xx:xx:xx:xx
# ifconfig eth0 up
# ifconfig eth0 |grep HWaddr
 
Old 12-19-2010, 03:12 PM   #11
ilvista
Member
 
Registered: Nov 2010
Location: Ghazaouet
Distribution: Fedora OpenSuse
Posts: 150

Rep: Reputation: 21
Or you can download macchanger ,and install it and then

Code:
[root@benchabane benchabane]# macchanger eth0
Current MAC: xx:xx:xx:xx:xx:xx (Toshiba)
Faked MAC:   00:1c:7e:b1:db:1f (Toshiba)
for exemple ,change the mac to 00:05:6f:62:ea:b3
Code:
 macchanger --mac=00:05:6f:62:ea:b3 eth0
check if it worked
Code:
ifconfig -a | grep HWaddr
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Missing /var/run/pppoe.conf-pppoe.pid.pppoe file acraig Debian 2 11-02-2010 07:24 PM
[SOLVED] Cannot access internet even PPPoE is up after configuring Samba ethereal1m Linux - Newbie 2 03-31-2010 08:18 AM
Need help about configuring ADSL PPPOE on RedHat 7.2 with Webin or SSH wicko Linux - Newbie 1 12-03-2007 05:50 PM
Configuring How pppoe reconnects anwar Linux - Networking 1 08-10-2005 11:20 AM
configuring openbsd 3.3 pppoe gateway yocompia *BSD 3 09-28-2003 01:11 PM


All times are GMT -5. The time now is 01:23 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration