srakajournal.blogg.se

Firewall builder ddwrt default iptables
Firewall builder ddwrt default iptables




firewall builder ddwrt default iptables

After discovering dd-wrt several weeks ago and seeing what *should* be possible, I just can't seem to stop though. The Firewall Builder's rule set seems to break DHCP on the internal lan no matter which default rules I disable/delete so I always return to the defaults following my tests. I've tried using Firewall Builder to temporarily/permanently overwrite the default iptables entries, but to no avail. I have connected a Canon BJC-85 and LaserJet 3330 (one at a time) and both are detected and printed to successfully.įor me, it is the Port Forwarding issue that is the hangup at the moment. Another reboot (or two) solves the problem. From what I have read, this seems to be a problem common to all dd-wrt builds. It is true that every couple of router reboots I find that no USB devices are detected.

firewall builder ddwrt default iptables

I then installed the p910nd print server via the console, corrected the path on the third line of /jffs/etc/init.d/p910nd (as did you, per the guide), and inserted the following statement in my usb.startup script: I enabled the "USB storage support", "USB 1.1 Support (OHCI)", "USB 2.0 Support", and "USB Printer Support" modules (amongst others) via the web interface. Over the last week or two I've only used the build posted by Eko via this discussion thread (DD-WRT v24-sp1 (08/14/0 mini - build 10137M TNG Eko), since it has been the only build I've used thus far with stable USB storage support for this router, and I can confirm that printer sharing works fine on this build too. Printer sharing is the one feature that I have not had any troubles with on this router - not on the v24sp1 generic mini, standard, or mega builds. Posted: Tue 18:02 Post subject: printer sharing I've tried enabling and disabling USB 2.0 support, same results both ways. What the heck am I doing wrong here? From what I see the printer is not being detected. Netstat also confirms port 9100 being open, etc. Sep 16 08:05:13 p9100d: finished job: 154047 bytes received, 0 bytes sentĪnd finally, the results of "ps | grep p910" show that it is set up correctly!:ģ06 root 688 S p9100d -b -f /dev/usb/lp0 0Ĥ46 root 680 S /jffs/usr/sbin/p9100d -b -f /dev/usb/lp0 0

firewall builder ddwrt default iptables

jffs/usr/sbin/p910nd -b -f /dev/usb/lp0 0Īnd yes, I did "chmod +x /jffs/etc/config/usb.startup" the file to make it executable, as well as add it into the startup command box so that it is run on each boot.Īlso, in the syslog, I am seeing info to confirm that /dev/usb/lp0 is not being created: Within the "/jffs/etc/init.d/p910nd" file, the "DEFAULT=" line was changed to "/jffs/etc/default/p910nd" as per the guide.Ĭontents of the file "/jffs/etc/config/usb.startup" are: Within the file "/jffs/etc/default/p910nd" I have: Usb.c: new USB bus registered, assigned bus number 1 Usb-ohci.c: USB OHCI at membase 0xb8003000, IRQ 6

FIREWALL BUILDER DDWRT DEFAULT IPTABLES DRIVER

Usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Not getting any USB related errors, but /dev/usb/lp0 is not being created. I've sucessfully set this up with the same printer on a Asus WL-500G Premium v1, with no problems using just the regular release of the v24sp1 build. I've used both the Web GUI to configure the Port Forward as well as the command line via telnet: I am configuring the router on a private 10.7.x.x subnet at the moment and attempting to view the Index.htm page served out by the thttpd service. I imagine there would be security implications if I were to disable the firewire with the WAN port being public (Comcast cable modem). The incoming security log indicates that the TCP connections originating from the I computer I'm attempting to browse from (on the WAN side) are being dropped. Is this to be expected? I've read dozens of posts and they seem to suggest that I should be able to port forward with SPI enabled. I'm finding that I am unable to forward a port on the WAN interface (x.x.x.x:8080 for instance) to the port used by thttpd on the private side of the router (192.168.1.1:8008) unless I disable the SPI firewall. Posted: Mon 22:23 Post subject: port forwarding with firewall up (versus down).Įxperimenting with the thttpd service now before moving on to the Optware installment of OpenVPN.






Firewall builder ddwrt default iptables