search for: dns_resolv

Digging more, loadfile("192.0.2.1::pxe.0", &file.data, &file.size), queries DNS, which sounds like it doesn't follow the same call path as a COM32 calling pxe_dns(). If the DNS won't resolve the IP, things won't load properly. pxechn.c32 sets sname in the intended packet to "192.0.2.1" which may be confusing something. More debugging needed. -- -Gene

...s(). If the DNS won't resolve the IP, things >> won't load properly. pxechn.c32 sets sname in the intended packet to >> "192.0.2.1" which may be confusing something. >> >> More debugging needed. >> >> -- >> -Gene > > core/legacynet/dns_resolv.c is quite different and doesn't bother > testing quads first. > > Matt/HPA: should this be patched or somehow checked to see if it can > be factored away? I've got a crude patch that I can clean up. > > -- > -Gene Also, com32/lib/syslinux.c:pxe_dns() and core/pxe/dns...

...rently it appears that when PXE booting the domain search option is ignored and only the domain name option used for name resolution. The following patch adds support for domain search path usage when PXE booting: - adds parsing of the DHCP domain search option (119) - When resolving names via dns_resolv uses the search path if there's no dot in the name. - Reverts to the previous behaviour in the absence of a search path, if the name contains a dot or if no addresses are found when searching the domain search path. Steve Bleazard -- diff -upr syslinux-6.03.orig/core/fs/pxe/dhcp...

...oting the domain search option is > ignored > and only the domain name option used for name resolution. > > The following patch adds support for domain search path usage when PXE > booting: > - adds parsing of the DHCP domain search option (119) > - When resolving names via dns_resolv uses the search path if there's no > dot in the name. > - Reverts to the previous behaviour in the absence of a search path, if > the name contains a dot or if no addresses are found when searching the > domain search path. > > Steve Bleazard > > -- > di...

Hello, When trying out (g)pxelinux using TFTP URLs and the '<host>::<path>' syntax, pxelinux seemed to "hang". Some printf debugging and tcpdump revealed that it looped in the timeout after sending the TFTP RRQ. Further investigation revealed, that if a plain IP address (e.g. "tftp://12.34.56.78/something") is used, the byte order is not converted from host

I noticed several issues when diagnosing why pxechn.c32 didn't work in 5.01-pre3. 1) pxechn.c32, prdhcp.c32 and other modules crash Syslinux and force a reboot by executing an unresolved symbols. unload_pxe(), dns_resolv() and pxe_call() are the three. "Error: An undefined symbol was referenced" 2) In past versions, I built a debug build by having "CFLAGS += -DDEBUG=1" in mk/local.mk but this fails. core/../com32/include/com32.h:144: undefined reference to `__bad_SEG'

...twork stacks do. By > timing out we are now able to handle packet loss on the network, e.g. > we'll now re-send TFTP requests instead of waiting for ACK packets that > will never come. > Hmmm. We already have a timeout loop in tftp_get_packet() as well as in the legacy version of dns_resolv(). I would like to suggest we augment the generic UDP receive function call with a timeout, rather than implementing a timeout upon a timeout. What do you think? -hpa

On Sat, Jan 16, 2016 at 8:49 AM, Celelibi via Syslinux <syslinux at zytor.com> wrote: > 2016-01-15 22:23 UTC+01:00, Bateman, Matt via Syslinux <syslinux at zytor.com>: >> I am working on setting up a global boot server that serves up files across >> the WAN. I am running into a 5 minute timer that is rebooting my hosts >> before they can complete the kernel and

...version this manpage is accurate against. Signed-off-by: Jeff Layton <jlayton at samba.org> commit 861824f588a870da7c110b6f199eb5ce7d4dc476 Author: Jeff Layton <jlayton at samba.org> Date: Tue Jul 19 14:53:47 2011 -0400 cifs-utils: add a note about inclusion of keys.dns_resolver program in keyutils As of version 1.5, the keyutils package is shipping a generic dns_resolver upcall. Add a note to the cifs.upcall manpage that mentions this and recommends the use of that program over cifs.upcall. Eventually, we may want to be able to conditionally co...

...on is >> ignored >> and only the domain name option used for name resolution. >> >> The following patch adds support for domain search path usage when PXE >> booting: >> - adds parsing of the DHCP domain search option (119) >> - When resolving names via dns_resolv uses the search path if there's no >> dot in the name. >> - Reverts to the previous behaviour in the absence of a search path, if >> the name contains a dot or if no addresses are found when searching the >> domain search path. >> >> Steve Bleaz...

....00GB, used=586.00MB Metadata: total=8.00MB, used=0.00 Apr 13 04:05:54 datastore01 kernel: [1210991.339071] BUG: soft lockup - CPU#3 stuck for 22s! [btrfs-endio-wri:30524] Apr 13 04:05:54 datastore01 kernel: [1210991.342079] Modules linked in: nfsd nfsv3 nfs_acl nfsv4 auth_rpcgss nfs lockd sunrpc dns_resolver fscache btrfs zlib_deflate libcrc32c lpfc coretemp kvm_intel kvm iTCO_wdt enic i7core_edac i2c_i801 iTCO_vendor_support edac_core bnx2 lpc_ich mfd_core ioatdma joydev pcspkr acpi_power_meter dca crc32c_intel microcode wmi i2c_algo_bit drm_kms_helper ttm drm fnic usb_storage libfcoe libfc mptsas s...

...ompat mode) I have searched the web for a solution on the last few days. Mostly it came down to this: Take care that smbclient, cifs-utils and keyutils is installed. Also have these lines in /etc/request-key.conf: create cifs.spnego * * /usr/sbin/cifs.upcall %k create dns_resolver * * /usr/sbin/cifs.upcall %k My setup satisfies these requirements. I have tried the connection with these commands (I replaced our domain with example.com): mount -v -t cifs //office.example.com/technik /mnt/dfs -o username=c.garling,domain=OFFICE,vers=2.0 mount -v -t...

I ran into a panic while running find -xdev | xargs brtfs fi defrag ''{}''. I don''t remember the exact command because the history was not saved. I also started and stopped it a few times however. The kernel logs were on a different filesystem. Here is the kern.log:http://fpaste.org/9383/36729191/ My setup is two 2TB hard drives in raid 1. They are both sata drives so

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e: Merge remote-tracking branch 'mfleming/merge/elflink/master'...

...no avail .. do you have any suggestions ? .config is attachted This is on the guest console: [ 0.219507] TCP: cubic registered [ 0.219513] NET: Registered protocol family 17 [ 0.219530] Bridge firewalling registered [ 0.219536] Ebtables v2.0 registered [ 0.219550] Registering the dns_resolver key type [ 0.219736] registered taskstats version 1 [ 0.219748] XENBUS: Device with no driver: device/vbd/51713 [ 0.219752] XENBUS: Device with no driver: device/vbd/51714 [ 0.219757] XENBUS: Device with no driver: device/vif/0 [ 0.219789] Magic number: 1:252:3141 [ 0.219840]...

...tions? Here is dmesg in one of the freezes: [23664.639186] WARNING: CPU: 3 PID: 7223 at drivers/gpu/drm/nouveau/include/nvkm/subdev/i2c.h:172 init_rdauxr+0xf4/0x130 [nouveau] [23664.639187] Modules linked in: nfnetlink cfg80211 fuse rfcomm arc4 md4 sha512_ssse3 sha512_generic nls_utf8 cifs ccm dns_resolver fscache 8021q garp mrp bridge stp llc vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac bnep intel_rapl snd_hda_codec_hdmi btusb btrtl btbcm x86_pkg_temp_thermal btintel intel_powerclamp bluetooth nls_ascii nls_cp437 coretemp vfat fat kvm_intel jitterentropy_rng kvm snd_hda_codec_realtek snd_hd...

...st_del_entry+0xdd/0xe0() Oct 10 10:36:18 adam.happyassassin.net kernel: list_del corruption. next->prev should be ffff8801b5727240, but was ffff8001b5727240 Oct 10 10:36:18 adam.happyassassin.net kernel: Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd rfcomm arc4 md4 nls_utf8 cifs dns_resolver fscache fuse xt_CHECKSUM ipt_MASQUERADE vhost_net tun vhost macvtap macvlan nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT xt_conntrack cfg80211 ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip...

Christian Garling via samba wrote: > Take care that smbclient, cifs-utils and keyutils is installed. Also > have these lines in /etc/request-key.conf: > > create cifs.spnego * * /usr/sbin/cifs.upcall %k > create dns_resolver * * /usr/sbin/cifs.upcall %k > > My setup satisfies these requirements. I have tried the connection > with these commands (I replaced our domain with example.com): > > mount -v -t cifs //office.example.com/technik /mnt/dfs -o > username=c.garling,domain=...

On Sun, Nov 14, 2010 at 10:32, Gene Cumm <gene.cumm at gmail.com> wrote: > Per doc/pxelinux.txt, the special PXELINUX filename specification of > "IP address::filename" allows "IP address" to be a DNS recognizable > name. ?If it contains no dots, the domain name (DHCP option 15) is > supposed to be appended to qualify the name. > > Testing PXELINUX 3.86,

...l path as > a COM32 calling pxe_dns(). If the DNS won't resolve the IP, things > won't load properly. pxechn.c32 sets sname in the intended packet to > "192.0.2.1" which may be confusing something. > > More debugging needed. > > -- > -Gene core/legacynet/dns_resolv.c is quite different and doesn't bother testing quads first. Matt/HPA: should this be patched or somehow checked to see if it can be factored away? I've got a crude patch that I can clean up. -- -Gene