Mike P <[EMAIL PROTECTED]> wrote: > Hello, > > The pppoe solution has spreaded into my area as i saw > on many providers. I setup a computer with openbsd 3.7 > to act as a router togheter with pf and nat > capabilities. > > After all the settings i did this computer is acting > very strange. The connection is not useable and i > can't continue like this. I never used pppoe so i > decided to test the kernel implementation, seeing in > many articles this is not so overloading for the OS. > > I setup the pppoe0 as the man page says. At boot time > i was able to see all three phases of pppoe connection > (displayed with blue backgroud), but after a while > during daemon initialization i received this errors:
daemon initialization? what daemon? > pppoe*: GENERIC ERROR : RP-PPPoE Remote sends you an error tag, it is RP-PPPoE is your ISP using Linux (Roaring Penguin) or is some other PPPoE server around is interfereing? > Child pppd process terminated FFEDEE... (long string) huh? > pppoe*: GENERIC ERROR : Received PADT. Remote sends you an error tag, telling it Received PADT. Are there any other pppoe talking devices/servers on the network? there is no 'pppd' process anywhere that is needed for in kernel pppoe operation (or even for userland pppoe) you are obviously doing something wrong. > Sometimes, even with those errors, the link is > working. I see this doing an ifconfig -a pppoe0. I 'm > able to see the address. I'm able to ping google.com > and the DNS server. Yes it works, I use it in production. Try a snapshot or 3.8 when it comes out. In kernel pppoe had some problems with keeping connections alive in 3.7. > Sometimes, the ifconfig -a pppoe0 reports the session > as being ok, but i'm able to ping only the DNS server > of my ISP, not google.com. I tried a traceroute to > google.com and it looks like the packets cannot travel > thru a computer from my ISP. routing or ISP problems? Sometimes ISP's allow the connection but hand out different IP blocks (with no outside connection) if you fail to authenticate (or provide a different/wrong access concentrator name) > Sometimes, even the ifconfig -a pppoe reports link ok, > i'm not able to ping something. although ping is not the ultimate connectivity test nowadays, it looks loke you have some kind of configuration problem. You could try to get packet dumps using tcpdump from the underlying ethernet device (I dont know which because you have not provided any configuration information). > This is a random behaviour, with all three situation > alternating. I wasn't able to relate somehow this > behaviour to something. From a Windows xp computer, > the connection works very good. > > I didn't paste the settings here, because i did them > like in the man page, i even tried some examples from > internet. You obviously did something wrong. But without any information about how you set things up, it is hard to tell. Even if your setup were correct, you should still send information about your configuration and the dmesg so that we can diagnose any problems (it is ok to change/obfuscate any login information). At this point, the only thing I can say is that you messed something up with configuration. > Having all these, is the pppoe kernel > implementation mature enough, or maybe i should try > the userland tool? You could try a snapshot instead of 3.7 but first fix your configuration. Even in 3.7 it is certainly much more usable than you describe. Can
