Re: your mail AKA @home, NICs and windows
Hmmmmm...
They may be using MAC in Canada. Call Tech to inform that your NIC broke
and you installed a new NIC. Heck, what do they know. Tell them to update
database to activate your connection.
(Use Windows machine behind your Linux machine using ipmasq! Nothing to
lose. Their contract prohibit extension of connection beyond your premis
only. IPMASQ is LEGAL according to the contract.)
BTW, I use @home in California. They may be different from Canada but...
First I did not use @home provided NIC since my PC had Tulip NIC given
by my past ADSL connection. It is working. If you ask @HOME tech to
install first PC, you will be assigned as DHCP client though you are
connected at fixed IP here. Official @HOME policy here is "first PC
connection by DHCP" and "additional ones by FIXED IP".
Best place to look at is your WORK ORDER. CIP is your IP, DGA is gateway IP,
HST is host name, SUB is your subnetwork, etc. If you want to
connect to the network by DHCP, I heard PUMP configuration with proper host
name is needed. If you set up with Fixed IP like me, plug ipchain to shut
up loging for stupid incoming DHCP packet.
As far as I remember, installation tech did not check MAC nor serial number
of NIC he gave me. (Kept in my junk box safely) He was handling ISA and
PCI NIC and did not even bother to record type either.
I have good luck of using Linksys PCI or Kingston PCI (with Tulip driver).
Good luck configuring Linux for ipmasq. @HOME here scans NNTP port for
detecting customer running server. Be sure to plug these connection for
preventing trouble. I also get at least few suspicious trials of connections
to the ports (ftp, http, sunrpc, linuxconf, etc.) from script-kiddies.
FYI: My configuration example for ipmasq is on my web page.
http://www.aokiconsulting.com
Osamu Aoki
On Sat, Sep 23, 2000 at 08:28:18PM -0400, Richard Morin wrote:
> I believe that our cable modems will only work with the nic that @home gave
> you, hardcoded to the MAC as I recall.... of course I could be wrong..
> Rich
> ----- Original Message -----
> From: <ben.konrath@utoronto.ca>
> To: <debian-user@lists.debian.org>
> Sent: Tuesday, September 12, 2000 9:38 AM
> Subject: Re: your mail AKA @home, NICs and windows
>
>
> > Quoting Krzys Majewski <majewski@cs.ubc.ca>:
> >
> > > Uh ok this is a braindead reply but did you try
> > turning off
> > > the modem for a few minutes. I had a hard time
> > getting my new
> > > machine to work with cable, it suddenly worked on the
> > third
> > > network card (a 3c905b). -chris
> > >
> >
> > yep ... thats what i meant by power cycling the modem,
> >
> > b
> >
> >
> >
> > > On Tue, 12 Sep 2000 ben.konrath@utoronto.ca wrote:
> > >
> > > > hey
> > > >
> > > > i have been trying to get 2.2 (i386) working with
> > > > rogers @home cable modem service. the problem that i
> > > > keep encountering is that i can only get on-line
> > when i
> > > > am using a NIC that has been used with the cable
> > modem
> > > > in windows. if the card is used elsewhere or the
> > cable
> > > > modem is used with another card then i get the
> > > > following results:
> > > >
> > > > -eth0 configured correctly with all the static info
> > > > i
> > > > put in correct (ip, gateway, netmask etc.) and > >
> > > > correct driver
> > > > -when i try to ping an ip (my gateway or any other
> > > > active ip) i can see the send and receive lights on
> > > > the cable modem active, but i get 100% packet lose
> > > >
> > > > my assumption under this situation is that the ping
> > > > gets out and back in to the modem (hense the send
> > > > AND receive lights) but doesn't actually make it to
> > > > my machine.
> > > >
> > > > i have tried this set up with 3 separate computers
> > > > and 5 different NICs (SMC, dlink, 3c900b, 2
> > > > sohoware) but all have the same results.
> > > >
> > > > i have tried to "power cycle" the modem but that did
> > > > not work as well.
> > >
> > >
> > >
> >
> >
> > --
> > Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org <
> /dev/null
> >
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
>
>
Reply to: