Am Sonntag, 13. Februar 2011, um 13:25:10 schrieb superchode .: > greetings, all. former leaf user (bering 2.x), back in the day. looking to > get it going again since consumer grade routers are universally terrible. > > > anyway. fired up the latest 4.0 beta2 package from the site. > > > minimal changes, just got the network card going and the internal network > online (dhcpcd). external connection (eth0) left as default, since it's > suitable for my connection (ziggo cable in the netherlands). > > > my only real concern was that the modem would bind to the old router's MAC, > so i called ziggo and they assured me that they don't fix to a specific > MAC, and it's just a matter of getting the modem to pick up the new MAC. > so, i spoofed the eth0 mac of my bering setup in the old d-link router, > which worked fine (so, presumably, the modem is now looking for a > connection with the bering router's MAC address, perfect). the d-link > router is working just fine with the bering router's MAC... so i assume no > issues on the modem/ISP side. > > > trouble is, i'm not getting a proper IP from the modem with the bering > router and, as a result, no connectivity. there isn't really any > configuration for a dynamic dhcp cable connection, so it's difficult to > see what needs to be done. > > > here's some output that i hope someone will find useful: > > > Reconfiguring network interfaces: eth0: sending signal 1 to pid 6066 > eth0: waiting for pid 6066 to exit > eth0: dhcpcd 4.0.15 starting > eth0: broadcasting for a lease > eth0: offered 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: acknowledged 94.210.26.12 from 212.54.38.82 > eth0: checking 94.210.26.12 is available on attached networks > eth0: leased 94.210.26.12 for 604312 seconds > /libexec/dhcpcd-run-hooks: /libexec/dhcpcd-hooks/10-mtu: line 5: ifconfig: > not found done. > > > > > > and some eth0 down/up results: (it's a four-port NIC, only eth0 and eth1 > are in use). > > > firewall# ifdown eth0 > eth0: sending signal 1 to pid 11147 > eth0: waiting for pid 11147 to exit > firewall# ifup eth0 > eth0: dhcpcd 4.0.15 starting > eth0: broadcasting for a lease > eth0: offered 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: ignoring offer of 94.210.26.12 from 212.54.38.82 > eth0: acknowledged 94.210.26.12 from 212.54.38.82 > eth0: checking 94.210.26.12 is available on attached networks > eth0: leased 94.210.26.12 for 3600 seconds > /libexec/dhcpcd-run-hooks: /libexec/dhcpcd-hooks/10-mtu: line 5: ifconfig: > not found firewall
Another package that uses the somewhat outdated ifconfig utility... You may try pump until a solution is found. btw: what kernel do you use? kp ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
