Very Computer

Need some pointers at configuring a linux laptop to be able to access
a local network while making a ppp connection to the WAN.

using:
mdk9.2
kppp

THX

"Routing" is the key for that. - See the Networking-HowTo and others.
If that's not enough, see "Linux Advanced Routing", on the web at
"lartc.org" or "Adv-Routing-HowTo".

Cheers, Jack.

--
----------------------------------------------------------------------
My personal reading of the string "MicroSoft" expands to "NanoWeak"...

If there is a problem then you need to post more information.  At a
minimum that would be a narrative description of the problem.

If this is a request for general instructions then consult the PPP
HOWTO to setup dial out PPP or, better,

http://www.theory.physics.ubc.ca/ppp-linux.html

and make sure there is no default route to the LAN.

--

PPP-Q&A links, downloads:                      http://ckite.no-ip.net/

Sorry, I was tired last night and really thought I put in enough info,
to only read it today and go??

My only unknowns here are how to I guess "route" the LAN. I use them
presently one at a time. KPPP has been great and does some things I
have never been able to accomplish using anything else. So..

I will check these links for hints. I am thinking that I need to route
the lan, or "eth0" for my 192.168.*.* somehow and to keep it that way
while when kppp is brought up to become the route for anything else.
THX

Something's really wrong if you don't have a network route such as

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0

on each LAN host.

That's all you need for the LAN hosts to communicate with one another.

If there's a default route through the LAN interface on the PPP host
then remove it.  Kppp is a frontend to pppd and the standard pppd
won't set a default route if one already exists.  How you remove it
permanently depends on the distribution.

--

PPP-Q&A links, downloads:                      http://ckite.no-ip.net/
/* The wealth of a nation is created by the productive labor of its
 * citizens. */

Quote:> Need some pointers at configuring a linux laptop to be able to access
> a local network while making a ppp connection to the WAN.

The local ethernet would be accessable by default, if the firewall isnt
customised to stop it.
(eg turn off the firewall first and test, to see ? )

IF the local lan is  at work and you have  a group of ethernets to access,
then you need to add routes to these ethernets (specified by their network
adress and netmask) to go via the gateway on the ethernet you plug into

if network 192.168.1.0 is connected to gw1 and 192.168.2.0 is connected to a
different gateway, then

route add 192.168.1.0/255.255.255.0 gw 192.168.10.1
route add 192.168.2.0/255.255.255.0 gw 192.168.10.2

often you just need the full list of networks and netmasks, and just one
gateway that can reach them all.

The PPP then has the default route, and can access the entire internet...

Quote:

> using:
> mdk9.2
> kppp

> THX

Ok,
I have them both working, but, and perhaps this might have been a good
thing to say before,, I have a pcmcia ethernet. kppp will dial out and
do it's thing but not be able to start the pppd with the ethernet
pugged in. I have tried selecting and unselecting the "Default Route"
check box within kppp to no avail. Now, if I unplug the pcmcia
ethernet and then start kppp it will log on and start pppd. To get
both working simultaneously as they are at this moment, I must start
kppp with the ethernet unplugged and then after the ppp0 is up,
hotplug the pcmcia ethernet.

Here's route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref  
Use Iface
216.231.162.14  0.0.0.0         255.255.255.255 UH    0      0      
0 ppp0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0      
0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0      
0 lo
0.0.0.0         216.231.162.14  0.0.0.0         UG    0      0      
0 ppp0

THX

Of course it can! You don't mean to say that at all! You mean to say
that it won't set a default route, since one is already set.

Well, unset it first! Or don't set it! What's the point of having
a serial connection up when you already have an ethernet?

Quote:> pugged in. I have tried selecting and unselecting the "Default Route"
> check box within kppp to no avail.

Who cares! Just unset your default route to eth0, since you don't want
it!

Quote:> Now, if I unplug the pcmcia
> ethernet and then start kppp it will log on and start pppd. To get

It'll do so anyway.

Quote:> both working simultaneously as they are at this moment, I must start
> kppp with the ethernet unplugged and then after the ppp0 is up,
> hotplug the pcmcia ethernet.

Please don't dissemble.  You know perfectly well that this is a tissue
of imagined falsehoods.  Both eth0 and ppp start fine - all that is
happening is that pppd won't set a default route when there is already
one set (to WHERE!!!!???  What's the point in setting a default route to
nowhere?  don't set it if you don't want it!).  So don't set it!  Unset
it, and then start your serial connection.

Quote:> Here's route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref   Use Iface
> 216.231.162.14  0.0.0.0         255.255.255.255 UH    0      0       0 ppp0
> 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0       0 eth0

There you are  - your lie is exposed. You can see both eth0 and ppp0.

Quote:> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0       0 lo
> 0.0.0.0         216.231.162.14  0.0.0.0         UG    0      0       0 ppp0

And here you can see a correct default route through ppp0. So nothing to worry
about!

Peter

Yeah, that's not what I meant by default route through the LAN interface.
Selecting that almost certainly tells kppp to use the pppd defaultroute
option and you'll need that - unless you choose the alternative suggested
below.

Quote:> ethernet and then start kppp it will log on and start pppd. To get
> both working simultaneously as they are at this moment, I must start
> kppp with the ethernet unplugged and then after the ppp0 is up,
> hotplug the pcmcia ethernet.
> Here's route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref  
> Use Iface
> 216.231.162.14  0.0.0.0         255.255.255.255 UH    0      0      
> 0 ppp0
> 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0      
> 0 eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0      
> 0 lo
> 0.0.0.0         216.231.162.14  0.0.0.0         UG    0      0      
> 0 ppp0

The last line shows a default route through the PPP interface (ppp0).

There's no default route through the LAN interface there, but it still
sounds like it's an existing default route problem.  Pppd won't add
a default route through the PPP interface if a default route already
exists to anywhere, even with the defaultroute option.  What does the
routing look like when the LAN is active but before the PPP link is
ever brought up?  In particular, is there a default route through eth0?

It may be that there is a LAN default route that is not set when there
is an existing default route at the time the LAN is activated - in the
manner of pppd.  That could most likely be changed by a distribution
network configuration script.

Alternately, you could just add the line

/sbin/route add default $IFNAME

to /etc/ppp/ip-up, which should override any existing LAN default route
for the duration of the PPP link.  See man pppd for an explanation of
IFNAME.

--

PPP-Q&A links, downloads:                      http://ckite.no-ip.net/

http://www.oneway.com/scooter/liar.jpg

Perhaps I should just had said,, I have no idea what I am doing and
should just pack up like all the others living well and outside in the
world and leave this to you. Unfortunately in many other ways it is
not possible for me, yet could use the extra time towards something
more my inclanation.

Sorry for the inconvenience,
Scott

This is a kppp error being displayed.  It means nothing in itself -
kppp's only a gui.  kppp has no difficulty starting pppd.  But what pppd
does after that is up to pppd!  If pppd has a problem, it will tell you
about it, but it will not be due to your running ethernet at the same
time (it may be a collateral effect of something else you did while
setting up ethernet).  In particular it may well be protesting about the
existence of a default route - looking at what pppd says will tell you
more.

So I would imagine that you already have a default route set and you want
to remove it first in order to let pppd set the default route, as you
requested it to do.

Show us the error log from pppd, and we, and you, will know.

Quote:> Perhaps I should just had said,, I have no idea what I am doing and
> should just pack up like all the others living well and outside in the

Eh?

Quote:> world and leave this to you. Unfortunately in many other ways it is
> not possible for me, yet could use the extra time towards something
> more my inclanation.

A first step would be to report what you see, and not place (false!)
interpretations on it, and most especially keep them to yourself if you
do insist on making false interpretations. They're less annoying that
way.

Peter

Sorry, I didn't read that carefully.  It took the liar.jpg file to show
me what you meant (two firsts for me there, first time I've seen the
kppp GUI and the first time I've seen a jpg that would enlarge itself
at the click of the mouse).

It could be an IRQ conflict problem.  The IRQ being used by the PCMCIA
Ethernet when it is already up may be the same as pppd uses, in which
case the the PPP negotiations might well fail.  If the PPP link is
already up when the PCMCIA card is plugged in then the IRQ selected
for it may be automatic and assign a different IRQ so everything works.

All said in the paragraph above assumes certain things are true about
hot-plugging, and hardware that I've either not used at all, or used
only marginally.

Check the IRQs with "cat /proc/interrupts" to see if that's the problem.

If it is the problem then you'll need to assign the modem to a different
serial device file (COM port) and so a different IRQ, or find a way to
reserve the modem's IRQ and keep the PCMCIA card from grabbing it when
it's plugged in and no PPP link is up.

PPP-Q&A links, downloads:                      http://ckite.no-ip.net/
/*   In his wisdom RMS decided that people need no man pages when they can
  use GNU's beautiful info system.
     Unfortunately, everybody I know greatly prefers man pages.
                 - From the man-pages-1.55/man1/README */

pppd does not use an irq - it's an application, a user space program.
The serial port will use an irq, but there will not normally be a clash
with the port used by a pcmcia controller (or card?).  It may happen,
however.  Both may be on 3, for example, in which case the OP may well
have to configure your pcmcia controller to use another port.

I agree, it's a possibility, but not a great one since you can see that
the modem worked fine in itself - it dialed out viat at*, and made a
connect. That's shown on the kppp log console. That could not happen if
there were an irq conflict.

Quote:> case the the PPP negotiations might well fail.  If the PPP link is
> already up when the PCMCIA card is plugged in then the IRQ selected
> for it may be automatic and assign a different IRQ so everything works.

It's a remote possibility, but I don't think that mechanism exists.
It's impossible to say for certain without looking at the rq selection
code in the pcmcia controller driver.

Quote:> All said in the paragraph above assumes certain things are true about
> hot-plugging, and hardware that I've either not used at all, or used
> only marginally.
> Check the IRQs with "cat /proc/interrupts" to see if that's the problem.

He wouldn't see it straight off. Only one or the other would show up if
that were the case. But yes, he needs to look at which irq he is using
for his serial port and which for his cmcia controller.

Quote:> If it is the problem then you'll need to assign the modem to a different
> serial device file (COM port) and so a different IRQ, or find a way to
> reserve the modem's IRQ and keep the PCMCIA card from grabbing it when

Modem?  What modem? Are you saying that he has an internal modem?

Quote:> it's plugged in and no PPP link is up.

Imposible to say what's going on without more data!

Peter

Leon,
Based on your answer below, I'm sure you'll solve my problem easily.

I have a simple lan, 2 linux PCs connected via a router. they both
have Class C addresses (192.168.0.100/101). The router is 192.168.0.1

PC 1 dials out (pppd) to the web and can browse the web, get mail no
problem. Both PCs can see each other (ping) and I can mount ext2
volumes from one PC to the other.

PROBLEM: PC 2 cannot ping any web addresses. I run squid on PC1 and
tell the browser on PC 2 to connect via the squid proxy on PC 1 ...
this works fine but I need to have PC 2 see the web directly.

I think this is a route command using gateway issue but I don't know
enough about it. PC1 is dynamically assigned an IP address by my ISP.

Thanks,
Asher