[EMAIL PROTECTED] writes:
>It would probably help if you posted the results of
>
>ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 00:00:39:54:24:E7  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:1180 (1.1 Kb)
          Interrupt:11 Base address:0xdf40 Memory:fceff000-fceff038
>
>ifconfig eth1

eth1      Link encap:Ethernet  HWaddr 00:02:2D:43:3E:B0  
          inet addr:172.16.1.158  Bcast:172.16.255.255  Mask:255.255.0.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:585596 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1543 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:594883047 (567.3 Mb)  TX bytes:208433 (203.5 Kb)
          Interrupt:11 Base address:0x100
>
>route

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
172.16.0.0      *               255.255.0.0     U     0      0        0
eth1
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         172.16.0.1      0.0.0.0         UG    0      0        0
eth1
>
>dmesg|grep eth
e100: eth0: Intel(R) PRO/100 VE Network Connection
wvlan_cs: Registered netdevice eth1
wvlan_cs: MAC address on eth1 is 00 02 2d 43 3e b0 
wvlan_cs: MAC address on eth1 is 00 02 2d 43 3e b0 
wvlan_cs: MAC address on eth1 is 00 02 2d 43 3e b0 
>
>
>On Wed, 12 Feb 2003 12:09:16 +1300
>Hamish McBrearty <[EMAIL PROTECTED]> wrote:
>
>> Hi there
>> 
>> After much tweaking, I've finally gotten my laptop successfully running
>> Mandrake 9.0. However, I've got a few gremlins left to kill. Mainly to
>do
>> with networking. 
>> 
>> During set up it correctly detected I have 2 network cards, an Intel Pro
>> 100/VE and a Toshiba Mini PCI Wifi card. The Intel card worked fine,
>and I
>> set the wireless card not to start on boot so I could have a tweak once
>I
>> got to school and within range of our wireless network. To my complete
>> shock, eth1 which was the onboard LAN card at home, picked up a DHCP
>> address at school even tho it wasn't plugged in, and happily functions
>on
>> our wireless network here. Meanwhile eth0 is permanently down.
>> 
>> Now here comes something even stranger. Our DHCP server gives out IPs
>> starting from 172.16.1.30 with a subnet mask of 255.255.0.0 making it a
>> class B subnet. However, from my laptop I am unable to access anything
>> that doesn't begin with 172.16.1 almost like I'm on a class C subnet.
>Can
>> anyone help me out here? I'm horribly confused, stuff that shouldn't
>work
>> does, and stuff that should work doesn't!
>> 
>> -------------------------------------------------
>> Hamish McBrearty     MCSE  MCSA
>> Network Engineer
>> Rangi Ruru Girls' School
>> 59 Hewitts Road
>> Christchurch
>> NEW ZEALAND
>> Ph 03 355-6099
>> Fax 03 355-6027
>> CELL 021 999770
>> E-Mail: [EMAIL PROTECTED]
>> --------------------------------------------------
>> 
>> 
>
>--
>"All that was needed was to parse the cat root slash dev etcetera file
>for eth0 and pugle the forward identity-locking rehooliginator and
>symlink it to the libgc perl humongisooler module after a kernel
>decompile and basic repatch update." - theregister.co.uk
>



-------------------------------------------------
Hamish McBrearty     MCSE  MCSA
Network Engineer
Rangi Ruru Girls' School
59 Hewitts Road
Christchurch
NEW ZEALAND
Ph 03 355-6099
Fax 03 355-6027
CELL 021 999770
E-Mail: [EMAIL PROTECTED]
--------------------------------------------------


Reply via email to