Modify

Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#169 closed defect (invalid)

robocfg - deprecated ?

Reported by: edgrootjans@… Owned by: amain
Priority: minor Milestone: milestone:
Component: other Version: 2.0
Severity: severity 1 Keywords: robocfg
Cc:

Description

I have tryed to make 3 networks:
lan, wlan and wan.
So i did a new link in /etc/network from interfaces.seperate-wlan-lan
For this i did activated in /etc/default robocfg, by placing a 1

I could not get in my ASUS router again.
When I did connect by RS232, I saw:

root@debwrt:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:15:f2:77:d0:c1  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3786 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1132 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:438269 (427.9 KiB)  TX bytes:152003 (148.4 KiB)

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:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4685 (4.5 KiB)  TX bytes:4685 (4.5 KiB)

wl0       Link encap:Ethernet  HWaddr 00:15:f2:77:d0:c1  
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING 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 bytesroot@debwrt:~# ifconfig
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@debwrt:

Because of this, I added the following after eth0_lan and eth0_wan

auto eth0
iface eth0 inet static
   address 192.168.0.251
   netmask 255.255.255.0
auto eth0:1
iface eth0:1 inet static
    address 192.168.1.1
    netmask 255.255.255.0

Because of this i can now login with ssh

I looked in /etc/inet.d/robocfg and saw the following:

# Old file: switch now managed from /etc/network/interfaces
exit 0

I looked in /etc/network/interfaces, but I did not find a file who creates the
eth0_lan and eth0_wan interfaces.
I did see a file interfaces.broadcom, but what it does is not totally clear to me.

Question if robocfg is not used anymore
What or how do i have to activate my interfaces.

PS.
Enabling robocfg by outcommanding exit 0 and i got the expected configuration


Attachments (0)

Change History (6)

comment:1 Changed 9 years ago by edgrootjans@…

When I restart with robocfg enabled.
It is not enymore posible to login using ssh
I get no route to host

Loging in by usb gives my:

ifconfig
eth0 192.168.0.251
eth0:1 192.168.1.1
lo 127.0.0.1
wl0 192.168.2.1

SO why can i not connect to these interfaces ??

When i do a restart of the network - my interfaces become available:

cd /etc/init.d
./networking stop
./ifupdown stop
./robocfg stop
./robocfg start
./ifupdown start
./networking start

I can login on the lan-part with 192.168.1.1
and got 2 more interfaces:

eth0_lan

eth0_wan

comment:2 Changed 9 years ago by edgrootjans@…

I have found a solution.

Robocfg is started as last in rcS.
The Start Sequence is no longer made by the S or K value,
but since debian 6 the LSB sequence is used.

Robocfg needs to start for ifupdown.
So i changed the following in ifupdown:

 # Required-Start:   ifupdown-clean
 # Required-Stop:   $local_fs

To

# Required-Start:    ifupdown-clean robocfg
# Required-Stop:    $local_fs Robocfg

After that I did an insserv ifupdown,
but get an error: insserv: warning script 'rcS.debian' missing lsb tags and overrides
After that I did

mv /etc/init.d/rcS.debian /root/etc/init.d
insserv ifupdown
reboot

Conclussion:

Robocfg is started in the correct sequence, all interfaces are after boot directly available

I deleted my backup interfaces eth0 and eth0:1
I show you:

root@debwrt:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:15:f2:77:d0:c1  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:101 errors:0 dropped:0 overruns:0 frame:0
          TX packets:533 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:14447 (14.1 KiB)  TX bytes:46268 (45.1 KiB)
          Interrupt:4 

eth0_lan  Link encap:Ethernet  HWaddr 00:15:f2:77:d0:c1  
          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:95 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:11278 (11.0 KiB)  TX bytes:8482 (8.2 KiB)

eth0_wan  Link encap:Ethernet  HWaddr 00:15:f2:77:d0:c1  
          inet addr:192.168.0.251  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:257 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:10794 (10.5 KiB)

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:95 errors:0 dropped:0 overruns:0 frame:0
          TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:9025 (8.8 KiB)  TX bytes:9025 (8.8 KiB)

wl0       Link encap:Ethernet  HWaddr 00:15:f2:77:d0:c1  
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING 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:5 

root@debwrt:~# 

So (I use rev314)

1) Can /etc/init.d/rcS.debian be deleted in next version
and
2) Robocfg be enabled or made clear what to use for it.
Thanks

Erik

comment:3 Changed 9 years ago by amain

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

rcS.debian should be removed indeed, if I'm correct, that should have been taken care of in trunk. robocfg on 2.0 was added just as an example to get things to work. <2.0 was specifically for the asus wl500 range/comapitible >=2.0 is for way more devices. Hence removal /disabling of all custom networking related scripts.

robocfg is not depricated. There should be quite some info now in the wiki/forum etc to get networking going. Feel free to update the hardware wiki pages which are fully user editable.

see pacakge debwrt-net in trunk. it will bring back 1.0 level support for Asus based routers.

comment:4 Changed 9 years ago by amain

note: having a backlog of DebWrt mail...you other mails are noticed :-)

comment:6 Changed 7 years ago by services

Enjoyed every bit of your post.Really thank you! Great.

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.