[plug] NT and Linux coexisting (Eisa)

[Garth Atkinson]

Chris

Eisa most likely arent allocating your local ip in a way that linux
understands. I had this problem with another ISP (who shall remain
nameless). What this means is that you can specify any ip to use as a
local ip. Unfortunately if you choose an ip that is in use, or one that
is not of the correct subnet then tcp/ip traffic wont route properly. At
the moment linux will be allocating the same ip that you use for eth0 or
similar. Use NT to connect to Eisa, note the PPP local ip allocated to
you, boot back to linux and tell pppd to use that same IP as the local
IP, and see how you go (This is not a solution, only a diagnostic
effort).

I think this is a security hole. In theory you could allocate for
yourself a trusted IP (one that Eisa have assumed to be trusted), and
then make use of that trust to do bad things. After our testing, if this
is the case then you should notify Eisa.

Garth

Chris Maidorn wrote:
> 
> 
> Another question is for people who use eisa (not great service, but I will
> not complain about 5 free hours a month and 1$ per hour from then onwards)
> as their ISP.  Since (recently) installing linux I have been unable to use
> eisa to connect to the internet using Linux. I have had no probs using iinet
> and onenet, and I have had no probs using eisa with NT.  (P.S. I have set up
> iinet and onenet using kppp). Any help would be appreciated.
>