Menu
▾
▴
linux-atm-general — General discussion of ATM networking under linux
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(25) |
Oct
(110) |
Nov
(138) |
Dec
(146) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(221) |
Feb
(154) |
Mar
(113) |
Apr
(84) |
May
(79) |
Jun
(114) |
Jul
(148) |
Aug
(197) |
Sep
(76) |
Oct
(116) |
Nov
(88) |
Dec
(58) |
| 2002 |
Jan
(69) |
Feb
(77) |
Mar
(41) |
Apr
(52) |
May
(80) |
Jun
(129) |
Jul
(54) |
Aug
(38) |
Sep
(50) |
Oct
(69) |
Nov
(39) |
Dec
(59) |
| 2003 |
Jan
(42) |
Feb
(67) |
Mar
(82) |
Apr
(87) |
May
(38) |
Jun
(74) |
Jul
(56) |
Aug
(99) |
Sep
(201) |
Oct
(73) |
Nov
(15) |
Dec
(55) |
| 2004 |
Jan
(67) |
Feb
(54) |
Mar
(73) |
Apr
(67) |
May
(13) |
Jun
(33) |
Jul
(35) |
Aug
(18) |
Sep
(11) |
Oct
(18) |
Nov
(8) |
Dec
(21) |
| 2005 |
Jan
(66) |
Feb
(20) |
Mar
(26) |
Apr
(56) |
May
(39) |
Jun
(16) |
Jul
(21) |
Aug
(32) |
Sep
(33) |
Oct
(55) |
Nov
(126) |
Dec
(8) |
| 2006 |
Jan
(7) |
Feb
(11) |
Mar
|
Apr
(15) |
May
(17) |
Jun
(4) |
Jul
(7) |
Aug
(12) |
Sep
(18) |
Oct
(30) |
Nov
(12) |
Dec
(12) |
| 2007 |
Jan
(6) |
Feb
(20) |
Mar
(16) |
Apr
(20) |
May
(14) |
Jun
(12) |
Jul
(5) |
Aug
(20) |
Sep
(17) |
Oct
(2) |
Nov
|
Dec
(10) |
| 2008 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
(17) |
Jul
(32) |
Aug
(8) |
Sep
(3) |
Oct
(4) |
Nov
(4) |
Dec
(6) |
| 2009 |
Jan
|
Feb
(12) |
Mar
(10) |
Apr
|
May
(1) |
Jun
|
Jul
(8) |
Aug
(11) |
Sep
(6) |
Oct
(6) |
Nov
(5) |
Dec
|
| 2010 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(2) |
May
(7) |
Jun
(14) |
Jul
(60) |
Aug
(39) |
Sep
(41) |
Oct
(4) |
Nov
|
Dec
(29) |
| 2011 |
Jan
(15) |
Feb
(3) |
Mar
(37) |
Apr
(5) |
May
(3) |
Jun
|
Jul
(15) |
Aug
(16) |
Sep
|
Oct
(7) |
Nov
(10) |
Dec
(2) |
| 2012 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(9) |
Aug
(10) |
Sep
|
Oct
|
Nov
(2) |
Dec
(3) |
| 2015 |
Jan
(6) |
Feb
|
Mar
(4) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
(5) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Philip P. <phi...@re...> - 2011-03-19 00:10:54
|
I'm seeing the following. I have a Geos box running Openwrt from SVN (about 2 weeks old from trunk), and using the Geos platform target. I've configured RFC-2684 bridged mode for my Frontier Communications ADSL connection. Openwrt shows me that: br2684ctl -c 0 -e 0 -p 1 -a 0.0.35 -s 2040 is running as we'd expect. However, I rebuilt the solos-pci driver to call: list_vccs(0); whenever it enters find_vcc(), which was always returning NULL will called with '35' as the argument. I compiled the module with: #define DEBUG 1 #define VERBOSE_DEBUG 1 It should be printing the entire table out whenever a packet is received... But it doesn't... or it does but the table is empty. Mar 18 16:25:07 OpenWrt kern.info kernel: solos 0000:00:0c.0: Received: device 0 Mar 18 16:25:07 OpenWrt kern.info kernel: solos 0000:00:0c.0: size: 43 VPI: 0 VCI: 35 Mar 18 16:25:07 OpenWrt kern.debug kernel: 00: 31 0A 31 36 33 32 30 30 Mar 18 16:25:07 OpenWrt kern.debug kernel: 08: 30 0A 34 34 37 38 30 30 Mar 18 16:25:07 OpenWrt kern.debug kernel: 10: 0A 53 68 6F 77 74 69 6D Mar 18 16:25:07 OpenWrt kern.debug kernel: 18: 65 0A 36 2E 37 30 20 64 Mar 18 16:25:07 OpenWrt kern.debug kernel: 20: 42 0A 36 39 2E 30 20 64 Mar 18 16:25:07 OpenWrt kern.debug kernel: 28: 42 20 0A Mar 18 16:25:07 OpenWrt kern.info kernel: solos 0000:00:0c.0: Port 0: Showtime @1632/447 kb/s, SNR 6.70 dB, Attn 69.0 dB Mar 18 16:25:08 OpenWrt kern.info kernel: solos 0000:00:0c.0: Transmitted: port 0 Mar 18 16:25:08 OpenWrt kern.debug kernel: 00: 9D 01 00 00 23 00 00 00 Mar 18 16:25:08 OpenWrt kern.debug kernel: 08: AA AA 03 00 80 C2 00 07 Mar 18 16:25:08 OpenWrt kern.debug kernel: 10: 00 00 FF FF FF FF FF FF Mar 18 16:25:08 OpenWrt kern.debug kernel: 18: 00 0A FA 22 00 84 08 00 Mar 18 16:25:08 OpenWrt kern.debug kernel: 20: 45 00 01 85 00 00 00 00 Mar 18 16:25:08 OpenWrt kern.debug kernel: 28: 40 11 79 69 00 00 00 00 Mar 18 16:25:08 OpenWrt kern.debug kernel: 30: FF FF FF FF 00 44 00 43 Mar 18 16:25:08 OpenWrt kern.debug kernel: 38: 01 71 14 57 01 01 06 00 Mar 18 16:25:08 OpenWrt kern.debug kernel: 40: C1 48 78 3B 00 00 00 00 Mar 18 16:25:08 OpenWrt kern.debug kernel: 48: 00 00 00 00 00 00 00 00 Mar 18 16:25:10 OpenWrt kern.info kernel: solos 0000:00:0c.0: Received: device 0 Mar 18 16:25:10 OpenWrt kern.info kernel: solos 0000:00:0c.0: size: 145 VPI: 0 VCI: 35 Mar 18 16:25:10 OpenWrt kern.debug kernel: 00: AA AA 03 00 80 C2 00 07 Mar 18 16:25:10 OpenWrt kern.debug kernel: 08: 00 00 0C D5 02 58 DC B3 Mar 18 16:25:10 OpenWrt kern.debug kernel: 10: 00 90 1A 41 45 FE 08 00 Mar 18 16:25:10 OpenWrt kern.debug kernel: 18: 45 00 00 79 7D 84 40 00 Mar 18 16:25:10 OpenWrt kern.debug kernel: 20: 38 06 7A 59 C6 89 CA 12 Mar 18 16:25:10 OpenWrt kern.debug kernel: 28: 47 6F 72 96 03 E1 E3 CD Mar 18 16:25:10 OpenWrt kern.debug kernel: 30: 28 7D 87 1A 59 6E EE 7B Mar 18 16:25:10 OpenWrt kern.debug kernel: 38: 80 18 82 18 19 95 00 00 Mar 18 16:25:10 OpenWrt kern.debug kernel: 40: 01 01 08 0A 29 5A 4D 3F Mar 18 16:25:10 OpenWrt kern.debug kernel: 48: 21 87 4F 95 17 03 01 00 Mar 18 16:25:10 OpenWrt kern.debug kernel: 50: 40 0E 30 D7 94 BD D6 41 Mar 18 16:25:10 OpenWrt kern.debug kernel: 58: D8 1D 1D 6C FF 97 CC 3A Mar 18 16:25:10 OpenWrt kern.debug kernel: 60: 01 67 D4 DB 7E 6C D5 A7 Mar 18 16:25:10 OpenWrt kern.debug kernel: 68: 80 BA 37 F5 F0 AB 4C FC Mar 18 16:25:10 OpenWrt kern.debug kernel: 70: 37 6D 62 E9 70 A4 5C 6C Mar 18 16:25:10 OpenWrt kern.debug kernel: 78: B4 80 4A ED 19 81 06 DE Mar 18 16:25:10 OpenWrt kern.debug kernel: 80: 74 45 18 2A FC 86 58 C3 Mar 18 16:25:10 OpenWrt kern.debug kernel: 88: 63 F1 68 C7 E0 EB 9D B3 Mar 18 16:25:10 OpenWrt kern.debug kernel: 90: 3F Mar 18 16:25:10 OpenWrt kern.info kernel: solos 0000:00:0c.0: find_vcc: ddd39e00, 0.35 Mar 18 16:25:10 OpenWrt kern.info kernel: solos 0000:00:0c.0: head=e04dd42c, first= (null), mask=3 Mar 18 16:25:10 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 Mar 18 16:25:11 OpenWrt kern.info kernel: solos 0000:00:0c.0: Transmitted: port 0 Mar 18 16:25:11 OpenWrt kern.debug kernel: 00: 9D 01 00 00 23 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 08: AA AA 03 00 80 C2 00 07 Mar 18 16:25:11 OpenWrt kern.debug kernel: 10: 00 00 FF FF FF FF FF FF Mar 18 16:25:11 OpenWrt kern.debug kernel: 18: 00 0A FA 22 00 84 08 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 20: 45 00 01 85 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 28: 40 11 79 69 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 30: FF FF FF FF 00 44 00 43 Mar 18 16:25:11 OpenWrt kern.debug kernel: 38: 01 71 14 57 01 01 06 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 40: C1 48 78 3B 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 48: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 50: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 58: 00 0A FA 22 00 84 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 60: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 68: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 70: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 78: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 80: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 88: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 90: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 98: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: A0: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: A8: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: B0: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: B8: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: C0: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: C8: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: D0: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: D8: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: E0: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: E8: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: F0: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: F8: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 100: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 108: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 110: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 118: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 120: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 128: 63 82 53 63 35 01 01 3D Mar 18 16:25:11 OpenWrt kern.debug kernel: 130: 07 01 00 0A FA 22 00 84 Mar 18 16:25:11 OpenWrt kern.debug kernel: 138: 3C 0C 75 64 68 63 70 20 Mar 18 16:25:11 OpenWrt kern.debug kernel: 140: 31 2E 31 37 2E 33 39 02 Mar 18 16:25:11 OpenWrt kern.debug kernel: 148: 02 40 37 08 01 03 06 0C Mar 18 16:25:11 OpenWrt kern.debug kernel: 150: 0F 11 1C 2A FF 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 158: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 160: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 168: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 170: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 178: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 180: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 188: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 190: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 198: 00 00 00 00 00 00 00 00 Mar 18 16:25:11 OpenWrt kern.debug kernel: 1A0: 00 00 00 00 00 Mar 18 16:25:12 OpenWrt kern.info kernel: solos 0000:00:0c.0: Received: device 0 Mar 18 16:25:12 OpenWrt kern.info kernel: solos 0000:00:0c.0: size: 136 VPI: 0 VCI: 35 Mar 18 16:25:12 OpenWrt kern.debug kernel: 00: AA AA 03 00 80 C2 00 07 Mar 18 16:25:12 OpenWrt kern.debug kernel: 08: 00 00 0C D5 02 58 DC B3 Mar 18 16:25:12 OpenWrt kern.debug kernel: 10: 00 90 1A 41 45 FE 08 00 Mar 18 16:25:12 OpenWrt kern.debug kernel: 18: 45 00 00 70 81 AE 00 00 Mar 18 16:25:12 OpenWrt kern.debug kernel: 20: 38 06 EB B6 D8 9B 82 82 Mar 18 16:25:12 OpenWrt kern.debug kernel: 28: 47 6F 72 96 1A 0B E3 AC Mar 18 16:25:12 OpenWrt kern.debug kernel: 30: CC 49 2D 12 EE 82 FC BC Mar 18 16:25:12 OpenWrt kern.debug kernel: 38: 80 18 20 14 0B 67 00 00 Mar 18 16:25:12 OpenWrt kern.debug kernel: 40: 01 01 08 0A 2C 60 20 A1 Mar 18 16:25:12 OpenWrt kern.debug kernel: 48: 21 87 4F DB 3A 65 6D 61 Mar 18 16:25:12 OpenWrt kern.debug kernel: 50: 6C 64 6F 6E 61 5F 6D 74 Mar 18 16:25:12 OpenWrt kern.debug kernel: 58: 76 21 7E 65 6D 61 6C 64 Mar 18 16:25:12 OpenWrt kern.debug kernel: 60: 6F 6E 61 40 32 30 39 2E Mar 18 16:25:12 OpenWrt kern.debug kernel: 68: 31 33 32 2E 31 38 31 2E Mar 18 16:25:12 OpenWrt kern.debug kernel: 70: 38 36 20 4A 4F 49 4E 20 Mar 18 16:25:12 OpenWrt kern.debug kernel: 78: 3A 23 66 65 64 6F 72 61 Mar 18 16:25:12 OpenWrt kern.debug kernel: 80: 2D 64 65 76 65 6C 0D 0A Mar 18 16:25:12 OpenWrt kern.info kernel: solos 0000:00:0c.0: find_vcc: ddd39e00, 0.35 Mar 18 16:25:12 OpenWrt kern.info kernel: solos 0000:00:0c.0: head=e04dd42c, first= (null), mask=3 Mar 18 16:25:12 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 Mar 18 16:25:14 OpenWrt kern.info kernel: solos 0000:00:0c.0: Transmitted: port 0 Mar 18 16:25:14 OpenWrt kern.debug kernel: 00: 9D 01 00 00 23 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 08: AA AA 03 00 80 C2 00 07 Mar 18 16:25:14 OpenWrt kern.debug kernel: 10: 00 00 FF FF FF FF FF FF Mar 18 16:25:14 OpenWrt kern.debug kernel: 18: 00 0A FA 22 00 84 08 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 20: 45 00 01 85 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 28: 40 11 79 69 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 30: FF FF FF FF 00 44 00 43 Mar 18 16:25:14 OpenWrt kern.debug kernel: 38: 01 71 14 57 01 01 06 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 40: C1 48 78 3B 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 48: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 50: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 58: 00 0A FA 22 00 84 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 60: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 68: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 70: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 78: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 80: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 88: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 90: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 98: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: A0: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: A8: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: B0: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: B8: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: C0: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: C8: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: D0: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: D8: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: E0: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: E8: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: F0: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: F8: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 100: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 108: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 110: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 118: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 120: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 128: 63 82 53 63 35 01 01 3D Mar 18 16:25:14 OpenWrt kern.debug kernel: 130: 07 01 00 0A FA 22 00 84 Mar 18 16:25:14 OpenWrt kern.debug kernel: 138: 3C 0C 75 64 68 63 70 20 Mar 18 16:25:14 OpenWrt kern.debug kernel: 140: 31 2E 31 37 2E 33 39 02 Mar 18 16:25:14 OpenWrt kern.debug kernel: 148: 02 40 37 08 01 03 06 0C Mar 18 16:25:14 OpenWrt kern.debug kernel: 150: 0F 11 1C 2A FF 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 158: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 160: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 168: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 170: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 178: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 180: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 188: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 190: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 198: 00 00 00 00 00 00 00 00 Mar 18 16:25:14 OpenWrt kern.debug kernel: 1A0: 00 00 00 00 00 And I see 24 bytes of preamble from the AA AA 03 SNAP preamble to the 45 00 of the beginning of the IP packet. Not sure why there are an extra 8 bytes of prefix on transmit... as "9D 01 ... 00 00 00". Retrying in bridged mode, I get: Mar 18 16:28:08 OpenWrt kern.info kernel: solos 0000:00:0c.0: Received: device 0 Mar 18 16:28:08 OpenWrt kern.info kernel: solos 0000:00:0c.0: size: 110 VPI: 0 VCI: 35 Mar 18 16:28:08 OpenWrt kern.debug kernel: 00: AA AA 03 00 80 C2 00 07 Mar 18 16:28:08 OpenWrt kern.debug kernel: 08: 00 00 0C D5 02 58 DC B3 Mar 18 16:28:08 OpenWrt kern.debug kernel: 10: 00 90 1A 41 45 FE 08 00 Mar 18 16:28:08 OpenWrt kern.debug kernel: 18: 45 00 00 56 63 AE 00 00 Mar 18 16:28:08 OpenWrt kern.debug kernel: 20: 35 06 9E 61 4A 7D 7F 10 Mar 18 16:28:08 OpenWrt kern.debug kernel: 28: 47 6F 72 96 03 E1 E3 D2 Mar 18 16:28:08 OpenWrt kern.debug kernel: 30: 01 52 43 20 B4 88 66 AE Mar 18 16:28:08 OpenWrt kern.debug kernel: 38: 80 18 00 6A 3D 50 00 00 Mar 18 16:28:08 OpenWrt kern.debug kernel: 40: 01 01 08 0A 2F 42 B1 2B Mar 18 16:28:08 OpenWrt kern.debug kernel: 48: 21 87 4D 8D 17 03 01 00 Mar 18 16:28:08 OpenWrt kern.debug kernel: 50: 1D 59 D6 25 B7 98 89 39 Mar 18 16:28:08 OpenWrt kern.debug kernel: 58: 87 FF 9B 83 BD CC C0 3E Mar 18 16:28:08 OpenWrt kern.debug kernel: 60: 18 5A 9B 29 76 63 18 A8 Mar 18 16:28:08 OpenWrt kern.debug kernel: 68: 59 53 CE D9 C5 C7 Mar 18 16:28:08 OpenWrt kern.info kernel: solos 0000:00:0c.0: find_vcc: ddd74a00, 0.35 Mar 18 16:28:08 OpenWrt kern.info kernel: solos 0000:00:0c.0: head=e04dd42c, first= (null), mask=3 Mar 18 16:28:08 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 Mar 18 16:28:11 OpenWrt kern.info kernel: solos 0000:00:0c.0: Transmitted: port 0 Mar 18 16:28:11 OpenWrt kern.debug kernel: 00: 8D 01 00 00 23 00 00 00 Mar 18 16:28:11 OpenWrt kern.debug kernel: 08: AA AA 03 00 00 00 08 00 Mar 18 16:28:11 OpenWrt kern.debug kernel: 10: 45 00 01 85 00 00 00 00 Mar 18 16:28:11 OpenWrt kern.debug kernel: 18: 40 11 79 69 00 00 00 00 Mar 18 16:28:11 OpenWrt kern.debug kernel: 20: FF FF FF FF 00 44 00 43 Mar 18 16:28:11 OpenWrt kern.debug kernel: 28: 01 71 D3 C7 01 01 06 00 Mar 18 16:28:11 OpenWrt kern.debug kernel: 30: 90 28 DF 4C 00 00 00 00 Mar 18 16:28:11 OpenWrt kern.debug kernel: 38: 00 00 00 00 00 00 00 00 Mar 18 16:28:11 OpenWrt kern.debug kernel: 40: 00 00 00 00 00 00 00 00 Mar 18 16:28:11 OpenWrt kern.debug kernel: 48: 00 00 00 00 00 00 00 00 Mar 18 16:28:14 OpenWrt kern.info kernel: solos 0000:00:0c.0: Transmitted: port 0 Mar 18 16:28:14 OpenWrt kern.debug kernel: 00: 8D 01 00 00 23 00 00 00 Mar 18 16:28:14 OpenWrt kern.debug kernel: 08: AA AA 03 00 00 00 08 00 Mar 18 16:28:14 OpenWrt kern.debug kernel: 10: 45 00 01 85 00 00 00 00 Mar 18 16:28:14 OpenWrt kern.debug kernel: 18: 40 11 79 69 00 00 00 00 Mar 18 16:28:14 OpenWrt kern.debug kernel: 20: FF FF FF FF 00 44 00 43 Mar 18 16:28:14 OpenWrt kern.debug kernel: 28: 01 71 D3 C7 01 01 06 00 Mar 18 16:28:14 OpenWrt kern.debug kernel: 30: 90 28 DF 4C 00 00 00 00 Mar 18 16:28:14 OpenWrt kern.debug kernel: 38: 00 00 00 00 00 00 00 00 Mar 18 16:28:14 OpenWrt kern.debug kernel: 40: 00 00 00 00 00 00 00 00 Mar 18 16:28:14 OpenWrt kern.debug kernel: 48: 00 00 00 00 00 00 00 00 Mar 18 16:28:16 OpenWrt kern.info kernel: solos 0000:00:0c.0: Received: device 0 Mar 18 16:28:16 OpenWrt kern.info kernel: solos 0000:00:0c.0: size: 110 VPI: 0 VCI: 35 Mar 18 16:28:16 OpenWrt kern.debug kernel: 00: AA AA 03 00 80 C2 00 07 Mar 18 16:28:16 OpenWrt kern.debug kernel: 08: 00 00 0C D5 02 58 DC B3 Mar 18 16:28:16 OpenWrt kern.debug kernel: 10: 00 90 1A 41 45 FE 08 00 Mar 18 16:28:16 OpenWrt kern.debug kernel: 18: 45 00 00 56 63 AF 00 00 Mar 18 16:28:16 OpenWrt kern.debug kernel: 20: 35 06 9E 60 4A 7D 7F 10 Mar 18 16:28:16 OpenWrt kern.debug kernel: 28: 47 6F 72 96 03 E1 E3 D2 Mar 18 16:28:16 OpenWrt kern.debug kernel: 30: 01 52 43 20 B4 88 66 AE Mar 18 16:28:16 OpenWrt kern.debug kernel: 38: 80 18 00 6A 1C 30 00 00 Mar 18 16:28:16 OpenWrt kern.debug kernel: 40: 01 01 08 0A 2F 42 D2 4B Mar 18 16:28:16 OpenWrt kern.debug kernel: 48: 21 87 4D 8D 17 03 01 00 Mar 18 16:28:16 OpenWrt kern.debug kernel: 50: 1D 59 D6 25 B7 98 89 39 Mar 18 16:28:16 OpenWrt kern.debug kernel: 58: 87 FF 9B 83 BD CC C0 3E Mar 18 16:28:16 OpenWrt kern.debug kernel: 60: 18 5A 9B 29 76 63 18 A8 Mar 18 16:28:16 OpenWrt kern.debug kernel: 68: 59 53 CE D9 C5 C7 Mar 18 16:28:16 OpenWrt kern.info kernel: solos 0000:00:0c.0: find_vcc: ddd74a00, 0.35 Mar 18 16:28:16 OpenWrt kern.info kernel: solos 0000:00:0c.0: head=e04dd42c, first= (null), mask=3 Mar 18 16:28:16 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 Mar 18 16:28:17 OpenWrt kern.info kernel: solos 0000:00:0c.0: Transmitted: port 0 Mar 18 16:28:17 OpenWrt kern.debug kernel: 00: 8D 01 00 00 23 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 08: AA AA 03 00 00 00 08 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 10: 45 00 01 85 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 18: 40 11 79 69 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 20: FF FF FF FF 00 44 00 43 Mar 18 16:28:17 OpenWrt kern.debug kernel: 28: 01 71 D3 C7 01 01 06 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 30: 90 28 DF 4C 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 38: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 40: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 48: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 50: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 58: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 60: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 68: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 70: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 78: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 80: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 88: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 90: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 98: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: A0: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: A8: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: B0: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: B8: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: C0: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: C8: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: D0: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: D8: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: E0: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: E8: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: F0: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: F8: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 100: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 108: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 110: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 118: 63 82 53 63 35 01 01 3D Mar 18 16:28:17 OpenWrt kern.debug kernel: 120: 07 01 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 128: 3C 0C 75 64 68 63 70 20 Mar 18 16:28:17 OpenWrt kern.debug kernel: 130: 31 2E 31 37 2E 33 39 02 Mar 18 16:28:17 OpenWrt kern.debug kernel: 138: 02 40 37 08 01 03 06 0C Mar 18 16:28:17 OpenWrt kern.debug kernel: 140: 0F 11 1C 2A FF 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 148: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 150: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 158: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 160: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 168: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 170: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 178: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 180: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 188: 00 00 00 00 00 00 00 00 Mar 18 16:28:17 OpenWrt kern.debug kernel: 190: 00 00 00 00 00 Mar 18 16:28:20 OpenWrt kern.info kernel: solos 0000:00:0c.0: Transmitted: port 0 Mar 18 16:28:20 OpenWrt kern.debug kernel: 00: 8D 01 00 00 23 00 00 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 08: AA AA 03 00 00 00 08 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 10: 45 00 01 85 00 00 00 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 18: 40 11 79 69 00 00 00 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 20: FF FF FF FF 00 44 00 43 Mar 18 16:28:20 OpenWrt kern.debug kernel: 28: 01 71 D3 C7 01 01 06 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 30: 90 28 DF 4C 00 00 00 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 38: 00 00 00 00 00 00 00 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 40: 00 00 00 00 00 00 00 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 48: 00 00 00 00 00 00 00 00 Mar 18 16:28:20 OpenWrt kern.info kernel: solos 0000:00:0c.0: Received: device 0 Mar 18 16:28:20 OpenWrt kern.info kernel: solos 0000:00:0c.0: size: 214 VPI: 0 VCI: 35 Mar 18 16:28:20 OpenWrt kern.debug kernel: 00: AA AA 03 00 80 C2 00 07 Mar 18 16:28:20 OpenWrt kern.debug kernel: 08: 00 00 0C D5 02 58 DC B3 Mar 18 16:28:20 OpenWrt kern.debug kernel: 10: 00 90 1A 41 45 FE 08 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 18: 45 00 00 BE BD 19 40 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 20: 38 06 3A 7F C6 89 CA 12 Mar 18 16:28:20 OpenWrt kern.debug kernel: 28: 47 6F 72 96 03 E1 E3 CD Mar 18 16:28:20 OpenWrt kern.debug kernel: 30: 28 7D 87 1A 59 6E EE 7B Mar 18 16:28:20 OpenWrt kern.debug kernel: 38: 80 18 82 18 61 C0 00 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 40: 01 01 08 0A 29 5D 34 4F Mar 18 16:28:20 OpenWrt kern.debug kernel: 48: 21 87 4F 95 17 03 01 00 Mar 18 16:28:20 OpenWrt kern.debug kernel: 50: 40 0E 30 D7 94 BD D6 41 Mar 18 16:28:20 OpenWrt kern.debug kernel: 58: D8 1D 1D 6C FF 97 CC 3A Mar 18 16:28:20 OpenWrt kern.debug kernel: 60: 01 67 D4 DB 7E 6C D5 A7 Mar 18 16:28:20 OpenWrt kern.debug kernel: 68: 80 BA 37 F5 F0 AB 4C FC Mar 18 16:28:20 OpenWrt kern.debug kernel: 70: 37 6D 62 E9 70 A4 5C 6C Mar 18 16:28:20 OpenWrt kern.debug kernel: 78: B4 80 4A ED 19 81 06 DE Mar 18 16:28:20 OpenWrt kern.debug kernel: 80: 74 45 18 2A FC 86 58 C3 Mar 18 16:28:20 OpenWrt kern.debug kernel: 88: 63 F1 68 C7 E0 EB 9D B3 Mar 18 16:28:20 OpenWrt kern.debug kernel: 90: 3F 17 03 01 00 40 14 E9 Mar 18 16:28:20 OpenWrt kern.debug kernel: 98: D7 D4 E3 C4 2A DF EA 5D Mar 18 16:28:20 OpenWrt kern.debug kernel: A0: 6E 00 4B 9A 1F 27 F9 07 Mar 18 16:28:20 OpenWrt kern.debug kernel: A8: 55 67 5B 45 D6 76 09 A4 Mar 18 16:28:20 OpenWrt kern.debug kernel: B0: 69 28 B1 4F 54 80 DB 15 Mar 18 16:28:20 OpenWrt kern.debug kernel: B8: 3A 01 3A A1 6E 89 F8 E7 Mar 18 16:28:20 OpenWrt kern.debug kernel: C0: 2A EA 2E 59 13 09 44 A1 Mar 18 16:28:20 OpenWrt kern.debug kernel: C8: F7 06 85 74 A0 07 20 88 Mar 18 16:28:20 OpenWrt kern.debug kernel: D0: 55 7E 4A C4 D0 75 Mar 18 16:28:20 OpenWrt kern.info kernel: solos 0000:00:0c.0: find_vcc: ddd74a00, 0.35 Mar 18 16:28:20 OpenWrt kern.info kernel: solos 0000:00:0c.0: head=e04dd42c, first= (null), mask=3 Mar 18 16:28:20 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 So we're receiving 24 bytes of preamble (AA AA 03 ... 00 80), but we send either 16 bytes of MAC header with a 8 byte prefix in bridged mode (that's probably just the logging showing something before the header), or we send 8 bytes of prefix and 8 bytes of MAC header in routed mode. My money is on routed mode. Two things stand out from these traces... (1) minor, we're seeing 8 bytes of prefix on transmit that we don't see on transmit (is that buffer descriptor or what?)... which incidentally is the same size as the pkt_hdr structure. (2) we're consistently seeing find_vcc() return NULL also not clear why "vpi" is usually a short in the code, but "vci" is more often an "int". This is running 2.6.37... I was previously using the same image with Qwest and PPPoA, and that seemed to work fine. It's not clear to me why the hash of VC's is kept on a per-driver basis... shouldn't that go in atm common stuff? Taking the 8-bytes of prefix and disassembling it as a struct pkt_hdr, I get: 9D 01 00 00 23 00 00 00 0x019d (413) == size 0x0000 (0) == vpi 0x0023 (35) == vci 0x0000 (0) == type (PKT_DATA) Oh, and another couple of nits, we say "Received: device 0", but "Transmitted: port 0"... and we dump the first 3 fields of the pkt_hdr on receive but not on transmit. Thanks, -Philip |
|
From: Guy E. <gu...@tr...> - 2011-03-12 20:39:40
|
No need for (2), you can do this with ifconfig. ifconfig nas0 hw ether xx:xx:xx:xx:xx:xx up Cheers, - Guy. On 13/03/2011 7:28 AM, Philip Prindeville wrote: > I urgently need to features for br2684ctl... I'll try to bang them out in the next few days, but if someone more familiar with the code than me has an opportunity to do so that would be awesome. > > They're fairly trivial: > > (1) allow specifying a "pid" file when backgrounding; > (2) allow specifying a MAC hardware address when running in bridged mode (i.e. -p 1); > > See the threads: > > http://patchwork.midlink.org/patch/773/ > http://patchwork.midlink.org/patch/775/ > > for the background. > > Thanks, > > -Philip > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Linux-atm-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-atm-general > > -- Guy Ellis gu...@tr... http://www.traverse.com.au Skype: guy.ellis1 Tel: +613 9386 4430 Fax: +613 9386 4435 |
|
From: Philip P. <phi...@re...> - 2011-03-12 20:29:01
|
I urgently need to features for br2684ctl... I'll try to bang them out in the next few days, but if someone more familiar with the code than me has an opportunity to do so that would be awesome. They're fairly trivial: (1) allow specifying a "pid" file when backgrounding; (2) allow specifying a MAC hardware address when running in bridged mode (i.e. -p 1); See the threads: http://patchwork.midlink.org/patch/773/ http://patchwork.midlink.org/patch/775/ for the background. Thanks, -Philip |
|
From: Philip P. <phi...@re...> - 2011-03-07 06:25:26
|
On 3/6/11 1:36 AM, Karl Hiramoto wrote: > On 03/06/11 02:38, Philip Prindeville wrote: >> "nas1"? >> >> Hmm..... Also, how do I clone the MAC address of the Westell when using RFC-2684 mode? >> > nasX are the default RFC2884 devices. use br2684ctl to create them. > > I have seen one provider (vodafone) in spain filter MAC addresses and > the hostname on the DHCP request. > > Th only way i know to find the MAC address will be to: > > 1. The logs > 2. hack the device > 3. Some providers use the device serial number as MAC > 4. use your own DSLAM on one end of line and setup a sniffer. I > have a cheap zisa DLAM I've done this with you have to know the > VPI/VCI they are using to try this. > 5. Search internet or try and contact your provider for the settings. > > > -- > Karl I'll those in order. I got the MAC device out of the status screen from the modem... no hacking required. Owning my own DSLAM sounds kind of cool. :-) I still don't understand what the message: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 means, however. If I've already done a: br2684ctl -b -c 0 -e 0 -p 0 -a 0.0.35 then why would 0.35 be considered "unknown"? Isn't that exactly what I'm listening on? What am I missing? -Philip |
|
From: Guy E. <gu...@tr...> - 2011-03-07 01:27:29
|
Not true for PPPoA - sorry. - Guy. On 7/03/2011 11:30 AM, Philip Prindeville wrote: > Well, if you passively listen, you'll eventually get a frame: > > Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: > Received packet for unknown VPI.VCI 0.35 on port 0 > > > and I was thinking that might be usable to then figure out what > vpi/vci to do a "aread" or "atmdump" on. > > From that, you could match against a pattern to see if it looks like > an LCP frame or an IP-over-SNAP frame. > > > > On 3/5/11 9:15 PM, Guy Ellis wrote: >> Hi Philip, >> >> Unfortunately auto-detecting PPP links as totally inpractical - you >> would have to send out an LCP request on every PVC! >> >> Based on your later emails, it looks like you should used bridged >> ethernet. >> >> See section 4 of the Geos Linux User Manual for tips. >> If your ISP uses DHCP then bring the interface up unnumbered >> >> ifconfig nas0 up >> >> >> Where is the user manual you ask? >> If you go to the Geos product page, there is a link for the Linux >> User Manual top RHS... >> http://www.traverse.com.au/productview.php?product_id=117 >> >> Cheers, >> >> - Guy. >> >> >> On 6/03/2011 9:59 AM, Philip Prindeville wrote: >>> There's no utility to auto-detect the configuration? >>> >>> What about using atmdump? >>> >>> -Philip >>> >>> On 3/5/11 2:18 PM, Guy Ellis wrote: >>>> Hi Philip, >>>> >>>> Try PPPoA, VPI = 0, VCI = 35 and see if that works. >>>> >>>> I've got to go to the football this morning, so I'll put up the >>>> lastest user docs when I get back and post a link. >>>> >>>> Cheers, >>>> >>>> - Guy. >>>> >>>> >>>> >>>> >>>> >>>> On 6/03/2011 7:20 AM, Philip Prindeville wrote: >>>>> I recently moved into Frontier Communications land, and it's been >>>>> difficult getting support from them on non-Frontier issued >>>>> equipment (including being told the settings were 'proprietary'... >>>>> huh???). >>>>> >>>>> Anyway, I'm troubleshooting the DSL support on OpenWRT which is >>>>> somewhat untested on my Geos (which has the Solos chipset built in). >>>>> >>>>> I'm using the config: >>>>> >>>>> config 'interface' 'wan' >>>>> option 'proto' 'dhcp' >>>>> option 'ifname' 'nas0' >>>>> >>>>> config 'atm-bridge' >>>>> option 'unit' '0' >>>>> option 'vpi' '0' >>>>> option 'vci' '35' >>>>> option 'atmdev' '0' >>>>> option 'encaps' 'vc' >>>>> option 'payload' 'routed' >>>>> >>>>> ("atmdev" just sets the unit # for the nasX interface, 'unit' sets >>>>> the port # on a multiport card) >>>>> >>>>> But this isn't working and indeed I'm seeing: >>>>> >>>>> Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: >>>>> Received packet for unknown VPI.VCI 0.35 on port 0 >>>>> >>>>> Can someone walk me through troubleshooting this? >>>>> >>>>> Glancing at the driver code, it's not clear why I'd be seeing that >>>>> message. I'm running 2.6.37. >>>>> >>>>> Thanks, >>>>> >>>>> -Philip >>>>> >> |
|
From: Philip P. <phi...@re...> - 2011-03-07 00:31:08
|
Well, if you passively listen, you'll eventually get a frame: Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 and I was thinking that might be usable to then figure out what vpi/vci to do a "aread" or "atmdump" on. From that, you could match against a pattern to see if it looks like an LCP frame or an IP-over-SNAP frame. On 3/5/11 9:15 PM, Guy Ellis wrote: > Hi Philip, > > Unfortunately auto-detecting PPP links as totally inpractical - you would have to send out an LCP request on every PVC! > > Based on your later emails, it looks like you should used bridged ethernet. > > See section 4 of the Geos Linux User Manual for tips. > If your ISP uses DHCP then bring the interface up unnumbered > > ifconfig nas0 up > > > Where is the user manual you ask? > If you go to the Geos product page, there is a link for the Linux User Manual top RHS... > http://www.traverse.com.au/productview.php?product_id=117 > > Cheers, > > - Guy. > > > On 6/03/2011 9:59 AM, Philip Prindeville wrote: >> There's no utility to auto-detect the configuration? >> >> What about using atmdump? >> >> -Philip >> >> On 3/5/11 2:18 PM, Guy Ellis wrote: >>> Hi Philip, >>> >>> Try PPPoA, VPI = 0, VCI = 35 and see if that works. >>> >>> I've got to go to the football this morning, so I'll put up the lastest user docs when I get back and post a link. >>> >>> Cheers, >>> >>> - Guy. >>> >>> >>> >>> >>> >>> On 6/03/2011 7:20 AM, Philip Prindeville wrote: >>>> I recently moved into Frontier Communications land, and it's been difficult getting support from them on non-Frontier issued equipment (including being told the settings were 'proprietary'... huh???). >>>> >>>> Anyway, I'm troubleshooting the DSL support on OpenWRT which is somewhat untested on my Geos (which has the Solos chipset built in). >>>> >>>> I'm using the config: >>>> >>>> config 'interface' 'wan' >>>> option 'proto' 'dhcp' >>>> option 'ifname' 'nas0' >>>> >>>> config 'atm-bridge' >>>> option 'unit' '0' >>>> option 'vpi' '0' >>>> option 'vci' '35' >>>> option 'atmdev' '0' >>>> option 'encaps' 'vc' >>>> option 'payload' 'routed' >>>> >>>> ("atmdev" just sets the unit # for the nasX interface, 'unit' sets the port # on a multiport card) >>>> >>>> But this isn't working and indeed I'm seeing: >>>> >>>> Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 >>>> >>>> Can someone walk me through troubleshooting this? >>>> >>>> Glancing at the driver code, it's not clear why I'd be seeing that message. I'm running 2.6.37. >>>> >>>> Thanks, >>>> >>>> -Philip >>>> > |
|
From: Karl H. <ka...@hi...> - 2011-03-06 09:36:38
|
On 03/06/11 02:38, Philip Prindeville wrote: > > "nas1"? > > Hmm..... Also, how do I clone the MAC address of the Westell when using RFC-2684 mode? > nasX are the default RFC2884 devices. use br2684ctl to create them. I have seen one provider (vodafone) in spain filter MAC addresses and the hostname on the DHCP request. Th only way i know to find the MAC address will be to: 1. The logs 2. hack the device 3. Some providers use the device serial number as MAC 4. use your own DSLAM on one end of line and setup a sniffer. I have a cheap zisa DLAM I've done this with you have to know the VPI/VCI they are using to try this. 5. Search internet or try and contact your provider for the settings. -- Karl |
|
From: Guy E. <gu...@tr...> - 2011-03-06 05:15:40
|
Hi Philip, Unfortunately auto-detecting PPP links as totally inpractical - you would have to send out an LCP request on every PVC! Based on your later emails, it looks like you should used bridged ethernet. See section 4 of the Geos Linux User Manual for tips. If your ISP uses DHCP then bring the interface up unnumbered ifconfig nas0 up Where is the user manual you ask? If you go to the Geos product page, there is a link for the Linux User Manual top RHS... http://www.traverse.com.au/productview.php?product_id=117 Cheers, - Guy. On 6/03/2011 9:59 AM, Philip Prindeville wrote: > There's no utility to auto-detect the configuration? > > What about using atmdump? > > -Philip > > On 3/5/11 2:18 PM, Guy Ellis wrote: >> Hi Philip, >> >> Try PPPoA, VPI = 0, VCI = 35 and see if that works. >> >> I've got to go to the football this morning, so I'll put up the >> lastest user docs when I get back and post a link. >> >> Cheers, >> >> - Guy. >> >> >> >> >> >> On 6/03/2011 7:20 AM, Philip Prindeville wrote: >>> I recently moved into Frontier Communications land, and it's been >>> difficult getting support from them on non-Frontier issued equipment >>> (including being told the settings were 'proprietary'... huh???). >>> >>> Anyway, I'm troubleshooting the DSL support on OpenWRT which is >>> somewhat untested on my Geos (which has the Solos chipset built in). >>> >>> I'm using the config: >>> >>> config 'interface' 'wan' >>> option 'proto' 'dhcp' >>> option 'ifname' 'nas0' >>> >>> config 'atm-bridge' >>> option 'unit' '0' >>> option 'vpi' '0' >>> option 'vci' '35' >>> option 'atmdev' '0' >>> option 'encaps' 'vc' >>> option 'payload' 'routed' >>> >>> ("atmdev" just sets the unit # for the nasX interface, 'unit' sets >>> the port # on a multiport card) >>> >>> But this isn't working and indeed I'm seeing: >>> >>> Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: >>> Received packet for unknown VPI.VCI 0.35 on port 0 >>> >>> Can someone walk me through troubleshooting this? >>> >>> Glancing at the driver code, it's not clear why I'd be seeing that >>> message. I'm running 2.6.37. >>> >>> Thanks, >>> >>> -Philip >>> |
|
From: Philip P. <phi...@re...> - 2011-03-06 01:38:54
|
Couple of other things make me think that it's using RFC-2684. See: ftp://ftp.redfish-solutions.com/pub/westell.png And looking at the connection logs on the Westell that Frontier lent me: Jan 1 07:45:54 daemon.notice net_mgr[350]: Routes transitioning to Up state on nas1. ... Jan 1 07:45:50 local0.info udhcpc[2566]: Lease of 71.111.120.3 obtained,lease time 7200 Jan 1 07:45:49 local0.debug udhcpc[2566]: Sending select for 71.111.120.3... Jan 1 07:45:49 local0.debug udhcpc[2566]: Sending discover... Jan 1 07:45:46 local0.debug udhcpc[2566]: Sending discover... Ok, so cutting and pasting HTML tables blows... "nas1"? Hmm..... Also, how do I clone the MAC address of the Westell when using RFC-2684 mode? Thanks, -Philip On 3/5/11 2:18 PM, Guy Ellis wrote: > Hi Philip, > > Try PPPoA, VPI = 0, VCI = 35 and see if that works. > > I've got to go to the football this morning, so I'll put up the lastest user docs when I get back and post a link. > > Cheers, > > - Guy. > > > > > > On 6/03/2011 7:20 AM, Philip Prindeville wrote: >> I recently moved into Frontier Communications land, and it's been difficult getting support from them on non-Frontier issued equipment (including being told the settings were 'proprietary'... huh???). >> >> Anyway, I'm troubleshooting the DSL support on OpenWRT which is somewhat untested on my Geos (which has the Solos chipset built in). >> >> I'm using the config: >> >> config 'interface' 'wan' >> option 'proto' 'dhcp' >> option 'ifname' 'nas0' >> >> config 'atm-bridge' >> option 'unit' '0' >> option 'vpi' '0' >> option 'vci' '35' >> option 'atmdev' '0' >> option 'encaps' 'vc' >> option 'payload' 'routed' >> >> ("atmdev" just sets the unit # for the nasX interface, 'unit' sets the port # on a multiport card) >> >> But this isn't working and indeed I'm seeing: >> >> Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 >> >> Can someone walk me through troubleshooting this? >> >> Glancing at the driver code, it's not clear why I'd be seeing that message. I'm running 2.6.37. >> >> Thanks, >> >> -Philip |
|
From: Philip P. <phi...@re...> - 2011-03-05 23:00:11
|
There's no utility to auto-detect the configuration?
What about using atmdump?
-Philip
On 3/5/11 2:18 PM, Guy Ellis wrote:
> Hi Philip,
>
> Try PPPoA, VPI = 0, VCI = 35 and see if that works.
>
> I've got to go to the football this morning, so I'll put up the lastest user docs when I get back and post a link.
>
> Cheers,
>
> - Guy.
>
>
>
>
>
> On 6/03/2011 7:20 AM, Philip Prindeville wrote:
>> I recently moved into Frontier Communications land, and it's been difficult getting support from them on non-Frontier issued equipment (including being told the settings were 'proprietary'... huh???).
>>
>> Anyway, I'm troubleshooting the DSL support on OpenWRT which is somewhat untested on my Geos (which has the Solos chipset built in).
>>
>> I'm using the config:
>>
>> config 'interface' 'wan'
>> option 'proto' 'dhcp'
>> option 'ifname' 'nas0'
>>
>> config 'atm-bridge'
>> option 'unit' '0'
>> option 'vpi' '0'
>> option 'vci' '35'
>> option 'atmdev' '0'
>> option 'encaps' 'vc'
>> option 'payload' 'routed'
>>
>> ("atmdev" just sets the unit # for the nasX interface, 'unit' sets the port # on a multiport card)
>>
>> But this isn't working and indeed I'm seeing:
>>
>> Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0
>>
>> Can someone walk me through troubleshooting this?
>>
>> Glancing at the driver code, it's not clear why I'd be seeing that message. I'm running 2.6.37.
>>
>> Thanks,
>>
>> -Philip
>>
|
|
From: Guy E. <gu...@tr...> - 2011-03-05 22:48:16
|
Hi Philip,
Try PPPoA, VPI = 0, VCI = 35 and see if that works.
I've got to go to the football this morning, so I'll put up the lastest
user docs when I get back and post a link.
Cheers,
- Guy.
On 6/03/2011 7:20 AM, Philip Prindeville wrote:
> I recently moved into Frontier Communications land, and it's been difficult getting support from them on non-Frontier issued equipment (including being told the settings were 'proprietary'... huh???).
>
> Anyway, I'm troubleshooting the DSL support on OpenWRT which is somewhat untested on my Geos (which has the Solos chipset built in).
>
> I'm using the config:
>
> config 'interface' 'wan'
> option 'proto' 'dhcp'
> option 'ifname' 'nas0'
>
> config 'atm-bridge'
> option 'unit' '0'
> option 'vpi' '0'
> option 'vci' '35'
> option 'atmdev' '0'
> option 'encaps' 'vc'
> option 'payload' 'routed'
>
> ("atmdev" just sets the unit # for the nasX interface, 'unit' sets the port # on a multiport card)
>
> But this isn't working and indeed I'm seeing:
>
> Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0
>
> Can someone walk me through troubleshooting this?
>
> Glancing at the driver code, it's not clear why I'd be seeing that message. I'm running 2.6.37.
>
> Thanks,
>
> -Philip
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Linux-atm-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-atm-general
>
>
--
Guy Ellis
gu...@tr...
http://www.traverse.com.au
Skype: guy.ellis1
Tel: +613 9386 4430
Fax: +613 9386 4435
|
|
From: Philip P. <phi...@re...> - 2011-03-05 20:20:37
|
I recently moved into Frontier Communications land, and it's been difficult getting support from them on non-Frontier issued equipment (including being told the settings were 'proprietary'... huh???).
Anyway, I'm troubleshooting the DSL support on OpenWRT which is somewhat untested on my Geos (which has the Solos chipset built in).
I'm using the config:
config 'interface' 'wan'
option 'proto' 'dhcp'
option 'ifname' 'nas0'
config 'atm-bridge'
option 'unit' '0'
option 'vpi' '0'
option 'vci' '35'
option 'atmdev' '0'
option 'encaps' 'vc'
option 'payload' 'routed'
("atmdev" just sets the unit # for the nasX interface, 'unit' sets the port # on a multiport card)
But this isn't working and indeed I'm seeing:
Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0
Can someone walk me through troubleshooting this?
Glancing at the driver code, it's not clear why I'd be seeing that message. I'm running 2.6.37.
Thanks,
-Philip
|
|
From: chas w. - C. <ch...@cm...> - 2011-02-19 12:50:24
|
On Fri, 18 Feb 2011 17:36:01 -0800 Philip Prindeville <phi...@re...> wrote: > Is there any traffic on this list? I've not see anything in a few weeks. > > Stranger still, a posting from netdev that was copied to this list never made it into my mailbox. some mailers can hide duplicate messages based on message-id. however, if the author was not subscribed to the linux-atm list i suspect it was put in the moderation queue. |
|
From: Mr. J. W. L. <ba...@ba...> - 2011-02-19 02:00:08
|
Hello Philip , Yup the list still works . When traffic hits it that is . Hth , JimL On Fri, 18 Feb 2011, Philip Prindeville wrote: > Is there any traffic on this list? I've not see anything in a few weeks. > > Stranger still, a posting from netdev that was copied to this list never made it into my mailbox. -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | ba...@ba... | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+ |
|
From: Philip P. <phi...@re...> - 2011-02-19 01:36:15
|
Is there any traffic on this list? I've not see anything in a few weeks. Stranger still, a posting from netdev that was copied to this list never made it into my mailbox. |
|
From: chas w. - C. <ch...@cm...> - 2011-01-26 15:01:21
|
well it seems pretty clear that the zatm driver must be broken. can you try 'aread 0.100' and 'awrite 0.100 'hello world"' these test programs will just open a vc (one in readonly and one in write-only). perhaps we can narrow it down. otherwise we will need to enable debugging in the zatm driver, rebuild it, and catch the console messages to see where the driver is broken. On Tue, 25 Jan 2011 14:38:23 +0000 Maestrelli Francesco <fra...@aa...> wrote: > So.. I tried to play around a bit with what you told me, but I still have the same problems. > > I closed X window, stopped the gdm service, I used Klogd -c 6 and i got the following: > > sudo atmsigd -b ->> Error: line 18 syntax error near "entity" and the system freezes. > > sudo ilmid -b ->> the system freezes with no messages > > Considering that It seems I don't need these, I tried br2684ctl and I got: > > sudo br2684ctl -c 0 -e 1 -a 0.101 ->> Interface "nas0" created successfully > ->> Communicating over ATM 0.0.101, encapsulation: VCmux > ->> system freezes > > > I tried also with the default paramenters (encapsulation LLC) but it freezes anyway. > I thought that it could be because the endpoint in the DSLAM wasn't configured, but I checked and it seems configured correctly (VPI 0 and VCI 101). > > any other suggestions? Could it be a problem with the zatm driver? > > Francesco Maestrelli > ------------------------------------ > fra...@aa... > > ________________________________________ > From: chas williams - CONTRACTOR [ch...@cm...] > Sent: 21 January 2011 17:27 > To: Maestrelli Francesco > Cc: lin...@li... > Subject: Re: [Linux-ATM-General] atm-tools and Ubuntu 10.10 > > On Fri, 21 Jan 2011 10:20:25 +0000 > Maestrelli Francesco <fra...@aa...> wrote: > > > I forgot to add as a CC to my answer the whole mailing list. Sorry for that and for sending again this message. > > > > Little description: > > > > I'm trying to configure an ATM connection between a computer I'm setting up and a DSLAM (Nokia D50, former Eksos B20) that will be connected over ADSL to an ADSL modem (M10 ADSL modem). This should simulate the standard conficuration an ISP could use to provide ADSL services to its customers. > > > > The computer I'm setting up should act as a switch or router and forward the requests coming from the ADSL connection (that the client computer connected to the ADSL modem will send) to the default gateway of the network I'm connected to. To do this the computer also have an ethernet card connected to the local network. > > > > Problem: > > > > The computer I'm setting up is running ubuntu 10.10 (kernel 2.6.35-24-generic), 512MB RAM, AMD Athlon Processor 1,4 Ghz. I was looking for information on the net to set up this environment, but i couldn't find much. > > I'm actually following this: http://www.linuxjournal.com/article/3005 even if it's a quite old article. > > > > When I start atmsigd or ilmid the computer suddenly stop responding. > > if you dont start X windows and turn off kernel logging so that it > appears on the screen (service syslog stop i think and klogd -c 6 > as well on some systems) do you see any oops? sometimes it is helpful > if you have a serial console setup to catch any errors on another > computer. > > however, given your config, you need a pvc, so you really dont need > ilmid or atmsigd. you only need to run those for pvc's. > > > Since I need to create a connection between this computer and the DSLAM and from there to the modem i think I'll need to setup a PVC thus I don't think I'll need those daemon.. right? What could be the reason they freeze anyway? > > as i recall from your other message to me, you are using a zeitnet > card. this is the zatm driver which should work but i havent heard of > any reports of it working either in quite a while. i dont happen to > have a zeinet on hand to test the driver in any way. > > > > > Leaving aside these two I did the following: > > > > * I created the ATM device name: atmarp -c atm0 > > > > and from ifconfig -a i see the following: > > > > atm0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > > [NO FLAGS] MTU:9180 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:100 > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > > (Isn't it weird that HWaddr is all zeros?) > > > > > > * I configured the interface : ifconfig atm0 10.38.100.254 netmask 255.255.255.0 mtu 9180 > > > > * I added a route for the ATM subnet : route add -net 10.38.100.0 netmask 255.255.255.0 atm0 > > > > *Now I tried to setup the PVC: atmarp -s 10.38.100.101 0.0.101 (VPI:0 VCI:101) > > > > now I'm not totally sure about this command, but as I said I can't find much documentation on how do do this. > > At this point the pc freezes again. > > > > > > Probably It's my bad that I'm not understanding something. Any help would be precious. Thanks in advance. > > you probably want br2684ctl instead. this creates a single ip > interface bound to a pvc. there is a man page for it here: > > http://linux.die.net/man/8/br2684ctl > > > > > > BR, > > > > Francesco Maestrelli > > ------------------------------------ > > fra...@aa... > > > > ________________________________________ > > From: chas williams - CONTRACTOR [ch...@cm...] > > Sent: 20 January 2011 17:10 > > To: Maestrelli Francesco > > Cc: lin...@li... > > Subject: Re: [Linux-ATM-General] atm-tools and Ubuntu 10.10 > > > > nothing that i know about specifically. what is your hardware and what > > are commands are you running? > > > > On Thu, 20 Jan 2011 11:03:59 +0000 > > Maestrelli Francesco <fra...@aa...> wrote: > > > > > Are there know issues with the atm daemons and Ubuntu 10.10? When I l start them following instructions in here http://www.linuxjournal.com/article/3005 the machine freezes. > > > > > > Thanks > > > > > > Francesco > > > > > > ------------------------------------------------------------------------------ > > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > > Finally, a world-class log management solution at an even better price-free! > > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > > February 28th, so secure your free ArcSight Logger TODAY! > > http://p.sf.net/sfu/arcsight-sfd2d > > _______________________________________________ > > Linux-atm-general mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linux-atm-general > > > > |
|
From: Maestrelli F. <fra...@aa...> - 2011-01-25 14:38:33
|
So.. I tried to play around a bit with what you told me, but I still have the same problems.
I closed X window, stopped the gdm service, I used Klogd -c 6 and i got the following:
sudo atmsigd -b ->> Error: line 18 syntax error near "entity" and the system freezes.
sudo ilmid -b ->> the system freezes with no messages
Considering that It seems I don't need these, I tried br2684ctl and I got:
sudo br2684ctl -c 0 -e 1 -a 0.101 ->> Interface "nas0" created successfully
->> Communicating over ATM 0.0.101, encapsulation: VCmux
->> system freezes
I tried also with the default paramenters (encapsulation LLC) but it freezes anyway.
I thought that it could be because the endpoint in the DSLAM wasn't configured, but I checked and it seems configured correctly (VPI 0 and VCI 101).
any other suggestions? Could it be a problem with the zatm driver?
Francesco Maestrelli
------------------------------------
fra...@aa...
________________________________________
From: chas williams - CONTRACTOR [ch...@cm...]
Sent: 21 January 2011 17:27
To: Maestrelli Francesco
Cc: lin...@li...
Subject: Re: [Linux-ATM-General] atm-tools and Ubuntu 10.10
On Fri, 21 Jan 2011 10:20:25 +0000
Maestrelli Francesco <fra...@aa...> wrote:
> I forgot to add as a CC to my answer the whole mailing list. Sorry for that and for sending again this message.
>
> Little description:
>
> I'm trying to configure an ATM connection between a computer I'm setting up and a DSLAM (Nokia D50, former Eksos B20) that will be connected over ADSL to an ADSL modem (M10 ADSL modem). This should simulate the standard conficuration an ISP could use to provide ADSL services to its customers.
>
> The computer I'm setting up should act as a switch or router and forward the requests coming from the ADSL connection (that the client computer connected to the ADSL modem will send) to the default gateway of the network I'm connected to. To do this the computer also have an ethernet card connected to the local network.
>
> Problem:
>
> The computer I'm setting up is running ubuntu 10.10 (kernel 2.6.35-24-generic), 512MB RAM, AMD Athlon Processor 1,4 Ghz. I was looking for information on the net to set up this environment, but i couldn't find much.
> I'm actually following this: http://www.linuxjournal.com/article/3005 even if it's a quite old article.
>
> When I start atmsigd or ilmid the computer suddenly stop responding.
if you dont start X windows and turn off kernel logging so that it
appears on the screen (service syslog stop i think and klogd -c 6
as well on some systems) do you see any oops? sometimes it is helpful
if you have a serial console setup to catch any errors on another
computer.
however, given your config, you need a pvc, so you really dont need
ilmid or atmsigd. you only need to run those for pvc's.
> Since I need to create a connection between this computer and the DSLAM and from there to the modem i think I'll need to setup a PVC thus I don't think I'll need those daemon.. right? What could be the reason they freeze anyway?
as i recall from your other message to me, you are using a zeitnet
card. this is the zatm driver which should work but i havent heard of
any reports of it working either in quite a while. i dont happen to
have a zeinet on hand to test the driver in any way.
>
> Leaving aside these two I did the following:
>
> * I created the ATM device name: atmarp -c atm0
>
> and from ifconfig -a i see the following:
>
> atm0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> [NO FLAGS] MTU:9180 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:100
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> (Isn't it weird that HWaddr is all zeros?)
>
>
> * I configured the interface : ifconfig atm0 10.38.100.254 netmask 255.255.255.0 mtu 9180
>
> * I added a route for the ATM subnet : route add -net 10.38.100.0 netmask 255.255.255.0 atm0
>
> *Now I tried to setup the PVC: atmarp -s 10.38.100.101 0.0.101 (VPI:0 VCI:101)
>
> now I'm not totally sure about this command, but as I said I can't find much documentation on how do do this.
> At this point the pc freezes again.
>
>
> Probably It's my bad that I'm not understanding something. Any help would be precious. Thanks in advance.
you probably want br2684ctl instead. this creates a single ip
interface bound to a pvc. there is a man page for it here:
http://linux.die.net/man/8/br2684ctl
>
> BR,
>
> Francesco Maestrelli
> ------------------------------------
> fra...@aa...
>
> ________________________________________
> From: chas williams - CONTRACTOR [ch...@cm...]
> Sent: 20 January 2011 17:10
> To: Maestrelli Francesco
> Cc: lin...@li...
> Subject: Re: [Linux-ATM-General] atm-tools and Ubuntu 10.10
>
> nothing that i know about specifically. what is your hardware and what
> are commands are you running?
>
> On Thu, 20 Jan 2011 11:03:59 +0000
> Maestrelli Francesco <fra...@aa...> wrote:
>
> > Are there know issues with the atm daemons and Ubuntu 10.10? When I l start them following instructions in here http://www.linuxjournal.com/article/3005 the machine freezes.
> >
> > Thanks
> >
> > Francesco
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Linux-atm-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-atm-general
>
|
|
From: Philip P. <phi...@re...> - 2011-01-24 19:16:22
|
Looks good to me! -Philip On 1/24/11 8:22 AM, chas williams - CONTRACTOR wrote: > i created a new branch V2_5_3 and integrated the openwrt. if you could > take a quick look when you have time. > > On Sat, 22 Jan 2011 12:02:37 -0800 > Philip Prindeville<phi...@re...> wrote: > >> I was updating OpenWRT to use 2.5.2, and saw these patches. >> >> https://dev.openwrt.org/browser/trunk/package/linux-atm/patches >> >> All of the first patch applies... >> >> The second patch seems to disable linking with Flex. >> >> Can we make flex an autoconf option, i.e. --disable-flex ? >> >> The first set of patches affect Debian... they might also apply to Ubuntu and address Francesco's issues. >> >> Thanks. >> >> -Philip |
|
From: chas w. - C. <ch...@cm...> - 2011-01-24 16:24:38
|
i created a new branch V2_5_3 and integrated the openwrt. if you could take a quick look when you have time. On Sat, 22 Jan 2011 12:02:37 -0800 Philip Prindeville <phi...@re...> wrote: > I was updating OpenWRT to use 2.5.2, and saw these patches. > > https://dev.openwrt.org/browser/trunk/package/linux-atm/patches > > All of the first patch applies... > > The second patch seems to disable linking with Flex. > > Can we make flex an autoconf option, i.e. --disable-flex ? > > The first set of patches affect Debian... they might also apply to Ubuntu and address Francesco's issues. > > Thanks. > > -Philip > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Linux-atm-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-atm-general > |
|
From: Chas W. (CONTRACTOR) <ch...@cm...> - 2011-01-23 03:44:46
|
In message <4D3...@re...>,Philip Prindeville writes: >All of the first patch applies... those changes seem pretty harmless. the int/socklen_t has been an issue forever. int should be the same size as socklen_t but if it isnt bad things will happen. >The second patch seems to disable linking with Flex. >Can we make flex an autoconf option, i.e. --disable-flex ? we shouldnt be linking with -lfl unless we are actually using flex. if we dont need it, we shouldnt link it. |
|
From: Philip P. <phi...@re...> - 2011-01-22 20:02:52
|
I was updating OpenWRT to use 2.5.2, and saw these patches. https://dev.openwrt.org/browser/trunk/package/linux-atm/patches All of the first patch applies... The second patch seems to disable linking with Flex. Can we make flex an autoconf option, i.e. --disable-flex ? The first set of patches affect Debian... they might also apply to Ubuntu and address Francesco's issues. Thanks. -Philip |
|
From: chas w. - C. <ch...@cm...> - 2011-01-21 15:29:08
|
you only need atmarpd for clip interfaces. you shouldnt need to run it. On Fri, 21 Jan 2011 11:32:13 +0000 Maestrelli Francesco <fra...@aa...> wrote: > In addition, when I run atmarpd (atmarpd -b) I get the following error: > > atmarpd:IO: ioctl ATMARPD_CTRL: Address already in use > Fatal error - Terminating > > > Francesco Maestrelli > ------------------------------------ > fra...@aa... > > ________________________________________ > From: Maestrelli Francesco [fra...@aa...] > Sent: 21 January 2011 12:20 > To: lin...@li... > Subject: [Linux-ATM-General] atm-tools and Ubuntu 10.10 > > I forgot to add as a CC to my answer the whole mailing list. Sorry for that and for sending again this message. > > Little description: > > I'm trying to configure an ATM connection between a computer I'm setting up and a DSLAM (Nokia D50, former Eksos B20) that will be connected over ADSL to an ADSL modem (M10 ADSL modem). This should simulate the standard conficuration an ISP could use to provide ADSL services to its customers. > > The computer I'm setting up should act as a switch or router and forward the requests coming from the ADSL connection (that the client computer connected to the ADSL modem will send) to the default gateway of the network I'm connected to. To do this the computer also have an ethernet card connected to the local network. > > Problem: > > The computer I'm setting up is running ubuntu 10.10 (kernel 2.6.35-24-generic), 512MB RAM, AMD Athlon Processor 1,4 Ghz. I was looking for information on the net to set up this environment, but i couldn't find much. > I'm actually following this: http://www.linuxjournal.com/article/3005 even if it's a quite old article. > > When I start atmsigd or ilmid the computer suddenly stop responding. > > Since I need to create a connection between this computer and the DSLAM and from there to the modem i think I'll need to setup a PVC thus I don't think I'll need those daemon.. right? What could be the reason they freeze anyway? > > Leaving aside these two I did the following: > > * I created the ATM device name: atmarp -c atm0 > > and from ifconfig -a i see the following: > > atm0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > [NO FLAGS] MTU:9180 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:100 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > (Isn't it weird that HWaddr is all zeros?) > > > * I configured the interface : ifconfig atm0 10.38.100.254 netmask 255.255.255.0 mtu 9180 > > * I added a route for the ATM subnet : route add -net 10.38.100.0 netmask 255.255.255.0 atm0 > > *Now I tried to setup the PVC: atmarp -s 10.38.100.101 0.0.101 (VPI:0 VCI:101) > > now I'm not totally sure about this command, but as I said I can't find much documentation on how do do this. > At this point the pc freezes again. > > > Probably It's my bad that I'm not understanding something. Any help would be precious. Thanks in advance. > > > BR, > > Francesco Maestrelli > ------------------------------------ > fra...@aa... > > ________________________________________ > From: chas williams - CONTRACTOR [ch...@cm...] > Sent: 20 January 2011 17:10 > To: Maestrelli Francesco > Cc: lin...@li... > Subject: Re: [Linux-ATM-General] atm-tools and Ubuntu 10.10 > > nothing that i know about specifically. what is your hardware and what > are commands are you running? > > On Thu, 20 Jan 2011 11:03:59 +0000 > Maestrelli Francesco <fra...@aa...> wrote: > > > Are there know issues with the atm daemons and Ubuntu 10.10? When I l start them following instructions in here http://www.linuxjournal.com/article/3005 the machine freezes. > > > > Thanks > > > > Francesco > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Linux-atm-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-atm-general > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Linux-atm-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-atm-general > |
|
From: chas w. - C. <ch...@cm...> - 2011-01-21 15:28:01
|
On Fri, 21 Jan 2011 10:20:25 +0000 Maestrelli Francesco <fra...@aa...> wrote: > I forgot to add as a CC to my answer the whole mailing list. Sorry for that and for sending again this message. > > Little description: > > I'm trying to configure an ATM connection between a computer I'm setting up and a DSLAM (Nokia D50, former Eksos B20) that will be connected over ADSL to an ADSL modem (M10 ADSL modem). This should simulate the standard conficuration an ISP could use to provide ADSL services to its customers. > > The computer I'm setting up should act as a switch or router and forward the requests coming from the ADSL connection (that the client computer connected to the ADSL modem will send) to the default gateway of the network I'm connected to. To do this the computer also have an ethernet card connected to the local network. > > Problem: > > The computer I'm setting up is running ubuntu 10.10 (kernel 2.6.35-24-generic), 512MB RAM, AMD Athlon Processor 1,4 Ghz. I was looking for information on the net to set up this environment, but i couldn't find much. > I'm actually following this: http://www.linuxjournal.com/article/3005 even if it's a quite old article. > > When I start atmsigd or ilmid the computer suddenly stop responding. if you dont start X windows and turn off kernel logging so that it appears on the screen (service syslog stop i think and klogd -c 6 as well on some systems) do you see any oops? sometimes it is helpful if you have a serial console setup to catch any errors on another computer. however, given your config, you need a pvc, so you really dont need ilmid or atmsigd. you only need to run those for pvc's. > Since I need to create a connection between this computer and the DSLAM and from there to the modem i think I'll need to setup a PVC thus I don't think I'll need those daemon.. right? What could be the reason they freeze anyway? as i recall from your other message to me, you are using a zeitnet card. this is the zatm driver which should work but i havent heard of any reports of it working either in quite a while. i dont happen to have a zeinet on hand to test the driver in any way. > > Leaving aside these two I did the following: > > * I created the ATM device name: atmarp -c atm0 > > and from ifconfig -a i see the following: > > atm0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > [NO FLAGS] MTU:9180 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:100 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > (Isn't it weird that HWaddr is all zeros?) > > > * I configured the interface : ifconfig atm0 10.38.100.254 netmask 255.255.255.0 mtu 9180 > > * I added a route for the ATM subnet : route add -net 10.38.100.0 netmask 255.255.255.0 atm0 > > *Now I tried to setup the PVC: atmarp -s 10.38.100.101 0.0.101 (VPI:0 VCI:101) > > now I'm not totally sure about this command, but as I said I can't find much documentation on how do do this. > At this point the pc freezes again. > > > Probably It's my bad that I'm not understanding something. Any help would be precious. Thanks in advance. you probably want br2684ctl instead. this creates a single ip interface bound to a pvc. there is a man page for it here: http://linux.die.net/man/8/br2684ctl > > BR, > > Francesco Maestrelli > ------------------------------------ > fra...@aa... > > ________________________________________ > From: chas williams - CONTRACTOR [ch...@cm...] > Sent: 20 January 2011 17:10 > To: Maestrelli Francesco > Cc: lin...@li... > Subject: Re: [Linux-ATM-General] atm-tools and Ubuntu 10.10 > > nothing that i know about specifically. what is your hardware and what > are commands are you running? > > On Thu, 20 Jan 2011 11:03:59 +0000 > Maestrelli Francesco <fra...@aa...> wrote: > > > Are there know issues with the atm daemons and Ubuntu 10.10? When I l start them following instructions in here http://www.linuxjournal.com/article/3005 the machine freezes. > > > > Thanks > > > > Francesco > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Linux-atm-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-atm-general > |
|
From: Maestrelli F. <fra...@aa...> - 2011-01-21 11:33:32
|
In addition, when I run atmarpd (atmarpd -b) I get the following error: atmarpd:IO: ioctl ATMARPD_CTRL: Address already in use Fatal error - Terminating Francesco Maestrelli ------------------------------------ fra...@aa... ________________________________________ From: Maestrelli Francesco [fra...@aa...] Sent: 21 January 2011 12:20 To: lin...@li... Subject: [Linux-ATM-General] atm-tools and Ubuntu 10.10 I forgot to add as a CC to my answer the whole mailing list. Sorry for that and for sending again this message. Little description: I'm trying to configure an ATM connection between a computer I'm setting up and a DSLAM (Nokia D50, former Eksos B20) that will be connected over ADSL to an ADSL modem (M10 ADSL modem). This should simulate the standard conficuration an ISP could use to provide ADSL services to its customers. The computer I'm setting up should act as a switch or router and forward the requests coming from the ADSL connection (that the client computer connected to the ADSL modem will send) to the default gateway of the network I'm connected to. To do this the computer also have an ethernet card connected to the local network. Problem: The computer I'm setting up is running ubuntu 10.10 (kernel 2.6.35-24-generic), 512MB RAM, AMD Athlon Processor 1,4 Ghz. I was looking for information on the net to set up this environment, but i couldn't find much. I'm actually following this: http://www.linuxjournal.com/article/3005 even if it's a quite old article. When I start atmsigd or ilmid the computer suddenly stop responding. Since I need to create a connection between this computer and the DSLAM and from there to the modem i think I'll need to setup a PVC thus I don't think I'll need those daemon.. right? What could be the reason they freeze anyway? Leaving aside these two I did the following: * I created the ATM device name: atmarp -c atm0 and from ifconfig -a i see the following: atm0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 [NO FLAGS] MTU:9180 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:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) (Isn't it weird that HWaddr is all zeros?) * I configured the interface : ifconfig atm0 10.38.100.254 netmask 255.255.255.0 mtu 9180 * I added a route for the ATM subnet : route add -net 10.38.100.0 netmask 255.255.255.0 atm0 *Now I tried to setup the PVC: atmarp -s 10.38.100.101 0.0.101 (VPI:0 VCI:101) now I'm not totally sure about this command, but as I said I can't find much documentation on how do do this. At this point the pc freezes again. Probably It's my bad that I'm not understanding something. Any help would be precious. Thanks in advance. BR, Francesco Maestrelli ------------------------------------ fra...@aa... ________________________________________ From: chas williams - CONTRACTOR [ch...@cm...] Sent: 20 January 2011 17:10 To: Maestrelli Francesco Cc: lin...@li... Subject: Re: [Linux-ATM-General] atm-tools and Ubuntu 10.10 nothing that i know about specifically. what is your hardware and what are commands are you running? On Thu, 20 Jan 2011 11:03:59 +0000 Maestrelli Francesco <fra...@aa...> wrote: > Are there know issues with the atm daemons and Ubuntu 10.10? When I l start them following instructions in here http://www.linuxjournal.com/article/3005 the machine freezes. > > Thanks > > Francesco ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Linux-atm-general mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linux-atm-general |
|
From: Maestrelli F. <fra...@aa...> - 2011-01-21 10:20:33
|
I forgot to add as a CC to my answer the whole mailing list. Sorry for that and for sending again this message. Little description: I'm trying to configure an ATM connection between a computer I'm setting up and a DSLAM (Nokia D50, former Eksos B20) that will be connected over ADSL to an ADSL modem (M10 ADSL modem). This should simulate the standard conficuration an ISP could use to provide ADSL services to its customers. The computer I'm setting up should act as a switch or router and forward the requests coming from the ADSL connection (that the client computer connected to the ADSL modem will send) to the default gateway of the network I'm connected to. To do this the computer also have an ethernet card connected to the local network. Problem: The computer I'm setting up is running ubuntu 10.10 (kernel 2.6.35-24-generic), 512MB RAM, AMD Athlon Processor 1,4 Ghz. I was looking for information on the net to set up this environment, but i couldn't find much. I'm actually following this: http://www.linuxjournal.com/article/3005 even if it's a quite old article. When I start atmsigd or ilmid the computer suddenly stop responding. Since I need to create a connection between this computer and the DSLAM and from there to the modem i think I'll need to setup a PVC thus I don't think I'll need those daemon.. right? What could be the reason they freeze anyway? Leaving aside these two I did the following: * I created the ATM device name: atmarp -c atm0 and from ifconfig -a i see the following: atm0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 [NO FLAGS] MTU:9180 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:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) (Isn't it weird that HWaddr is all zeros?) * I configured the interface : ifconfig atm0 10.38.100.254 netmask 255.255.255.0 mtu 9180 * I added a route for the ATM subnet : route add -net 10.38.100.0 netmask 255.255.255.0 atm0 *Now I tried to setup the PVC: atmarp -s 10.38.100.101 0.0.101 (VPI:0 VCI:101) now I'm not totally sure about this command, but as I said I can't find much documentation on how do do this. At this point the pc freezes again. Probably It's my bad that I'm not understanding something. Any help would be precious. Thanks in advance. BR, Francesco Maestrelli ------------------------------------ fra...@aa... ________________________________________ From: chas williams - CONTRACTOR [ch...@cm...] Sent: 20 January 2011 17:10 To: Maestrelli Francesco Cc: lin...@li... Subject: Re: [Linux-ATM-General] atm-tools and Ubuntu 10.10 nothing that i know about specifically. what is your hardware and what are commands are you running? On Thu, 20 Jan 2011 11:03:59 +0000 Maestrelli Francesco <fra...@aa...> wrote: > Are there know issues with the atm daemons and Ubuntu 10.10? When I l start them following instructions in here http://www.linuxjournal.com/article/3005 the machine freezes. > > Thanks > > Francesco |
34 messages has been excluded from this view by a project administrator.
