Jayarajan,
I am sorry for not responding before, but this situation had me
thinking about the situation. After the output of ifconfig -a,
I see the following:
eth0 Link encap:Ethernet HWaddr 00:11:43:fe:45:ee
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:11
eth1 Link encap:Ethernet HWaddr 00:13:ce:01:87:2c
inet addr:192.168.0.199 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::213:ceff:fe01:872c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1232 errors:2 dropped:2 overruns:0 frame:0
TX packets:164 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:129490 (129.4 KB) TX bytes:13869 (13.8 KB)
Interrupt:5 Base address:0x6000 Memory:fcfee000-fcfeefff
It appears that one eth1 already has an ip and it is working. What
happens if you unplug your wireless pcmcia modem, does it still give
you the same output, ifconfig -a?
Other than that, I don't know how to help here, since I don't know
enough about these pcmcia modems.
Regards,
Antonio
On 6/27/09, Jayarajan P M <jayarajan@xxxxxxxxxxxxxxx> wrote:
>
> jai@jai-laptop:~$ sudo ifconfig -a
> eth0 Link encap:Ethernet HWaddr 00:11:43:fe:45:ee
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> Interrupt:11
>
> eth1 Link encap:Ethernet HWaddr 00:13:ce:01:87:2c
> inet addr:192.168.0.199 Bcast:192.168.0.255
> Mask:255.255.255.0
> inet6 addr: fe80::213:ceff:fe01:872c/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1232 errors:2 dropped:2 overruns:0 frame:0
> TX packets:164 errors:0 dropped:5 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:129490 (129.4 KB) TX bytes:13869 (13.8 KB)
> Interrupt:5 Base address:0x6000 Memory:fcfee000-fcfeefff
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)
>
> pan0 Link encap:Ethernet HWaddr 46:d5:1b:df:ea:d9
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> vboxnet0 Link encap:Ethernet HWaddr 00:76:62:6e:65:74
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
>
> On Fri, 2009-06-26 at 22:17 -0500, Antonio Olivares wrote:
>
> Yes I referred to the inbuilt one. scanModem did not return anything
> in regards to the pcmcia one?, if it did it flew by me and I did not
> catch it.
>
> if it is a wireless modem, what do you get when you execute following
> commands
> # ifconfig -a or
> $ sudo ifconfig -a
>
> Regards,
> Antonio
>
