Displaying 5 results from an estimated 5 matches for "ospfv2".
2008 Mar 31
4
Packet corruption in re0
...> packet length issue.
> >
> > Here's what tcpdump on the re(4) device thinks it's transmitting:
> >
> > 00:08:a1:3c:32:9c > 00:90:fb:0c:89:7d, ethertype 802.1Q (0x8100), length
> 1510: vlan 1000, p 0, ethertype IPv4, 196.22.138.92 > 196.22.138.89: OSPFv2,
> Database Description, length: 1472
> >
> > Here's what was actually recieved by the em(4) device on the
> > neighbour. Note the absense of the 801.1Q header:
> >
> > 00:08:a1:3c:32:9c > 00:90:fb:0c:89:7d, ethertype IPv4 (0x0800), length 1506:
>...
2013 Nov 05
2
syslinux.efi pxeboot across multiple subnets
The same client was used for syslinux.efi (both success on same subnet and
failure on different subnet) and grub.efi. The DHCP host block is setup
like:
host testing {
hardware ethernet {mac} ;
next-server 10.16.195.178 ;
filename "rhel64/syslinux.efi" ;
}
I'll pull a tcpdump filtering by the IP tomorrow when I get back to the
systems.
On Mon, Nov 4, 2013 at 6:41 PM,
2013 Nov 05
0
syslinux.efi pxeboot across multiple subnets
...eader OSPF (89) payload length: 36)
fe80::a17:f4ff:fe62:631f > ff02::5: OSPFv3-hello 36: rtrid 2.2.2.2 backbone
V6/E/R ifid 0.0.0.32 pri 1 int 10 dead 40 dr 2.2.2.2 nbrs
09:52:58.795974 IP (tos 0xc0, ttl 1, id 57703, offset 0, flags [none],
proto OSPF (89), length 64) 10.16.233.1 > 224.0.0.5: OSPFv2, Hello, length: 44
<snip/>
2013 Nov 05
2
syslinux.efi pxeboot across multiple subnets
...oad length: 36)
> fe80::a17:f4ff:fe62:631f > ff02::5: OSPFv3-hello 36: rtrid 2.2.2.2 backbone
> V6/E/R ifid 0.0.0.32 pri 1 int 10 dead 40 dr 2.2.2.2 nbrs
> 09:52:58.795974 IP (tos 0xc0, ttl 1, id 57703, offset 0, flags [none],
> proto OSPF (89), length 64) 10.16.233.1 > 224.0.0.5: OSPFv2, Hello,
> length: 44
> <snip/>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mai...
2008 Sep 13
3
Problem to run 4 virtual machines at a time.
Hi all
I have installed vyatta system, (vyatta-livecd-vc4-alpha2.iso ) on top of
Centos5.
Our system requirement is,
* Centos 5.1 (2.6.18-92.1.10.el5xen )
* 2 Gb RAM,
* x86_64
And cpu information is as follow,
[root at turtle4 ~]# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 107
model name : AMD Athlon(tm) 64 X2 Dual Core