Modify

Opened 8 years ago

Closed 8 years ago

#126 closed defect (worksforme)

Support request rs pro: network problem

Reported by: i_berbeu@… Owned by: amain
Priority: minor Milestone: milestone:
Component: buildsystem Version: 2.0
Severity: Keywords:
Cc:

Description

Hello,
I have a RouterStation pro. I've downloaded the file "debwrt-firmware-ar71xx-generic-ubnt-rspro-squashfs-factory.bin" from the web "http://www.debwrt.net/download/releases/2.0/". Now I flash the image following the instructions for flashing the rspro, but after it is done I cannot reach with ping the ip 192.168.1.1, neither another ip in that class D range. I now that my flashing method works because I've already flashed another images from the openwrt repositories.
I don't know what's the problem.

Attachments (0)

Change History (10)

comment:1 follow-up: Changed 8 years ago by amain

  • Priority changed from major to minor

Hi. What does the serial console of the RS PRO say?

comment:2 in reply to: ↑ 1 ; follow-up: Changed 8 years ago by anonymous

Using the serial console, everything seems to be well falshed but after rebooting, I get the following Kernel-panic message:

VFS: Cannot open root device "sda1" or unknown-block(8,1)
Please append a correct "root=" boot option; here are the available partitions:
1f00 192 mtdblock0 (driver?)
1f01 1088 mtdblock1 (driver?)
1f02 15040 mtdblock2 (driver?)
1f03 14976 mtdblock3 (driver?)
1f04 60 mtdblock4 (driver?)
1f05 4 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)

comment:3 in reply to: ↑ 2 Changed 8 years ago by anonymous

Ok, my fault, sorry.
I've forgotten to plug the sdcard in. But still, I have the problem that I cannot reach the device with ping. This is the output of ifoncifg. I've tried connecting with all the physical ports

root@debwrt:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:6d:c4:24:56

inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:161 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60 (60.0 B) TX bytes:13676 (13.3 KiB)
Interrupt:4

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:117 errors:0 dropped:0 overruns:0 frame:0
TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9768 (9.5 KiB) TX bytes:9768 (9.5 KiB)

comment:4 Changed 8 years ago by amain

Try using eth1...maybe one of your ports is dead? Using cross-cable or connect to a switch. Is link up???

After having a ping you may start playing with swconfig: http://www.debwrt.net/download/testing/packages/

comment:5 follow-up: Changed 8 years ago by amain

  • Summary changed from Firmware doesn't work to Support request rs pro: network problem

comment:6 in reply to: ↑ 5 Changed 8 years ago by anonymous

Ok, I get it. The problem was that by default you have the eth0 and I need (as you said) the eth1. So I changed that and it works.
You're right, now i have to start working with swconfig, because I have seen that the "routing" is not implemented, do I need to install everything?. Could you tell me how to start and what do I need to do?
thanks!

comment:7 follow-up: Changed 8 years ago by amain

Well....see ticket #38 for info on how to use swconfig.

comment:8 in reply to: ↑ 7 Changed 8 years ago by anonymous

Ok, thank you very much!
Now I have it working, but I cannot reach the internet from my LAN, I have to check that.
Is there going to be an init script for doing this thing automatically? Why these packages are not installed by default in the debian image if we are going to need them? Do you know a good way to provide UMTS access?

comment:9 Changed 8 years ago by stappers

I think this ticket is now covered in FrequentlyAskedQuestions

comment:10 Changed 8 years ago by amain

  • Resolution set to worksforme
  • Status changed from new to closed

DebWrt currently provides a firmware with a kernel and a rootfs with a standard Debian install. From that point you must consider your debwrt running device as a normal Debian server which needs to be configured accordingly. We do supply some small suggestions here and there, but it is to much work for now to maintain.

For you: you need to use iptables with NAT or MASQUARADING.

Closing ticket.

Add Comment

Modify Ticket

Action
as closed The owner will remain amain.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.