Alain Durand wrote:
> Hi James,
>
> Could you please elaborate a bit further ? I must admit I do not really
> understand what should be done.
http://blogs.sun.com/stw/entry/using_ip_instances_with_vlans
>
> Thanks,
> Alain
>
> On Jun 5, 2008, at 3:05 PM, James Carlson wrote:
>
>> Alain Dura
James Carlson wrote:
> Ben Rockwood writes:
>
>> I'm gonna bump this with hopes a developer will pick it up. I do not yet
>> see a bug associated with this issue.
>>
>
> You're talking about CR 6684810, which was fixed back in snv_88.
>
>
Awesome, thanks James.
benr.
___
Alain Durand writes:
> When the zone boots I get the following error :
>
> zoneadm: zone 'tournette': WARNING: skipping network interface
> 'vfe1000' which is used in the global zone.: Not owner
[...]
> PS : On Solaris 10 Update 5 dladm cannot be used to create vlan's so I
> used "ifconfig vfe
Not much success with that, here's what I got configuring the zone
with an exclusive IP stack :
...
set ip-type=exclusive
add net
set physical=vfe1000
end
My sysidcfg file has the following to set networking :
network_interface=primary
{hostname=tournette
ip_address=xx.12
Alain Durand writes:
> Could you please elaborate a bit further ? I must admit I do not
> really understand what should be done.
Something like this:
# dladm create-vlan -l vfe0 -v 1
# zonecfg -z blue 'add net; set physical=vfe1000; end'
--
James Carlson, Solaris Networking <[EMA
Hi James,
Could you please elaborate a bit further ? I must admit I do not
really understand what should be done.
Thanks,
Alain
On Jun 5, 2008, at 3:05 PM, James Carlson wrote:
Alain Durand writes:
I built the driver with GLDv3 :
# dladm show-link
vfe0type: non-vlan mtu: 150
Alain Durand writes:
> I built the driver with GLDv3 :
>
> # dladm show-link
> vfe0type: non-vlan mtu: 1500 device: vfe0
>
> What was your idea with a VLAN ?
You can create VLANs on that device and place them into exclusive
stack zones using zonecfg.
--
James Carlson, Solari
I built the driver with GLDv3 :
# dladm show-link
vfe0type: non-vlan mtu: 1500 device: vfe0
What was your idea with a VLAN ?
//Alain
On Jun 5, 2008, at 1:34 PM, James Carlson wrote:
Alain Durand writes:
and here are the routes seen from the zone :
That doesn't look qui
James Carlson wrote:
> James Carlson writes:
>> Steffen Weiberle writes:
>>> BTW, this only works for default routes. Static ones don't work. at
>>> least that is my/others' experience.
>> That's not true. Default routes are not supposed to be special.
>> They're just regular network routes that
Alain Durand writes:
> and here are the routes seen from the zone :
That doesn't look quite right; the route should be visible there
because the next hop address is reachable.
> If needed I could use IP instances (I'm running Solaris 10 Update 5),
> but have only one physical ethernet interface
Ben Rockwood writes:
> I'm gonna bump this with hopes a developer will pick it up. I do not yet see
> a bug associated with this issue.
You're talking about CR 6684810, which was fixed back in snv_88.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 N
James Carlson writes:
> Steffen Weiberle writes:
> > BTW, this only works for default routes. Static ones don't work. at
> > least that is my/others' experience.
>
> That's not true. Default routes are not supposed to be special.
> They're just regular network routes that happen to have 0/0 as a
Steffen Weiberle writes:
> BTW, this only works for default routes. Static ones don't work. at
> least that is my/others' experience.
That's not true. Default routes are not supposed to be special.
They're just regular network routes that happen to have 0/0 as a
destination.
If you're seeing su
I'm gonna bump this with hopes a developer will pick it up. I do not yet see a
bug associated with this issue.
Based on my looks through the code this error occurs on line 2518 of vplat.c.
The function configure_one_interface(); is called, but just prior loopback
nwif_defrouter is nulled:
14 matches
Mail list logo
