ipxe iscsi boot fails, even in virtualbox

[masterr-10da]

(2014-01-20 08:53)robinsmidsrod Wrote:  MultiMediaMan: The "autoboot" command (default script) does try to boot the root-path if it is present and looks like an iSCSI URL. But obviously that will not allow you to do the net0/gateway 0.0.0.0 hack. But I also notice that the dhcpd config sets that explicitly anyways. So overall it does seem like most of your suggestions have already been followed.

Master: I see ipxe.bus-id being used to detect iPXE instead of using user-class. That could be a problem. The image also shows the network settings _before_ the dhcp was performed, not after. So we don't know if they get applied to the setup or not (I think they are, but would like to be sure).

I see an error now as I installed portsentry:

Code:

Wed Jan 22 21:05:02 2014 daemon.notice portsentry[1461]: attackalert: UDP scan from host: 10.192.192.1/10.192.192.1 to UDP port: 68
Wed Jan 22 21:05:02 2014 daemon.notice portsentry[1461]: attackalert: Host: 10.192.192.1/10.192.192.1 is already blocked Ignoring

there must be a good reason why the rule

Code:

iptables -A forwarding_lan -i br-lan -o br-lan -j ACCEPT

doesn't apply. What does the error

iptables: No chain/target/match by that name.

mean? To me it looks like the forwarding_lan ruleset doesn't exist anymore.

"ipxe.bus-id being used to detect iPXE instead of using user-class"
Thanks, I'll test if that makes the difference.