Comment 18 for bug 290639
Revision history for this message
| Yigit Güneli (yiit) wrote Re: [Intrepid] network-manager only allows to use either eth0 or ppp0 | #18 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Sam is living in an university campus.
He has a laptop which has only one ethernet port.
He plugs the cable and gets ip adress for eth0 from dhcp (192.168.1.x) He is able to access his roommate John's computer which has an ip of 192.168.1.y
Then he wants to connect to the internet, use NM for pppoe connection. Now he got 181.x.x.x ip for ppp0 and lost the connection to John's computer.
(He could have used first nm to connect to pppoe, then ifconfig eth0 to eth0 to have access for both networks. But he doesn't know and care about this command since he thinks nm does manage the all networks.)
He is unhappy with this problem, and tries windows.
He connects to lan with 192.168.1.x ip (only with dhcp)
He connects to wan with 181.x.x.x ip (with pppoe)
Now he has the access to both wan and lan since windows can handle pppoe and ethernet connection at the same time.
I am living in this campus. We have a DC server on 192.168.1.1-255 network, but we use pppoe for validating our username, password and mac adress. At this moment, Windows users could both surf the internet and use DC, but NM users can not do this in linux.