[debian-non-standard] PPPoE on Asus WL-500gP with debian on board [solved problem]
Martin Steigerwald
Martin at lichtvoll.de
Fri Feb 22 22:22:35 CET 2008
Am Freitag 22 Februar 2008 schrieb Martin Steigerwald:
> Am Freitag 22 Februar 2008 schrieb Martin Steigerwald:
> > Am Montag 18 Februar 2008 schrieb Przemyslaw Baran:
> > > For Tomasz Chmielewski
> > I leave it now. I think I could go trying around for ages without
> > finding the obvious.
> >
> > Ciao,
One more attempt after reading the thread
[debian-non-standard] PPPoE on Asus WL-500gP with debian on board [solved
problem]
And dammit, it works!
I faced two obstacles:
1) One network cable did not work with the ASUS tough it reported a link
and worked with my Amiga ;)
2) When I have two IP addresses of the same network 10.0.0.0/24 I always
can ping both of them when I can ping one of them.
I now have:
gayatri:~# ls -l /etc/rcS.d/S38switch-config
lrwxrwxrwx 1 root root 23 2000-01-01
01:06 /etc/rcS.d/S38switch-config -> ../init.d/switch-config
gayatri:~# cat /etc/init.d/switch-config
#!/bin/sh
# eth0 muss zuerst initialisiert werden
ifconfig eth0 0.0.0.0
# Erstmal Switch aus
/usr/local/bin/robocfg switch disable
# VLAN-Einstellungen zuruecksetzen
/usr/local/bin/robocfg vlans enable reset
# WAN-Port auf VLAN 0, das eth0 (!) heisst
/usr/local/bin/robocfg vlan 0 ports "0 5u"
# LAN-Ports auf VLAN 1, das eth0.1 heisst
/usr/local/bin/robocfg vlan 1 ports "1 2 3 4 5t"
# Switch an!
/usr/local/bin/robocfg switch enable
as well as:
gayatri:/etc# cat /etc/network/interfaces
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback
# WAN-Port
auto eth0
iface eth0 inet manual
# hwaddress ether 00:1E:8C:2E:0F:51
# LAN-Ports
auto eth0.1
iface eth0.1 inet static
address 10.0.0.8
netmask 255.255.255.0
broadcast 10.0.0.255
gateway 10.0.0.9
hwaddress ether 00:1E:8C:2E:0F:52
And for testing I gave eth0 and my notebook an IP address of another
network
gayatri:~# ifconfig eth0 192.168.1.8 netmask 255.255.255.0 broadcast
192.168.1.255
shambala> ip addr add 192.168.1.21/24 dev eth0
And well not I can have a ping at 192.168.1.8 and one at 10.0.0.8 and when
I plug around the working cable the one ping stops and the other one
continues...
Oh well...
I got it.
BZW that hwaddress thing in /e/n/interfaces works:
gayatri:~# ip addr
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,PROMISC,UP,10000> mtu 1500 qdisc pfifo_fast
qlen 1000
link/ether 00:1e:8c:2e:0f:51 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.8/24 brd 192.168.1.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 40:10:18:00:00:2d brd ff:ff:ff:ff:ff:ff
4: eth0.1 at eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:1e:8c:2e:0f:52 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.8/24 brd 10.0.0.255 scope global eth0.1
eth0.1 has a different MAC..
Still robocfg does only show NULL macs
gayatri:~# robocfg show
Switch: enabled
Port 0(W): DOWN enabled stp: none vlan: 0 mac: 00:00:00:00:00:00
Port 1(4): 100FD enabled stp: none vlan: 1 mac: 00:00:00:00:00:00
Port 2(3): DOWN enabled stp: none vlan: 1 mac: 00:00:00:00:00:00
Port 3(2): DOWN enabled stp: none vlan: 1 mac: 00:00:00:00:00:00
Port 4(1): DOWN enabled stp: none vlan: 1 mac: 00:00:00:00:00:00
Port 5(C): 100FD enabled stp: none vlan: 0 mac: 00:00:00:00:00:00
VLANs: BCM5325/535x enabled mac_check mac_hash
vlan0: 0 5u
vlan1: 1 2 3 4 5t
Should I be worried about that?
So bzr'ing this configuration ;-)
Now my ASUS is ready to be setup as a ADSL router
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.wpkg.org/pipermail/debian-non-standard/attachments/20080222/44bca38a/attachment-0002.sig>
More information about the debian-non-standard
mailing list