🚀 go-pugleaf

Hey thanks for the link. The default root is set up to be the ppp interface and
not the ethernet.

Let me show you my route. Its pretty common setup...
192.168.1.1     *               255.255.255.255 UH    0      0        0 eth1
255.255.255.255 *               255.255.255.255 UH    0      0        0 eth1
a.a.a.a   *               255.255.255.255 UH    0      0        0 ppp0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         a.a.a.a   0.0.0.0         UG    0      0        0 ppp0
(IP addresses have been changed to protect the innocent)
I took out all instances of eth0 since it is just a vehicle for ppp0... (Is
this good logic?)

wait a second, I think I spotted it!
when I start pppoe and the ppp0 interface is established, the ip address
in the routing table does not match the ip when I do an ifconfig... Go
figure...

Here's the ifconfig...
eth0      Link encap:Ethernet  HWaddr AA:AA:AA:AA:AA:AA
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4762 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:5 Base address:0xe400

eth1      Link encap:Ethernet  HWaddr AA:AA:AB:BB:BB:BB
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1125 errors:0 dropped:0 overruns:0 frame:0
          TX packets:145 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:11 Base address:0xe800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:110 errors:0 dropped:0 overruns:0 frame:0
          TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

ppp0      Link encap:Point-to-Point Protocol
          inet addr:b.b.b.b  P-t-P:c.c.c.c  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
(again IP addresses have been changed to protect the innocent)

Notice a.a.a.a does not match b.b.b.b in ppp0.

Any idea what might cause this? Maybe NTS or ppp???

This is pretty screwy...

Many thanks...
Dave

Frank van Schie wrote:

> Dave wrote:
> >
> > Well the readme that is on the NTS CD (in the linux directory specifically
> > says to
> > initialize the ethernet device to the ip address 0.0.0.0. I have a feeling
> > that this has
> > got to mess with the broadcast in some way...
>
> The default route gets a numerical destination value of 0.0.0.0, which
> is your eth interface then. Seems to me to be causing the problem.
>
> > I'll try it. I think that would make sense. Is 10.0.0.1 an in-use address
> > on the internet?
>
> No, it's part of one of the (I think) 16 consecutive Class B networks?
> Definitely free space.
>
> > I would also like to get my hands on v1.3 of the NTS client. Any word on
> > how to get it
> > or do I have to call for a serviceman to bring it to my door (They do that
> > for me????)
>
> Well, personally I work at my ISP, which kinda gives me a connection
> (through some people) to NTS, the people who make the stuff. You'd have
> to mail/phone your provider's helpdesk to ask for whether they have also
> licensed a linux client. If they did, then you can probably ask them for
> it.
>
> Another place to look at: http://www.roaringpenguin.com/
> Their client seems heavily 'inspired' by the NTS Enternet software. :-)
> Even v1.3 of it. So that might be a good bet otherwise. Plus it's 100%
> free.
>
> --
> Frank