LinuxQuestions.org - Cannot access to web interface of wireless ethernet bridge Belkin F5D7330

- Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)

- - Cannot access to web interface of wireless ethernet bridge Belkin F5D7330 (https://www.linuxquestions.org/questions/linux-wireless-networking-41/cannot-access-to-web-interface-of-wireless-ethernet-bridge-belkin-f5d7330-522100/)

Cannot access to web interface of wireless ethernet bridge Belkin F5D7330

I'm a big newbie in configuring network interfaces. Here is what I did (I am using openSUSE 10.2 and NetworkManager)

-I plugged-in the wireless ethernet adapter
-I tried to access 192.168.2.225 (as written in the manual) with a browser (It said the connection was refused)

-I ran

Code:

ifconfig eth0 up

and ifconfig gives me the following output:

Code:

eth0      Link encap:Ethernet  HWaddr 00:11:43:68:4F:91

          inet addr:169.254.191.15  Bcast:169.254.255.255  Mask:255.255.0.0

          inet6 addr: fe80::211:43ff:fe68:4f91/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:2 errors:0 dropped:0 overruns:0 frame:0

          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:128 (128.0 b)  TX bytes:3098 (3.0 Kb)

          Interrupt:11



eth1      Link encap:Ethernet  HWaddr 00:0B:7D:10:91:14

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:10141 errors:0 dropped:0 overruns:0 frame:0

          TX packets:7273 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:12634119 (12.0 Mb)  TX bytes:807160 (788.2 Kb)

          Interrupt:7 Memory:faff6000-faff8000



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:70 errors:0 dropped:0 overruns:0 frame:0

          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:4824 (4.7 Kb)  TX bytes:4824 (4.7 Kb)

Knetworkmanager tells me it is connected to the Wired Interface. I still cannot enter 192
.168.2.225 (I have tried various other ip, but none worked).

-I have tried reseting my device several time: always the same results.
-I have googled the problem and searched the manual: no problem at all, everything seems to work out of the box even for linux users...
-I have even tried to access the web interface in a windows pc (not sure this test is reliable though: the pc is very buggy and uses a very restrictive firewall...), it didn't work. When I use the easy setup cd, it crashes when looking for the device...

I wonder if something could be broken in the device. So my questions are:
-How can I try to configure my eth0 interface so that I can access the device ?
-How to make sure that my ethernet interface is working and that the device has a problem I cannot fix from the PC ?

Thanks for your consideration. (Any kind of help would be very welcome)

Your router needs you to be able to connect to it at 192.168.2.225. However, your eth0 is on 169.254.191.15 and on a different "subnet" entirely, so they can't talk. Try this instead: "ifconfig eth0 192.168.2.100" and see if that works.

Could you give us the output from this please: "cat /etc/network/interfaces" From what I've seen so far, it looks like the interfaces file is misconfigured. If so, we should be able to get it set right so that you get an address from your wireless bridge.

Also, I couldn't download the manual, but if there's a switch on it, it needs to be switched to client mode.

Code:

ipconfig eth0 192.168.2.100

That solved my problem (I tried various address but none with 192.168.2.x)
Thank you very much, I will try helping you one day :)

Wait! Hold on! We're not finished. That was just a hack to get you working for a minute. It wasn't a fix. Give me the results of "cat /etc/network/interfaces" so we can get to the root of what's happening and I can give you a proper fix.

Code:

BOOTPROTO='dhcp'

BROADCAST=''

ETHTOOL_OPTIONS=''

IFPLUGD_PRIORITY='20'

IPADDR=''

MTU=''

NAME='Dell BCM4401 100Base-T'

NETMASK=''

NETWORK=''

REMOTE_IPADDR=''

STARTMODE='ifplugd'

UNIQUE='rBUF.iShmefsNM+5'

USERCONTROL='yes'

_nm_name='bus-pci-0000:02:00.0'

PREFIXLEN=''

I have changed some options in the meantime (use of ifup instead of networkmanager), so here is the output of ifconfig (with wireless (eth1) up and running. I suppose I will have to disable it ?)

Code:

eth0      Link encap:Ethernet  HWaddr 00:11:43:68:4F:91

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:4 errors:0 dropped:0 overruns:0 frame:0

          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:256 (256.0 b)  TX bytes:876 (876.0 b)

          Interrupt:11



eth1      Link encap:Ethernet  HWaddr 00:0B:7D:10:91:14

          inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::20b:7dff:fe10:9114/64 Scope:Link

          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:20501 errors:0 dropped:0 overruns:0 frame:0

          TX packets:18751 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:18774094 (17.9 Mb)  TX bytes:3064364 (2.9 Mb)

          Interrupt:7 Memory:faff6000-faff8000



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:511 errors:0 dropped:0 overruns:0 frame:0

          TX packets:511 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

For the moment
ifconfig eth1 down
and
ifconfig eth0 192.168.1.100
Solve my problem.

Oh, duh, Suse and not Debian. My mistake. The network configurations are completely different. What you really want is to setup eth0 for dhcp, but I can't help you with Suse. I guess you would be able to use the NetworkManager gui to disable eth1 and change eth0 from static to dhcp. I don't usually use the gui for this stuff so I don't even think to suggest someone else use it.

I don't like those GUI interfaces either. I guess I will just learn how to set it up by myself, there are enough tutorials on the internet. Thanks again for helping me.