OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Gregor Jeromen (gregor.jeromenlogina.si)
Date: Tue Jun 05 2001 - 06:06:15 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On Mon, 04 Jun 2001 22:58:25 +0100, Brian Somers wrote:

    >You may need to use the -n and/or -i switches to pppoe... something
    >like:
    > set device "!/usr/sbin/pppoe -n myisp -i ed0"

    >If this doesn't help, try monitoring the traffic:
    > tcpdump -i ed0 -t not ip

    >(replace ed0 with whatever your interface is and myisp with whatever
    >your ISP says the service tag should be).

    O.K. Extracted service name information from telco and inspected with
    tcpdump:

    09:26:32.996335 PPPoE-Discovery
            code Initiation, version 1, type 1, id 0x0000, length 20
            tag Host-Uniq, length 4 ną \226
            tag Service-Name, length 8 xxxxxxxx

    So, the (only) packet is on the way and there is no answer.

    Is there anything else I can do?

    I've discussed the ADSL setup with telco and it is as follows:
    Ethernet frame from my machine is inserted into ATM cells which travel
    over DSL bitstream to DSLAM and then on via ATM to some machine at ISP
    (they don't tell what it is) which unpacks ATM, maintains PPP
    connections and routes IP. Telco equipment is all Siemens.
    They do it by RFCs 2383 (ST2+ over ATM), 1483 (Multiprotocol
    Encapsulation over ATM Adaptation Layer 5) and 2364 (PPP Over AAL5).
    Seems to me that they are not concerned with higher layer than
    ethernet/PPP over ATM.

    If you see here any potential trouble, please let me know.

    Best regards,
                  Gregec
     ________________________________________________________________________
    | Logina Lagersoft d.o.o., Slovenija | We can make your warehouse dance! |
    | tel: +386-1-5838017, fax: -5154015 | Logistics & Automation & Comm's |