[Dnsmasq-discuss] DHCP doesn't seem to respond to requests(?)
dnsmasq at lovelady.com
dnsmasq at lovelady.com
Thu May 19 03:07:38 BST 2011
Sorry, I don't know what you mean. A little on the cryptic side for me,
sorry.
I have no shorewall. I followed these instructions, relevant to this
device:
To deactivate the firewall you need to edit /etc/init.d/oe-bootfinish, go to
line 114 and comment out, or delete, this line:
/etc/init.d/iptables ifup > /dev/null 2>&1
now you need to clear the current iptables rules, you can simply reboot the
Stora or delete them manually using:
> sudo /sbin/iptables -F
Then I rebooted.
After reboot, output of
iptables -L -n
is as follows:
iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
INPUT-INTERNAL all -- 169.254.0.0/16 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:515
reject-with icmp-port-unreachable
INPUT-INTERNAL all -- 192.168.0.0/24 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state
RELATED,ESTABLISHED
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 8
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:443
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:113
reject-with icmp-admin-prohibited
DROP all -- 0.0.0.0/0 0.0.0.0/0
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain INPUT-INTERNAL (2 references)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
Dennis Lovelady
--
Tom Seaver: "What time is it?"
Yogi Berra: "You mean now?"
> > > > My configuration is simple for now:
> >
> > # (latest)
> > domain-needed
> > bogus-priv
> > expand-hosts
> > domain=lovelady.com
> > dhcp-range=192.168.0.150,192.168.0.249,72h
> > dhcp-host=00:23:8b:8a:ad:70,192.168.0.249
> > log-dhcp
> >
> > > 1. turn on logging by adding "log-dhcp" and tail -f .../messages
> > > 2. run "tcpdump -i eth0 port bootpc or port bootps" on server
> >
> > Stopped iptables and flushed with -F on both systems.
> >
> iptables -F does not change policy. If you had DROP...
>
> # shorewall clear
> # tcpdump
> listening on loc, link-type EN10MB (Ethernet), capture size 65535 bytes
> 03:39:55.090620 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
> Request from 52:54:00:12:34:56 (oui Unknown), length 390
> 03:39:55.091080 IP 192.168.2.1.bootps > 192.168.2.2.bootpc: BOOTP/DHCP,
> Reply, length 300
>
> # iptables -P INPUT DROP
> # tcpdump
> listening on loc, link-type EN10MB (Ethernet), capture size 65535 bytes
> 03:40:37.588198 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
> Request from 52:54:00:12:34:56 (oui Unknown), length 390
> [ ****** no reply ******* ]
> 03:40:38.560985 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
> Request from 52:54:00:12:34:56 (oui Unknown), length 390
>
> --
> jasiu
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
More information about the Dnsmasq-discuss
mailing list