**** BEGIN LOGGING AT Thu Nov 12 02:59:57 2009 Nov 12 12:00:31 grmblfx - anyone here got working eth1 on openrd client? Nov 12 12:01:02 both stock debian & latest head from linux-2.6-openrd (i.e. _with_ the 18 -> 24 change for phys) Nov 12 12:01:16 only give me a link, but no packets on kernel level ... Nov 12 12:02:02 I also happily take hints on what/where to debug that - Nov 12 12:02:12 * thorsten looks at rabeeh ;) Nov 12 12:55:06 thorsten: with the original software with which it came, it worked for me Nov 12 12:55:30 haven't really tried eth1 with a newer kernel Nov 12 12:55:38 eFfeM: 'k, that's at least something to start with ;) Nov 12 12:56:51 thorsten: i had configured the thing as router once Nov 12 12:58:08 wiht a very simple routing script and with a 2.6.22.18 kernel with netfilter/iptables in it and a very simple routing script Nov 12 12:58:28 if you want to do routing don't forget this: Nov 12 12:58:28 echo 1 > /proc/sys/net/ipv4/ip_forward # Enables packet forwarding by kernel Nov 12 12:58:42 need to go shopping, back later **** BEGIN LOGGING AT Thu Nov 12 14:27:36 2009 Nov 12 15:31:09 thorsten: stupid question but are you sure you're using the machine id? Nov 12 15:31:27 thorsten: I had a report from someone who used the SheevaPlug id and hence eth1 wasn't working Nov 12 15:32:20 tbm: at first I didn't, you're right - but now I have arcNumber=2361, with the same results Nov 12 15:33:03 then I don't know Nov 12 15:33:37 tbm: it's _kind of_ working, so ethtool does something sensible, link up/down notifications are coming - but no packets ... Nov 12 18:16:19 armin76: both ethernets work fine on my openrd (factory defaults) Nov 12 18:16:33 armin76: joan is here by me Nov 12 18:16:59 armin76: btw, i have it at the office if you want to see it tomorrow **** ENDING LOGGING AT Fri Nov 13 02:59:57 2009