Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Make sure that it is using the proper media... You could have a frotzed card or a bad network cable.... At this point it isn't a Linux configuration issue. Good Luck, -derek "Peter R. Breton" <prbreton at fandago.read.tasc.com> writes: > > > This output seems to imply that the card is up and running fine. It > > is certainly configured, and it is transmitting AND receiving > > packets.... So, what is failing, now? From your linux box you should > > be able to ping other machines on 192.168.1.0, assuming they are setup > > properly. > > I can't ping anything in the 192.168.1.0 network. The other machines (a > Mac and an NT box) can ping each other, though. When I had the cards > reversed (eth1 going to MediaOne, eth0 to internal network), the > internal network worked fine but I got no MediaOne connection. Hence my > guess is that, despite the boot messages, the card is somehow whacked. > Someone on one of the express.* groups (the MediaOne newsgroups) > mentioned changing IRQs and having his card mysteriously start to work. > Right now that seems as likely an approach as any..... > > Peter -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord at MIT.EDU PGP key available *** Subcription/unsubscription/info requests: send e-mail with subject of "subscribe", "unsubscribe", or "info" to discuss-request at blu.org
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |