1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tomato 1.19.8815 Mod.

Discussion in 'Tomato Firmware' started by Victek, May 19, 2008.

Thread Status:
Not open for further replies.
  1. Victek

    Victek Network Guru Member

    Yes, it works, but the problem was related to Port Triggering not to Port Forwarding. The port triggering problem was linked to Speedmod 8500, now it has been updated to Speedmod 8502 in the 8825 release. Please wait some minutes and you can download last release from my page with all the related problem in the last post solved or you can download 8825 release, as you like.
     
  2. Kiwi8

    Kiwi8 LI Guru Member

    Yeah, but please do not use the rapidshare links otherwise the creation of alternative download links is inevitable. :redface:
     
  3. cHarOn

    cHarOn Network Guru Member

    ah ok that are good news :) thx for the mod really great one now i only need openvpn inside and i´m happy hahaha
     
  4. Toink

    Toink Network Guru Member

    I personally don't mind rapidshare links. It's Megaupload link that I am weary about because it forces you to install a downloader that has malware.

    MiHD.net actually works you just have to make sure that the webpage is completely loaded before you click on "request ticket".
     
  5. Victek

    Victek Network Guru Member

  6. zoz2000

    zoz2000 Addicted to LI Member

    Hi Victek!
    Could you write release notes for your firmware please?
    I see what's new in 8820 but in 8825 or 8835? I can't see..
    Maybe you can put release notes into the package..
    Thank you!
     
  7. Toink

    Toink Network Guru Member

    From Victek's site:

    Seperated: English/Spanish changelogs.
     
  8. Kiwi8

    Kiwi8 LI Guru Member

    Slowshare is ok as long as it starts. :biggrin:

    Rapidshare doesn't even allow the download to start! :biggrin:
     
  9. zoz2000

    zoz2000 Addicted to LI Member

    Toink: I saw his site and all of the changes..but i would like to know only the last changes..i have the ver.8820..what's different from 8825 and 8835? Because if changes not important i won't change..
    This is why i suggested release notes..
     
  10. cHarOn

    cHarOn Network Guru Member

    yes i cant read spain also :) is a little bit hard and now i flashed 8825 and 8835 is there now omg you are faster then i can flash hahaha
     
  11. Toink

    Toink Network Guru Member


    Port triggering is not working in v8820. It was fixed in v8825.

    DNS typo corrected in v8835.

    That's all I know of. :)
     
  12. Victek

    Victek Network Guru Member

    Changelog is build into the file package with all the changes from previous releases from now on. :eek:
     
  13. kameleon

    kameleon LI Guru Member

    Victek,

    I would be willing to host the files on my webhost if you would like. It would be a direct download, no waiting for download ticket stuff or anything. I have plenty of bandwidth to go around... a few TB to be exact. Let me know if you are interested and I can get it setup. My little way of giving back to the community.

    Also, I would like to try out your mod on my WRT54GS V1.1 router here soon. Wonder how hard it would be to merge the VPN stuff that roadkill does with this?
     
  14. zoz2000

    zoz2000 Addicted to LI Member

    Thank you Victek!
    Now all clear:)
     
  15. TexasFlood

    TexasFlood Network Guru Member

    Thanks, loaded up 1.19.8835, without resetting nvram, and the DNS page saves fine now.
     
  16. Kiwi8

    Kiwi8 LI Guru Member

    Haha, downloading from your website is really slow... :biggrin:
    But at least it finished. :biggrin:
     
  17. jsmiddleton4

    jsmiddleton4 Network Guru Member

    8835 getting dhcp/dns now from my cable modem. I did do full reset however, as last night, so I could not tell anyone if it will work without one. Just getting settings back in place now. Seems to be SNAPPY.....
     
  18. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Close but no cigars. Still dropping dns/ip/gateway information from cable modem. 8835 sits there saying "Renewing...." Worked a few times but then 8835 lost the information about who/what it was connected to. Something is not right with this piece of 8835. Again don't know what isn't right. Could be busybox, who knows? But its not right and not stable when I suddenly can't get online and its due to the router being lost in space.....

    Back to 8820 and the gateway/ip/dns cable modem stuff pops right up and is in place.

    Jim

    Edit: Since it appeared to be stable while I was doing the detailed config I went ahead and upgraded my wds slave. I just looked at it as I was going to go back to 8820 on it. Even though DCHP server is off and the dns/ip/gateway is hardcoded, it is the wds slave, ITS saying "Renewing..." when it used to say nothing, those fields were blank due to dhcp/hardcoding. So something in the section of the firmware that deals with this piece needs a little loving.....

    Not complaining by the way. Just reporting.
     
  19. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Have same experience with 8825. IP/DNS/Gateway information drops, can't be found, etc.

    However with 8820, no problems.

    Buffalo HP54G and Linksys WRT54G Version 2.0. Same experience on both routers.
     
  20. Victek

    Victek Network Guru Member

    Hi, do you have a cable connection I suppose? Please unpick "Reduce packet size in DHCP/DNS menu", is not needed if you ticked already. It will be nice to know your service provider since I did not get any complaint about this behaviour from the spanish cable provider. If the problem continues I can send to you a very old version of dhcp that it's the original used in the 1.19 official release. Thanks for the feedback. :biggrin: I really appreciate it.

    If I understood well you have the same issue in 8820/8825/8830 and 8835, it's correct? Did you tryed the 8815 release from my web site?
     
  21. Kiwi8

    Kiwi8 LI Guru Member

    Hmmm... I seem to get a momentary downtime too with regards to the WAN connection, although it went up soon after. This meant that the uptime got resetted.

    Same as u... it doesn't happen with the 8820 version, but occurs in the following versions.
     
  22. Victek

    Victek Network Guru Member

    As you checked (for sure you noticed that) the renewal of WAN DHCP is the quickest you have ever seen since the first Tomato appeared (you get a new IP in less than 1 sec). Sometimes this behaviour occur when you "play" with renewal/disconnect button (it remains in renewing ...). I can set up the following:
    _ Let at it's and please don't play connect/disconnect :)
    _ Insert a delay to avoid this message (eve you see the renewing message your IP is renewed internally and you have Internet access)
    _ Go to the official Tomato method (backwards to BusyBox 1.2.2) eliminate the IP/MAC limiter (it uses the BusyBox 1.10.2) and have a light Tomato with additional themes and function but not IP/MAC limiter.

    Your choice? :)

    Edit.. Interesting what you wrote.. 8820 ok.. I have to see, Thanks
     
  23. TexasFlood

    TexasFlood Network Guru Member

    Just noticed that the busybox command line tab completion isn't turned on in these builds. I know it's silly but I tend to use that a lot. Please consider enabling it in future builds?

    Thanks
     
  24. Victek

    Victek Network Guru Member

    No problem Texasflood, will be in next release, written in my TODO:biggrin:

    BTW, BusyBox 1.10.3 (stable) is out
     
  25. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Victek,

    8820 works perfectly with the dhcp/ip/dns/gateway information being handed to it from my Motorola modem. Also seemed to work fine with first couple of reboots/loads/etc. for both 8825 and 8830. However after configuring several items, wds, static dhcp, the arp assigned addresses, etc., then both 8825 and 8830 quit picking up/registering the information from the modem. When I go back to 8820, reconfig, etc., it continues to work perfectly.

    Something is different between firmwares 8820 and 8825-8830 regarding this "piece" of the firmware. I know, I should be a rocket scientist.... :)

    But something is different and setting back to defaults, I used a 30 second full reset by the way so it was fully reset, does not seem to make any difference.

    I was hoping with 8830 getting the dhcp/ip/gateway from the router on the first setup/reboot that it was fixed. But not so.

    Jim

    Edit: I didn't have the dhcp/ip/gateway after hitting play by the way. May have a problem with that in this firmware but that's not how I ran into this "bug". It was in the normal reboot when setting the firmware up that when it came "up", no dns/ip/gateway from the router could be found....
     
  26. TexasFlood

    TexasFlood Network Guru Member

    jsmiddleton4, trying to think of the differences between your setup and mine as everything is OK here. I have a Motorola Surfboard w/ Comcast, set up WDS and static dhcp. I haven't set up arp assigned addresses as of yet. If you can summarize what kinda config you have there or anything else unique, time permitting I can try to reproduce the issue here.
     
  27. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Basically the same although its Cox in terms of cable piece.

    3 routers. 1, main one, dhcp server, wds+ap, in it is assigned dhcp for static ip's, and the arp area that Victek's tweak adds which has all static IP's as well from the static IP section. This is as before and works with 8820 by the way. Although all added manually after reset.

    Second router is wds+ap as well. Its in front room/av room and has Denon receiver, Wii, xbox connected. Nothing fancy in it as its just a dumb box of rocks. Wanted to do WEB/WET with it but ran into problems with mac/ip's being duplicated from devices attached to in showing up in main router so stayed with WDS. The slave router is configured correctly as the non-dhcp slave, no dhcp, wan port off, etc. Again works fine with regular Tomato or 8820.

    Third router is actually just an AP in back of house around where my genetic offspring use their laptops to ROFL as they see fit. Its hardwired of course to main router. Have a little script in it so its a 5 port AP. As with the wds slave, everything is off in it save the wireless, lan ports and depending on my mood sometimes I'll run stp. Only the main router is config as gateway, others are routers.

    I really don't want to walk back through all the manual setup stuff again as it is time consuming. Did seem to work as noted with first boots but there was really nothing fancy in the config yet.

    Edit: I did try unchecking ARP thing, saving, rebooting, to see if turning off ARP IP thing mattered. Didn't. Tried just Gateway, no wds, etc., didn't matter.

    While the other routers could be having some impact it really seems like its just something between the main router and the cable modem not picking up the information from the modem or 8830 is picking it up at some place/point in its initialization but then isn't handing that information up the food chain to where it needs to be, something....
     
  28. Victek

    Victek Network Guru Member

    jsmiddleton4, try last beta 8840, it uses BB 1.10.3, you can find as usual in my slowshare web site or alternate link. Please feedback.
     
  29. jsmiddleton4

    jsmiddleton4 Network Guru Member

    victek....

    d/l now. I don't mind the speed of your web site. The freaky multi-faced troll gives me nightmares though.
     
  30. Fedora_Guy

    Fedora_Guy Addicted to LI Member

    A further suggestion :) As much as I like your website and have been keeping a look out on this thread... It would be great if you would kindly take time to implement some kind of "news letter" or "alert email" service so that all your fans can know as soon as a new release is made :biggrin:
     
  31. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Wish I could say it works. Didn't even get past the first initial install and boot and have the renewing and no ip/dns/gateway issue.

    Wish I could be more helpful but it just isn't working whereas 8820 is fine.

    Edit: Also I do NOT have Internet access. Its not just cosmetic where the "Renewing..." thing is showing up. The router does not have any connection to the modem.
     
  32. Victek

    Victek Network Guru Member

    :cool::cool:strange ... Thanks
     
  33. jsmiddleton4

    jsmiddleton4 Network Guru Member

    What is in 8820 that is not in 8825/8830/8840? Or what is in 8825/8830/8840 that wasn't in 8820? Cause for me 8820 is fine. All versions after 8820 have same symptom. Not picking up dns/ip/gateway information from the cable modem.
     
  34. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Just dawned on me that I didn't look at nor cut and paste the log with the problematic firmware. If it would possibly help would be glad to run 8840 again and check the logs. Don't know why I didn't even think about it.


    Edit: Only other tweaking I've done is this:

    ______________________________________________________
    No problem. BTW there is a hidden setting in Tomato 1.18 and 1.19, that allows you to switch the QOS qdiscs from SFQ to PFIFO.

    #nvram set qos_pfifo=1
    #nvram commit
    _______________________________________________________

    I guess anything is possible but don't see how that would impact ip/dns/gateway from the cable modem and again that tweak works fine in 8820.
     
  35. TexasFlood

    TexasFlood Network Guru Member

    Might not fix jsmiddleton4s WAN but it's got tab file completion... Yay! Thanks...
     
  36. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Put 8820 on, which works, pulled "All" log off. Printed it. Put 8840 on, which doesn't work for WAN, pulled "All" log off. Compared. They are of course not the same. Here is where they are different and the first line is from the working firmware, second line from the non-working one.

    Any reference to BusyBox is of course different. Working one is 1.10.2, non working is 1.10.3.

    But the line/info on the Broadcom modifications is different.

    Working firmware:
    Dec 31 17:00:05 ? user.warn kernel: Linux version 2.4.20 (root@linux-xux1) (gcc version 3.2.3 with Broadcom modifications) #64 Tue May 20 15:27:06 CEST 2008

    Non-working firmware:
    Dec 31 17:00:06 ? user.warn kernel: Linux version 2.4.20 (root@Servidor-Linux) (gcc version 3.2.3 with Broadcom modifications) #17 Sat Jun 7 00:56:17 CEST 2008

    Then this line in the working firmware:
    Dec 31 17:00:05 ? user.info kernel: vlan1: add 01:00:5e:00:00:01 mcast address to master interface

    Is completely MISSING in the non-working firmware.

    Then this in the working firmware:
    Dec 31 17:00:05 ? user.warn kernel: tomato_ct.c [May 2 2008 22:10:38]

    Is this in the non-working one:
    Dec 31 17:00:06 ? user.warn kernel: tomato_ct.c [Jun 2 2008 13:17:52]

    In the working firmware the references, whatever it is, in the dnsmasq entries for which there are several are [117] as here:
    Dec 31 17:00:08 ? daemon.info dnsmasq[117]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP

    In the non-working firmware those dnsmasq references are [101] as in here:
    Dec 31 17:00:08 ? daemon.info dnsmasq[101]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP

    I'm not a programmer and will make a wild guess. These reference numbers really don't mean much. The compile dates being different on the tomato.c thing, probably no biggy.

    The different broadcom driver COULD be a problem.

    But, MY money is on the completely missing line in the non-working firmware.... As that line looks to me like what is NOT happening. In the working firmware the information is being broadcast to the router. In the non-working firmware it is not. So missing the mcast address to the master interface, (sorta sounds like what my daughters do when they "forgot" to ask permission), that appears to be what isn't happening in the non-working one.

    Nothing is getting broadcast regarding dns/ip/gateway of the modem into the router.

    Back to the baseball game.

    And if I try to take down the router one more time to play with firmware so that my family loses its internet access, it won't matter much as to what the issue is with the firmware, about all I will be able to use with my broken fingers is my mouse....



    Jim
     
  37. TexasFlood

    TexasFlood Network Guru Member

    Maybe you could sniff the traffic and see what's going on. I have an old hub I keep specifically for that purpose. Just plug it between the devices in question with a PC running Wireshark and capture/analyze. If you don't have the hub, hmm, wonder if there is a way to set up iptables rules to copy all traffic to a single port and effectively create a spanning port that one could monitor from?
     
  38. TexasFlood

    TexasFlood Network Guru Member

    FYI, checked my log, from the first 8840 boot, and getting a WAN IP & did find that line:

    Dec 31 17:00:06 wrt54gv2 user.info kernel: :00:5e:00:00:01 mcast address to master interface
     
  39. jsmiddleton4

    jsmiddleton4 Network Guru Member

    So different broadcom driver and the Buffalo HP54G not playing well togther and not "coughing up" that line on mine where as its working on yours being Linksys? And I have no idea WHY that line is missing. Just saying its that missing line is the symptom. Finding out why is the fix.

    Edit: Can that line be added manually after I install the firmware to trouble shoot it? Not sure what the command line structure would possibly be.

    And yours not exactly the same.... thinking difference between Buffalo and Linksys?
     
  40. TexasFlood

    TexasFlood Network Guru Member

    Aren't these the lines that indicate the driver versions?

    Dec 31 17:00:06 wrt54gv2 user.warn kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.38.0
    Dec 31 17:00:06 wrt54gv2 user.warn kernel: eth1: Broadcom BCM4320 802.11 Wireless Controller 3.90.38.0
     
  41. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Not sure what i would capture Texas. Nothing works with the new firmware as I can't get on-line so there would be nothing to capture.
     
  42. TexasFlood

    TexasFlood Network Guru Member

    I was thinking monitor between the cable modem and router WAN port, see what handshaking is or isn't going on. This would work with my hub method, maybe not a spanning port, which I don't even know is possible.
     
  43. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Probably and i could be using the wrong lingo. While it looks almost the same, something is different with the lines about Broadcom modification number and compile dates. I just looked at those lines in my current log and they are the same as yours.

    I'm just guessing but I am pretty sure that the "Why" that line is missing from the non-working version on my buffalo router, that is the cause. Someone more technically skilled in the "Why" piece can maybe figure it out.
     
  44. jsmiddleton4

    jsmiddleton4 Network Guru Member

    But to monitor what? If its not working, what's to monitor? Wouldn't even suggest it at this point to my family to let me try. They've been very patient.
     
  45. TexasFlood

    TexasFlood Network Guru Member

    I resemble that remark...
     
  46. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Isn't "Hey, I resemble that remark!"

    :)
     
  47. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Ok, so what is the command to enter that line manually? Can't be as simple as a nvram add missing line....

    Maybe it is?
     
  48. TexasFlood

    TexasFlood Network Guru Member

    Pass, out of my depth now. Hopefully someone with more expertise will chime in.
     
  49. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Just checked again on the up and running router and it actually has the entry 3 times. Hard to keep focused as Ripley is about to blow the alien out of the shuttle in her underwear for about the 100th time on cable TV.

    Dec 31 17:00:09 ? user.info kernel: vlan1: add 01:00:5e:00:00:09 mcast address to master interface
    Dec 31 17:00:10 ? user.info kernel: vlan1: del 01:00:5e:00:00:09 mcast address from master interface
    Jun 6 18:20:23 ? user.info kernel: vlan1: add 01:00:5e:00:00:09 mcast address to master interface

    No entries of this nature in the non-working firmware.

    Oh man, the alien just got blown out the hatch AGAIN. About to get fried.
     
  50. TexasFlood

    TexasFlood Network Guru Member

    FYI, found a couple of mentions of that MAC address. Seems like it is a specific multicast MAC/IP related to RIPv2 routing protocol.

    Cisco Cable Modem High-Speed WAN Interface Cards Configuration Guide

    Vendor Specific Type-Length-Values 42


    TLV 42
    Use TLV 42 to enable downstream routing protocols using multicast address such as RIPv2.

    To support DOCSIS configuration file-based enabling downstream routing protocols using multicast address such as RIPv2, your DOCSIS configuration file editor must support the inclusion of the Cisco vendor-specific TLV 42.

    The following example shows how to use TLV 42 in the configuration file. This information can be found in the vendor information specific field (VISF):

    00 (Multicast Mac Address) = 42 %hex 01 00 5e 00 00 09

    Note The value of TLV 42 is fixed for all routers.

    and

    Illustrated TCP/IP
    by Matthew G. Naugle
    Wiley Computer Publishing, John Wiley & Sons, Inc.

    Chapter 113 - Multicast Support
    A key improvement for the RIP protocol is the ability to use a multicast address for its
    packets and for its datagram IP header. The multicast address for RIPv2 is 224.0.0.9 with
    a MAC address of 01-00-5E-00-00-09. Of course, this must be mapped to an Ethernet
    multicast address (for more information on this, please refer to Part Six, BOOTP, DHCP,
    RSVP, and SNMP in this book, or RFC 1700).
    Multicast Support
    • RIPv2 uses the multicast address of 224.0.0.9 to multicast, does not broadcast
    its table.
    • MAC address of 01-00-5E-00-00-09.
    • Details of this conversion are covered in RFC 1700 and the multicast
    section of this book.
    • RIPv1 uses a broadcast address in both the IP header and the MAC header.
    • IGMP is not used for this multicast support.
     
  51. jsmiddleton4

    jsmiddleton4 Network Guru Member

    So something goofed with the RIPv1/v2 stuff causing the symptom?
     
  52. GhaladReam

    GhaladReam Network Guru Member

    I'm running 1.19.8840 on a Linksys WRT54GSv2, and I don't seem to be having the issue of not being able to connect to WAN... The router sees my cable modem just fine, and grabs IP, DNS, and Gateway server addresses. I was under the impression that the Buffalo units were the same internally as the Linksys units, which is why they also run Tomato... Odd that it's no co-operating.
     
  53. TexasFlood

    TexasFlood Network Guru Member

    Same here with my WRT54Gv2, working just fine.
     
  54. TexasFlood

    TexasFlood Network Guru Member

    I'm really not sure, just trying to gather information and see if something in the fog comes into focus, :-D
     
  55. jsmiddleton4

    jsmiddleton4 Network Guru Member

    And 8820 works so well too.
     
  56. jsmiddleton4

    jsmiddleton4 Network Guru Member

    ghald...

    Similiar yes but not the same.
     
  57. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Victek

    unpick "Reduce packet size in DHCP/DNS menu"

    Already is unchecked. If I check Reduced Packet Size, my Denon 3808 reciever has never been able to connect to Internet Radio, etc. Cable provider is Cox.

    I think I tried 8815, tried them all from your first mod on up the line. So while I can't remember specifically suing it, I'm fairly certain I did.
     
  58. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Reinstalled 8840 to continue to play. Family heading for bed. Banging on it and thinking out loud as previous posts. What looks like it isn't picking up fully and instead doing the renewing thing is the DNS information. The IP, Gateway, subnet are there, at least displayed. What's missing on the display/gui is the DNS numbers from the cable modem. I manually entered them and I can get on the web, using 8840 right now. But something isn't right that I have to use static. Cox is not static and while its working now, when they refresh my modem I could lose the connection.

    Tried Static DNS and let DHCP do the WAN. Still a no go. "Renewing...." displays, the DCHP information at least is displayed, the Static DNS numbers show, but I can not connect. Static for everything, it works fine.

    DHCP issue? How is the DHCP different than 8820? How can 8820 work so well and I'm hosed with 8840?

    Edit: Back to 8820. Don't want to mess with static, losing connection, re-entering static. There are some other posts, not a lot of them but a few, about "issues" with other folks renewing wan dhcp, udhcp, stuff like that. Wonder if its all related?
     
  59. Victek

    Victek Network Guru Member

    Well, TBH the 8820 dhcp was a dirty dhcp modified to launch the BusyBox 1.10.2. I has been working to aliviate the uggly work of the 8820 and 8840 is more efficient than 8820. Going back to 8820 it's a uggly solution that I would like to avoid.
    Now with BB 1.10.3 I observed a very good behaviour of the dhcp but as you're talking the problem persists... strange and pity cause I have not access to your ISP to know what's happening.
    One simply question, did you entered a unique name in Basic/Identification for the router?
    Please copy the line that shows you the udhcp in terminal mode after you type the ps command.

    Thanks for your feedback.
     
  60. jsmiddleton4

    jsmiddleton4 Network Guru Member

    I just hate it when my dhcp's get dirty....

    If you are asking me have I named each router, yes. Main router is named.....wait for it...... Main_router. Router in the entertainment center that is wds slave is named Entertainment_Center. Router that is AP in back of house is named Back_Room_Wireless_AP. Has always worked even with plain old Tomato and your mods as noted.

    You want me to go into terminal mode, type "ps" and tell you what it says?
     
  61. jsmiddleton4

    jsmiddleton4 Network Guru Member

    This is 8820 though. I can't use dhcp and 8840.... So I'm guessing you want me to install 8840 and do the same thing? I'm telling you I really oughta be a rocket scientist or a brain surgeon....

    /tmp/home/root # ps
    PID USER VSZ STAT COMMAND
    1 root 1720 S init noinitrd
    2 root 0 SW [keventd]
    3 root 0 RWN [ksoftirqd_CPU0]
    4 root 0 SW [kswapd]
    5 root 0 SW [bdflush]
    6 root 0 SW [kupdated]
    7 root 0 SW [mtdblockd]
    39 root 1700 S buttons
    82 root 1920 S telnetd -p 23
    85 root 1928 S syslogd -m 60 -L -s 50
    87 root 1912 S klogd
    92 root 1764 S nas /etc/nas.conf /var/run/nas.pid lan
    131 root 1936 S zebra -d -f /etc/zebra.conf
    144 root 2052 S ripd -d -f /etc/ripd.conf
    198 nobody 972 S dnsmasq
    201 root 1940 S crond -l 9
    215 root 1240 S rstats
    235 root 1644 S httpd
    437 root 1928 S udhcpc -i vlan1 -s dhcpc-event
    674 root 1948 S -sh
    676 root 1936 R ps
    /tmp/home/root #
     
  62. jsmiddleton4

    jsmiddleton4 Network Guru Member

    As in our thinking out loud wandering posts last night, the same glaring thing stands out here for the same reason which is a line is missing. Again not sure why as the "why" is probably the problem and the fix. Here is same information from 8840. Its missing the whole udhcpc line.

    /tmp/home/root # ps
    PID USER VSZ STAT COMMAND
    1 root 1768 S init noinitrd
    2 root 0 SW [keventd]
    3 root 0 RWN [ksoftirqd_CPU0]
    4 root 0 SW [kswapd]
    5 root 0 SW [bdflush]
    6 root 0 SW [kupdated]
    7 root 0 SW [mtdblockd]
    39 root 1748 S buttons
    82 root 2008 S telnetd -p 23
    84 root 2016 S syslogd -m 60 -L -s 50
    86 root 2000 S klogd
    87 root 1812 S nas /etc/nas.conf /var/run/nas.pid lan
    94 root 2020 S crond -l 9
    96 root 1744 S sched start
    97 root 1288 S rstats
    101 nobody 1012 S dnsmasq
    106 root 1692 S httpd
    107 root 1984 S zebra -d -f /etc/zebra.conf
    111 root 2100 S ripd -d -f /etc/ripd.conf
    126 root 2044 S -sh
    134 root 2024 R ps
    /tmp/home/root #
     
  63. jsmiddleton4

    jsmiddleton4 Network Guru Member

    I'll get back with you later. Now its time to wash the dog.....

    I want to run some of the other odd posts/issues past you IF we can today as well.
     
  64. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Back. But wife decided since I was doing the dog's bath, I could do our 4 cats. Typing slowly to avoid opening the deep flesh wounds....

    Edit: Sorry meant to ask if there is a way to manually add that missing line and see if that missing is the problem. As in adding it and if works, adding it and it makes no difference?
     
  65. jsmiddleton4

    jsmiddleton4 Network Guru Member

    I did a quick search on the udhcp thing and looks like issues with it and Tomato are not new. Not that this is the same thing but have seen other posts about similar issues.
     
  66. jsmiddleton4

    jsmiddleton4 Network Guru Member

    I went ahead and tried adding the missing line manually. It works in the sense I am on-line, have ip/gateway/dns etc. as I should.

    Here is what it how adding the command went in telenet. Not sure what the "vlan1 no such process" means. It works. So somehow this is progress?

    /tmp/home/root # udhcpc -i vlan1 -s dhcpc-event
    ### adapter index 5
    ### adapter hardware address 00:16:01:d2:7a:fd
    udhcpc (v1.10.3) started
    ### vfork'ing and execle'ing dhcpc-event
    ### entering raw listen mode
    ### opening raw socket on ifindex 5
    ### got raw socket fd 6
    ### bound to raw socket fd 6
    ### adding option 0x35
    ### adding option 0x3d
    ### adding option 0x3c
    ### adding option 0x39
    Sending discover...
    ### Waiting on select...
    ### Unrelated/bogus packet
    ### Waiting on select...
    ### Got valid DHCP packet
    ### adding option 0x35
    ### adding option 0x3d
    ### adding option 0x3c
    ### adding option 0x32
    ### adding option 0x36
    Sending select for 72.222.160.186...
    ### Waiting on select...
    ### Got valid DHCP packet
    Lease of 72.222.160.186 obtained, lease time 86400
    ### vfork'ing and execle'ing dhcpc-event
    vlan1: No such process
    ### entering none listen mode
    /tmp/home/root #


    Edit: Looks like the "no such process" is that there is no script to run the that -s points to.

    Edit: No, that's probably wrong. Looks like the stand alone command line may not be exactly right.
     
  67. Toink

    Toink Network Guru Member

    Hi, js!

    I'm not sure if you've posted it before. Since Victek's 8825-8840 mod is based on Rod's non-ND 8502, and 8820 is based on 8500, have you tried installing Rod's non-ND 8502 and check if it manifests the same issues you're having on 8825-8840?

    I personally don't have any issues (yet) on 8840. The only difference I could think of between your router and mine is that yours is a Buffalo. Even so, 8820 works on it. Mine did too, except port triggering.
     
  68. jsmiddleton4

    jsmiddleton4 Network Guru Member

    I think Victek has enough information now to take a look at the components. Its working now with adding the command line manually. Will see how it unfolds. I've installed and reinstalled and reconfigured enough.
     
  69. jsmiddleton4

    jsmiddleton4 Network Guru Member

    toink,

    I'm up as I'm waiting for a call from my daughter who is in India for the summer helping with an infant girl orphanage.

    Something about your post had to settle in a bit and now I have question. Maybe for Victek. If he changed the driver set/core that was in 8820 and put different core/set in 8825 on up, what's with the responses that require digging into 8840 and being unsure of what's happening with 8840? If 8820 works great, and it does, and 8840 doesn't, and it doesn't, and the core/set of drivers is different, well isn't that part of the answer? There are indeed issues with these nd non-nd drivers with Buffalo's. Advised to take notice of them on the Polar web site. It doesn't bug me, I'm confused is all. If this is changed between 8820 and on up, well that's a major change and don't we want to start looking at the most obvious thing first?

    With all the post, questions, etc., on 8840 not working on my Buffalo's, your post is the first mention of the change in the driver set. I guess as soon as I had an issue I would have liked to have heard about the nd to non-nd thing and consider that until that is worked out, maybe sticking with 8820 is a good idea.

    So is it the case that the driver sets were changed? ND for non-nd, or non-nd for nd?
     
  70. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Loaded 8502. Works like a charm. Quick, gets data from cable modem just fine.
     
  71. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Here is the result of ps command with a working 8502

    Tomato v1.19.8502


    BusyBox v1.2.2 (2008.04.25-09:18+0000) Built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    # ps
    PID Uid VmSize Stat Command
    1 root 536 S init noinitrd
    2 root SW [keventd]
    3 root SWN [ksoftirqd_CPU0]
    4 root SW [kswapd]
    5 root SW [bdflush]
    6 root SW [kupdated]
    7 root SW [mtdblockd]
    39 root 304 S buttons
    2070 root 332 S syslogd -m 60 -L -s 50
    2073 root 312 S klogd
    2074 root 508 S nas /etc/nas.conf /var/run/nas.pid lan
    2089 root 336 S rstats
    2094 root 368 S crond -l 9
    2136 nobody 640 S dnsmasq
    2174 root 580 S zebra -d -f /etc/zebra.conf
    2178 root 788 S ripd -d -f /etc/ripd.conf
    2283 root 360 S udhcpc -i vlan1 -s dhcpc-event -l br0
    2361 root 308 S httpd
    2363 root 292 S telnetd -p 23
    2365 root 440 S -sh
    2367 root 344 R ps
    #


    Edit: Did some quick reading again. Is the -l br0 thing what some folks have talked about that in udhcpc there is no -l option?
     
  72. Victek

    Victek Network Guru Member

    jsmiddleton4, thanks for your rocket scientist job :biggrin:, let's go step by step.

    dhcp and udhcp module.

    Difference between official Tomato and 8502 speedmod = nothing regarding these modules and BusyBox.
    Difference between official Tomato and Victek's 8820 = (Day vs. Night) BusyBox 1.10.2 and dhcp.c code (uggly implementation)
    Difference between official Tomato and Victek's 8840 = (Earth vs. Saturn) BusyBox 1.10.3 and dhcp.c code (clean implementation)

    8820 and 8840 works OK in around 57 router WRT54GL but is not working in ONE Buffalo (your) with ISP Cox ..

    This is the conclusion of my rocket scientist job :biggrin:, so, we have to wait until ONE WRT54GL shows this behaviour OR one colleague will have problems with Cox using ONE WRT54GL.

    Thanks to be the only problem, the score is 98% success .. let's see how I can get 100%. :biggrin:

    Here is my line in the ps screen with 8840, -l is not used in 8820/8840 dhcp.c, and yes, you're right, there is no option in BusyBox 1.10.2 & 1.10.3 for -l. This is why I use -H as Hostname instead of if_name (-l)

    Jon Zarate also talked me about these issues with BusyBox ...

    283 root 2016 S udhcpc -i vlan1 -s dhcpc-event -H router_dhcp.
     
  73. TexasFlood

    TexasFlood Network Guru Member

    FYI, output of ps command on a WRT54Gv2 working with 8840

    Tomato v1.19.8840

    BusyBox v1.10.3 (2008-06-07 00:54:10 CEST) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    /tmp/home/root # ps
    PID USER VSZ STAT COMMAND
    1 root 1768 S init noinitrd
    2 root 0 SW [keventd]
    3 root 0 SWN [ksoftirqd_CPU0]
    4 root 0 SW [kswapd]
    5 root 0 SW [bdflush]
    6 root 0 SW [kupdated]
    7 root 0 SW [mtdblockd]
    39 root 1744 S buttons
    85 root 2012 S syslogd -m 60 -L -s 50
    86 root 2008 S telnetd -p 23
    89 root 2000 S klogd
    90 root 1932 S nas /etc/nas.conf /var/run/nas.pid lan
    95 root 2028 S crond -l 9
    98 root 1288 S rstats
    106 root 1692 S httpd
    113 nobody 1144 S dnsmasq
    313 root 2016 S udhcpc -i vlan1 -s dhcpc-event -H wrt54gv2
    525 root 2044 S -sh
    529 root 2024 R ps
    /tmp/home/root #
     
  74. zoz2000

    zoz2000 Addicted to LI Member

    I have the version 8820 and i want to upgrade to 8840.
    Do I have to erease NVRAM in this case?
    Other thing Victek: You worked on a release that should have known traffic per Ip..what about this? Are you working on it?
    Thank you in anticipation!
     
  75. Victek

    Victek Network Guru Member

    zoz2000, no nvram erase is needed, you can run normally after update.

    Yes, IP traffic statistics is ready in hide beta release, I wait for the new official Tomato to be released and see what new surprises includes,
    Rome was built after some years, my mod has been released and updated in hours, so, I don't want to release new upgrade version with any problem.. it's under test. :biggrin:
     
  76. TexasFlood

    TexasFlood Network Guru Member

    jsmiddleton4

    From Victeks last post, seems that he is using the router hostname as a udhcpc parameter. That being the case, makes me wonder if it matters that technically your hostnames (Main_router, Entertainment_Center, Back_Room_Wireless_AP) are in violation of RFC 952 / RFC 1101 in that they use underscores which aren't in the list of characters allowed in hostnames. Might not have anything to do with it, but I can tell you that several companies I worked for in the past got bit hard in the ass by that very character. Simple test would be to replace the underscores with the specifically allowed minus sign (-) then reboot and see if it makes a difference.

    RFC 952 states:
    A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of "domain style names". (See RFC-921, "Domain Name System Implementation Schedule", for background). No blank or space characters are permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character. The last character must not be a minus sign or period. A host which serves as a GATEWAY should have "-GATEWAY" or "-GW" as part of its name. Hosts which do not serve as Internet gateways should not use "-GATEWAY" and "-GW" as part of their names. A host which is a TAC should have "-TAC" as the last part of its host name, if it is a DoD host. Single character names or nicknames are not allowed.
     
  77. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Texas,

    I will change names and see. Remember they work fine with 8820 and 8502.

    Victek,

    Am I suppose to add this line:

    udhcpc -i vlan1 -s dhcpc-event -H router_dhcp.

    to my non-working 8840?

    "...is not working in ONE Buffalo (your) with ISP Cox .."

    So are you going to say your mods are not compatible with Buffalos? Linksys only mod?

    "problems with Cox..."

    Doubt its Cox. Would be difficult to believe. Do think its the latest version 8840 not being compatible with the Buffalo HP54G's as in between the Buffalo and "Cox" is the modem. The router never talks to Cox. I could try a Zoom modem instead of a Motorola. Will take a call to Cox to change the MAC address. But probably worth a shot. However my guess is behavior will be the same regardless of the modem and will not really be worth the time on hold with tech support at Cox to do so.
     
  78. a9988cd

    a9988cd LI Guru Member

    Output of ps command on a WHR-HP-G54

    Tomato v1.19.8840


    BusyBox v1.10.3 (2008-06-07 00:54:10 CEST) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    /tmp/home/root # ps
    PID USER VSZ STAT COMMAND
    1 root 1768 S init noinitrd
    2 root 0 SW [keventd]
    3 root 0 SWN [ksoftirqd_CPU0]
    4 root 0 SW [kswapd]
    5 root 0 SW [bdflush]
    6 root 0 SW [kupdated]
    7 root 0 SW [mtdblockd]
    39 root 1748 S buttons
    85 root 2016 S syslogd -m 60 -L -s 50
    86 root 2008 S telnetd -p 23
    89 root 2000 S klogd
    97 root 1812 S nas /etc/nas.conf /var/run/nas.pid lan
    128 root 1640 S upnp -D -L br0 -W vlan1 -I 60 -A 180
    230 root 2016 S udhcpc -i vlan1 -s dhcpc-event -H unknow
    234 nobody 2004 S dnsmasq
    237 root 2028 S crond -l 9
    244 root 1288 S rstats
    256 root 1692 S httpd
    376 root 2044 S -sh
    407 root 2024 R ps
    /tmp/home/root #
     
  79. jsmiddleton4

    jsmiddleton4 Network Guru Member

    a9....

    I get no udhcpcp line on my HP54G. Interesting. I do know there are a couple of different versions of the HP54G. Mine is not overclocked and I'm not an overclocker. But there is much discussion about how some HP54G's can over clock, come can't, due to different hardware on dd-wrt's forum months ago.

    Also how "deep" are you into settings? Are you doing arp filtering, static dhcp, wds, etc.? The first few times I booted after installing 8840 on my Buffalo everything worked when doing full nvram reset. It was after the third or fourth reboot when dialing the thing in that it lost the data from the modem and when back to "renewing...."

    "-H unknow"

    That might be interesting if I understand what's being posted about how 8840 is suppose to work. Do you have no name in your identity field?
     
  80. TexasFlood

    TexasFlood Network Guru Member

    I know it's a bit of a reach, just trying to find something, anything, relative to changes after 8820 and thought this might be something after reading Victeks last messages.
     
  81. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Trying it in about 2 minutes. Just renamed the router and will be going back to 8840. I am on a laptop that did not have 8840 d/l it. Took me quite awhile to figure out which symbol had a "cat" on it on rapidshare. I really don't care for rapidshare......


    Edit: Texas, no change with shorter router name.
     
  82. Victek

    Victek Network Guru Member

    a9988cd, nice to see your Buffalo working .. good news. Thanks

    jsmiddleton4, no, I did not mention problems with Buffalo router, my concern was related to your ISP and router, now, after a9988cd message we have only two variables to study .. your ISP or something you forgot in the router configuration...

    Please try to start from scratch, erase nvram, restore defaults, upgrade to new firmware, redo nvram erase, and configure manually .. let's see what's happen.. we are closer .. xing fingers :biggrin:
     
  83. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Ok, here is data update Victek. No change in experience. I wish I could find something in the equipment for you. It really seems to be the firmware. And as my family starts to get going here, I am not going to even try to keep taking their internet access up and down for them today. This data is really no different than we already know.
    ______________________________

    8840 before adding manually the missing line. Can’t get on line. Router does not get dhcp information from cable modem.

    /tmp/home/root # ps
    PID USER VSZ STAT COMMAND
    1 root 1768 S init noinitrd
    2 root 0 SW [keventd]
    3 root 0 SWN [ksoftirqd_CPU0]
    4 root 0 SW [kswapd]
    5 root 0 SW [bdflush]
    6 root 0 SW [kupdated]
    7 root 0 SW [mtdblockd]
    39 root 1748 S buttons
    81 root 2008 S telnetd -p 23
    83 root 2016 S syslogd -m 60 -L -s 50
    85 root 2000 S klogd
    86 root 1812 S nas /etc/nas.conf /var/run/nas.pid lan
    93 root 2020 S crond -l 9
    95 root 1744 S sched start
    96 root 1288 S rstats
    100 nobody 1012 S dnsmasq
    105 root 1984 S zebra -d -f /etc/zebra.conf
    108 root 1692 S httpd
    110 root 2100 S ripd -d -f /etc/ripd.conf
    114 root 2044 S -sh
    120 root 2024 R ps
    /tmp/home/root #

    Here is 8840 after the line Victek indicated 8840 uses added manually. CAN get on-line.

    /tmp/home/root # udhcpc -i vlan1 -s dhcpc-event -H router_dhcp
    ### adapter index 5
    ### adapter hardware address 00:16:01:d2:7a:fd
    udhcpc (v1.10.3) started
    ### vfork'ing and execle'ing dhcpc-event
    ### entering raw listen mode
    ### opening raw socket on ifindex 5
    ### got raw socket fd 6
    ### bound to raw socket fd 6
    ### adding option 0x35
    ### adding option 0x3d
    ### adding option 0x0c
    ### adding option 0x3c
    ### adding option 0x39
    Sending discover...
    ### Waiting on select...
    ### Unrelated/bogus packet
    ### Waiting on select...
    ### Got valid DHCP packet
    ### adding option 0x35
    ### adding option 0x3d
    ### adding option 0x0c
    ### adding option 0x3c
    ### adding option 0x32
    ### adding option 0x36
    Sending select for 72.222.160.186...
    ### Waiting on select...
    ### Got valid DHCP packet
    Lease of 72.222.160.186 obtained, lease time 86400
    ### vfork'ing and execle'ing dhcpc-event
    vlan1: No such process
    ### entering none listen mode
    /tmp/home/root # ps
    PID USER VSZ STAT COMMAND
    1 root 1768 S init noinitrd
    2 root 0 SW [keventd]
    3 root 0 SWN [ksoftirqd_CPU0]
    4 root 0 SW [kswapd]
    5 root 0 SW [bdflush]
    6 root 0 SW [kupdated]
    7 root 0 SW [mtdblockd]
    39 root 1748 S buttons
    81 root 2008 S telnetd -p 23
    83 root 2016 S syslogd -m 60 -L -s 50
    85 root 2000 S klogd
    86 root 1812 S nas /etc/nas.conf /var/run/nas.pid lan
    93 root 2020 S crond -l 9
    96 root 1288 S rstats
    108 root 1692 S httpd
    114 root 2044 S -sh
    168 nobody 1012 S dnsmasq
    193 root 2028 S /bin/sh /tmp/new_arpbind_start.sh
    199 root 1984 S zebra -d -f /etc/zebra.conf
    214 root 2100 S ripd -d -f /etc/ripd.conf
    432 root 2016 S udhcpc -i vlan1 -s dhcpc-event -H router_dhcp
    586 root 2024 R ps
    587 root 0 []
    /tmp/home/root #
     
  84. a9988cd

    a9988cd LI Guru Member


    I just clearing NVRAM and the ROUTER IP set to 192.168.11.1.
     
  85. jsmiddleton4

    jsmiddleton4 Network Guru Member

    victek....

    "we have only two variables to study .. your ISP or something you forgot in the router configuration... "

    Sorry but you are incorrect with that conclusion. You assume all HP54G's are the same inside. They are not. There are different versions. And IF its the router, that does not explain why works fine with 8820, 8502, regular Tomato but not with your versions starting with 8835 which you have changed.

    You can certainly focus where you'd like but focusing on this Buffalo router version seems to me a misfocus. Especially since I can add the line manually and it works and it works with 8820.

    Are you trying to prove its my router or that you still have work to do on the firmware? Since one will be a waste of my time I'd like to know. I'm there for you to do whatever I can as long as I am helping move toward a fix. If we're working on trying to pin this on my router, I will bow out and spend my time doing other things today.
     
  86. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Actually after reading victek's last post I'll just bow out for awhile. Its clear that with the firmware mod's after 8820 that you mods are no longer fully compatibility for hardware devices that Tomato regular supports. I'll check later today to see if you've decided to pursuit firmware mods that maintain that full compatibility or not. Glad to help IF that is what we are trying to accomplish.

    For now I'll just stay with speedmod 8502 and that full compatibility.

    THanks. Good luck.
     
  87. TexasFlood

    TexasFlood Network Guru Member

    Again, I resemble that remark, :-D , I have a long list of stuff to do today and won't be able to be online much as a result, although I'm sure my family will.
     
  88. Victek

    Victek Network Guru Member

    jsmiddleton4, thanks for your findings,

    1st_ You don't need to add any line, the router will find the IP WAN.
    2nd_ No changes has been done related to hardware.
    3rd_ I hope to find somebody else with your issue, thanks for your cooperation.
     
  89. mstombs

    mstombs Network Guru Member

    There is a clear bug in the sourcecode of 8840 if the wan hostname is not set - it is stored in nvram variable wan_hostname, if not set the command to start udhcpc could easily fail as it would have non-initialized variables, or the incompatible "-m" or "-Q".
     
  90. TexasFlood

    TexasFlood Network Guru Member

    I checked and the wan_hostname variable seems to be the same as the "Hostname" field on the Basic -> Identification page. This is where I have the wrt54gv2 name that shows up as a parameter on the udhcpc line. I probably should have been more specific about what field I was talking about earlier as there is also a "Router Name" field on that page which goes into the nvram router_name variable and doesn't seem to be in play here. I was assuming (and you know what they say about that word, can make an ass out of U and me), that jsmiddleton4 had his router names in the Hostname field when in fact he could have been using only the "Router Name" field with the Hostname field blank. I believe it would only be the Hostname field that RFC 952 / RFC 1101 apply to. That field being blank could more likely be a problem than having underscores in the name. When going back and testing, I was allowed to leave the Hostname field blank but not the Router Name field. Probably safe to assume that a lot of folks will leave that field blank if allowed to & not clearly required, especially if it hasn't had any negative impact previously.

    Just tested it and leaving the "Hostname" field blank on the Basic -> Identification page results in exactly what jsmiddleton4 is describing. Below is my ps list after blanking out that field on my router and rebooting. My router was unable to get a WAN IP and reported it was "renewing...." just as jsmiddleton4 described. Maybe this is the culprit.

    Tomato v1.19.8840


    BusyBox v1.10.3 (2008-06-07 00:54:10 CEST) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    /tmp/home/root # ps
    PID USER VSZ STAT COMMAND
    1 root 1768 S init noinitrd
    2 root 0 SW [keventd]
    3 root 0 SWN [ksoftirqd_CPU0]
    4 root 0 SW [kswapd]
    5 root 0 SW [bdflush]
    6 root 0 SW [kupdated]
    7 root 0 SW [mtdblockd]
    39 root 1744 S buttons
    85 root 2016 S syslogd -m 60 -L -s 50
    86 root 2008 S telnetd -p 23
    88 root 2000 S klogd
    89 root 1932 S nas /etc/nas.conf /var/run/nas.pid lan
    94 root 2020 S crond -l 9
    96 root 1744 S sched start
    98 root 1288 S rstats
    100 nobody 1012 S dnsmasq
    103 root 1692 S httpd
    120 root 2044 S -sh
    123 root 2024 R ps
    /tmp/home/root #
     
  91. jsmiddleton4

    jsmiddleton4 Network Guru Member

    1st_ You don't need to add any line, the router will find the IP WAN.

    Sorry but IF I want 8840 to work I most certainly do have to add the line via telnet.

    3rd_ I hope to find somebody else with your issue, thanks for your cooperation.

    Hope you do too. Not sure why? How much proof do you need to know something isn't quite right IF you want to continue to have the widespread platform support of your previous mods? I have 2 Buffalo HP54G's. 8840 does not work on either. Again its up to you and if your goal is to maintain the broad platform support enjoyed by your previous versions and Tomato in general. Its none of my business what you decide to do. However at this point it is clear there is an issue with some Buffalo HP54G's and if it isn't noted either on a download page or in your *.txt file I suggest a comment about the possibility of hardware support being at best suspect for some Buffalo routers.

    Again I'll be glad to help in anyway I can to help you track down what is not working in your firmware for some Buffalo HP54G's. However I'm not going to help build a case that your firmware is ok and the problem is my router. That is NOT the case and anything of that nature will be waste of my time. If it was the case that previous versions of Tomato, speedmods mod, your previous versions didn't work, ok, its probably my router. However that is not the case. Whatever changes were made starting with 8835 have removed support for the Buffalo HP54G's that I have.

    There is nothing wrong with saying your mod's only fully support certain Linksys routers and maybe certain Buffalo routers. Even if that is the case your mod's are still amazing and quite handy. Again I'm not telling you what your mods should or should not support. Just making it clear that IF you want to allow the implication that your mod will support the same hardware platforms that regular Tomato support, you have some work to do. If you are only shooting for support certain hardware platforms, that needs to be clearly stated somewhere.

    Jim
     
  92. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Texas,

    So what information/fields did you fill out to make it work? Both router name and host name?
     
  93. TexasFlood

    TexasFlood Network Guru Member

    I think so, yes. I have the Domain Name defined as well but don't think that's involved in what's happening here, although I didn't test that. And just to be safe, when chosing your hostname I would use the rules in my earlier, not quite on track, post which described the RFC rules for a host name. This, in a nutshell is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-). If this is causing the issue, then I think that this is a bug in the 8840 code, and other post 8820 builds as this is currently not a mandatory field. While I think it's good practice to fill that field out, as I had done, it's not required and the WAN DHCP should not fail if it is left blank.
     
  94. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Put "Main" in router name. Put "Server" in Host name. Did so under 8820. Saved it. Then installed 8840. Snaps right up and I'm on-line using 8840 typing here. I have no idea what that is telling anyone. The "Why" component. But clearly different than previous versions and if what has been posted about it is correct, something isn't quite right.

    So a line missing in the .c pre-compiled code or something? A "get this information from this place and send it over to that place" not quite right?

    Jim
     
  95. Victek

    Victek Network Guru Member

    Jim.. you have a PM .. read and try :biggrin: ... You're a terrific Beta tester ... ;) . The rules for udhcp meet standard RFC3397.
     
  96. TexasFlood

    TexasFlood Network Guru Member

    I can't say specifically. mstombs could as he found it in the code. Somewhere in the "clean" post-8820 dhcp.c code implementation, the case of a blank hostname wasn't accounted for properly but must have been in the "ugly" 8820 dhcp.c code implementation.
     
  97. jsmiddleton4

    jsmiddleton4 Network Guru Member

    I think victek is trying to clean up the dhcp code which is a good thing. Cleaner effective code is usually faster, more stable, etc. So its not like its a bad idea. And I'm not a programmer so in no way do I suppose to judge such a thing or even have a clue about what the issues are. I can however tell when there is an issue. One would think that the code for the router name, server name, host name thing would not be too many lines of code nor too complicated. Again assuming there. Obviously some variable/dependency is being required/made with 8835 on up that is not in place on 8820 down, nor regular Tomato. 8835 on up DEPENDS on the names being there, etc., and that dependency is critical in nature for the DHCP stuff to work. Again obviously that is either not the case with previous versions or it is and in addition to that critical dependency being in place somewhere else there is an "If no data is present then ignore.." code as well. Who knows.

    I think it is reasonable to stream line the code. Now we know what the problem is I'm sure that's more than 1/2 of the battle. And while I really like Tomato and plan to use it for a long time to come, it does seem to have some history with dhcp "issues".
     
  98. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Once I can actually obtain the beta victek asked me to test I'll get back to him and here.
     
  99. mstombs

    mstombs Network Guru Member

    I'm sure Victek has found and fixed it by now, but look in src/router/rc/dhcp.c lines 292-319. The wan_hostname blank condition wasn't handled properly. Just think how long it would take to get Linksys to fix such a bug - the benefits of Opensource!
     
  100. jsmiddleton4

    jsmiddleton4 Network Guru Member

    victek,

    8845 same issue. If no name in both fields, Router Name and Hostname, (missing space?), no dhcp info passed on, can not connect to web.

    mst....

    Yes, I think we all appreciate the way this thing works and victek's work. Maybe you could suggest some code edits to victek? Something still isn't quite right.
     
Thread Status:
Not open for further replies.

Share This Page